3 ms·
>expectation to use latest and greatest and be future-proof In javascript (just like in any other programming language) you generally get one or the other. Yo
by Klathmon 11y ago
>expectation to use latest and greatest and be future-proof
In javascript (just like in any other programming language) you generally get one or the other.
You can have the "cutting edge" features or libraries, or you can stay a bit behind and have one that's stable and will stick around for a while.
People are using features of JS that aren't even in the spec yet then getting burnt out when they break in the future? Using a library at version 0.0.3 and getting upset when 2.4.3 breaks something?
There is nothing wrong with using mature systems, and that's why I personally feel all of this "javascript fatigue" is self inflicted. If it is going to be a project you write once then don't touch for 5 years, maybe don't use react 0.15.beta-4 as your library of choice...