Re:Why is the JavaScript ecosystem like this
by PaulHoule on Wednesday January 04, 2023 @05:21PM
(#34252737)
Common Lisp and Java were two of the first languages designed by adults and they broke those trends.
[ Parent
| on HN ]
Re:Why is the JavaScript ecosystem like this
by amalgamated_inc on Wednesday January 04, 2023 @05:40PM
(#34252967)
I've never used CL but heard it's very "design by committee." Java is worse than JS. So yea, maybe hodge podge is actually the best option we have.
Re:Why is the JavaScript ecosystem like this
by WorldMaker on Wednesday January 04, 2023 @10:18PM
(#34255451)
Yeah, the "Common" in Common Lisp comes from committee. Lisp itself was a "basically designed overnight" language that became an incredibly popular hodge podge of a million snowflake variants and then eventually two competing attempts to standardize and clean up the hodge podge happened: Scheme (to my understanding a BFDL-like situation of a strong figure building anew, with few backwards compatibility cares) and Common Lisp (a standards committee and then some, with a bunch of backwards compatibility shenanigans to sort out).
(ETA: I am a fan of Common Lisp, for what that is worth, if this sounds too critical. It's a very nice language. Some of what has made it nice was a massive committee and standards effort, very similar to the way JS has continued to evolve under TC-39 stewardship.)
Also yeah, my impression of Java was that it was very design-by-committee.
Re:Why is the JavaScript ecosystem like this
by lispm on Thursday January 05, 2023 @04:13AM
(#34257645)
> Lisp itself was a "basically designed overnight" language
Roughly "overnight" for six years:
Re:Why is the JavaScript ecosystem like this
by WorldMaker on Thursday January 05, 2023 @03:09PM
(#34265789)
Per that own history, the first version "Lisp 1" was written as a project in a single University semester. Compared to the many committee years of, for instance, ALGOL, that is "basically overnight" by comparison.