What's very interesting about your comment is this:
Let's say that JavaScrip was a language for "kiddies" in 2008. Let's call them people in the age group 17-22. That was fourteen years ago, and those "kiddies" are now 31-36.
In 2008, they were in entry-level positions. Today, they have over a decade of industry experience and are lead engineers, engineering managers, &c. It's not like they "grew up and switched to adult languages."
They brought JavaScript with them, and as they recognized its shortcomings... They fixed the language and its ecosystem.
(For some debatable definition of "fixed," but the general point is that even if it was a language for script kiddies a decade and a half ago, those kiddies grew up and to a certain extent, the language grew up with them.)
Exactly, add another decade and we're talking about the original Script Kiddies being seasoned executives, or possibly even having cashed out a startup or two and are now investing in startups via the Founder-to-VC pipeline.
Let's say that JavaScrip was a language for "kiddies" in 2008. Let's call them people in the age group 17-22. That was fourteen years ago, and those "kiddies" are now 31-36.
In 2008, they were in entry-level positions. Today, they have over a decade of industry experience and are lead engineers, engineering managers, &c. It's not like they "grew up and switched to adult languages."
They brought JavaScript with them, and as they recognized its shortcomings... They fixed the language and its ecosystem.
(For some debatable definition of "fixed," but the general point is that even if it was a language for script kiddies a decade and a half ago, those kiddies grew up and to a certain extent, the language grew up with them.)