onesixtythree
Joined 11 years ago
Joined 11 years ago
What I don't get is: why has Python 3 adoption been so slow? Is it just backward compatibility, or are there deeper problems with it that I'm not aware of?
Not true. Traditional Asian societies take the other extreme and venerate age (probably more than they should, but that's another topic). Hence, you have 90-year-old patriarchs calling shots in family businesses, and middle-aged men whose parents were still alive were traditionally considered still adolescent. Also, not taking care of your parents is a jailable crime in China.
In every society but our own, women after 40 were considered very old.
I'm a man under 40, so this may not be my fight, but... Fuck. That. Shit. While it is true that middle-aged, unmarried women were once considered undesirable and suspect, that was in societies in which urinating at the dinner table was socially acceptable, childbirth meant a 1-in-25 chance of dying, indoor plumbing didn't exist, and tuberculosis was a death sentence.
She should be happy to be alive instead of complaining about young people being young.
She's not complaining about young people being young. She's complaining about people (often with no reference to their age) being stupid. Not all young people are stupid.
I do find, strangely, that I'm way more attractive to women now that I'm older, even though my looks have (objectively) declined. Adolescent men are unwanted, invisible, and generally disliked by society unless they're in the top 5% for social skills; things get better at 25 and a lot better after 30... although I'm still glad that I married young because I'd imagine that the dating pool shrinks considerably.
The aim isn't necessarily widespread adoption, so much as the ability for people who know it to use professionally. It's way past merely "production ready", but reputation is a lagging indicator and so most programmers are stuck doing Java...
Since the goal is to avoid {success at all costs}, getting 25% market share is probably not possible. 1 percent would be a start.
The problem, economically speaking, is that Haskell and Clojure engineers are massively underpaid, when you consider that an average Haskeller would be Principal+ at any Java shop. That's because the Java and C++ people can create bidding wars every year and spike their salaries, whereas using a better but more niche language makes that career strategy untenable.
Haskell's laziness isn't as much of an issue as people make it out to be. You can have strictness any time you need it, so it's more akin to an opt-out model than laziness being forced upon the programmer. It is correct to observe that high-performance applications frequently have a lot of strictness annotations, and the argument can be made that high-performance Haskell (while it can be close to C in performance) isn't "idiomatic"... although that claim is true of all high-level languages (even Java). High-performance Clojure ends up being full of '^' characters for type annotations, and high-performance Haskell ends up being full of '!' characters for strictness.