3 ms·

JS doesn't have a reasonable patch and release cycle, so it's always going to be a chore to try to keep up with discoveries and best practices. The noticeable u

by jack9 9y ago

JS doesn't have a reasonable patch and release cycle, so it's always going to be a chore to try to keep up with discoveries and best practices. The noticeable uptick in releases for other languages are why it's such a joy to work with living languages, instead of the twisted JS world of half-measures and fallen-behind code.

RobertKerans 9y ago
Yearly releases combined with a transparent process track for new features and fixes would be nice.
- lambdadmitry 9y ago
  There is a (somewhat) transparent process! (see [1]) I can't see no design process or vision in there, however, it's just a ton of extra features. It seems that between chaotic feature addition and backward compatibility requirements JS becomes a new C++. [1]: https://github.com/tc39/ https://github.com/tc39/
digi_owl 9y ago
Half and half. Yes JS is a chore to keep up with because everyone can just push crap online willy nilly. But the uptick in other languages is likely more because they are new and therefore there they have a virgin land advantage. Thus everyone and their dog jumps in to play with and stake their claim on fame and fortune. Soon enough those languages will again be bogged down in half measures and fallen behind code. This because while developers wants to play with new ideas and new code, users value stability and predictability.
- jack9 9y ago
  > But the uptick in other languages is likely more because they are new and therefore there they have a virgin land advantage. That is incorrect. The languages in production that interact with javascript, might be a better way to think about it. They are all generally older than javascript (as opposed to dead, like ALGOL). The MS ecosystems and Java might have a bogged down problem in the future, but when even Lua is updated more frequently than JS, you might want to question the wisdom of the current processes.

by jack9 9y ago

RobertKerans 9y ago

Yearly releases combined with a transparent process track for new features and fixes would be nice.

lambdadmitry 9y ago
There is a (somewhat) transparent process! (see [1]) I can't see no design process or vision in there, however, it's just a ton of extra features. It seems that between chaotic feature addition and backward compatibility requirements JS becomes a new C++. [1]: https://github.com/tc39/ https://github.com/tc39/

digi_owl 9y ago

Half and half. Yes JS is a chore to keep up with because everyone can just push crap online willy nilly. But the uptick in other languages is likely more because they are new and therefore there they have a virgin land advantage. Thus everyone and their dog jumps in to play with and stake their claim on fame and fortune. Soon enough those languages will again be bogged down in half measures and fallen behind code. This because while developers wants to play with new ideas and new code, users value stability and predictability.

jack9 9y ago
> But the uptick in other languages is likely more because they are new and therefore there they have a virgin land advantage. That is incorrect. The languages in production that interact with javascript, might be a better way to think about it. They are all generally older than javascript (as opposed to dead, like ALGOL). The MS ecosystems and Java might have a bogged down problem in the future, but when even Lua is updated more frequently than JS, you might want to question the wisdom of the current processes.