undefined | Better HN

0 pointspetre3y ago0 comments

> the steering council simply wants to to avoid being bitten by Zawinski's "CADT" model

They're being bitten by the bikeshedding model instead, actively encouraging the use of the language like it's 1998. You want to live in 2022? Fine, just type

   use v5.36;

At the top of your program.

0 comments

dinom3y ago

I hesitate to say "they're bikeshedding" since triviality can be highly subjective.

For me, backward compatibility and a smooth, discretionary upgrade path is greatly preferred to trends in language popularity. Therefore, I appreciate the extra deliberation they seem to be taking. Of course other people have different preferences.

To suggest they're bikeshedding implies there's some bigger problems being ignored. Can you elaborate on what those may be?

petreOP3y ago

> Can you elaborate on what those may be?

Read rurban's comment below.

dinom3y ago

I see. Still, somehow I don't think trying to crow-bar "Perl11" onto machines against end user wishes is the right approach. There could be a backlash.

¯\_(ツ)_/¯

j / k navigate · click thread line to collapse

0 pointspetre3y ago0 comments

> the steering council simply wants to to avoid being bitten by Zawinski's "CADT" model

They're being bitten by the bikeshedding model instead, actively encouraging the use of the language like it's 1998. You want to live in 2022? Fine, just type

   use v5.36;

At the top of your program.

0 comments

dinom3y ago

I hesitate to say "they're bikeshedding" since triviality can be highly subjective.

To suggest they're bikeshedding implies there's some bigger problems being ignored. Can you elaborate on what those may be?

petreOP3y ago

> Can you elaborate on what those may be?

Read rurban's comment below.

dinom3y ago

I see. Still, somehow I don't think trying to crow-bar "Perl11" onto machines against end user wishes is the right approach. There could be a backlash.

¯\_(ツ)_/¯

j / k navigate · click thread line to collapse