3 ms·
> When we introduced a library for a new project Great, a real data point! From this and previous comments, I'm guessing the library was React? And from anothe
by porker 11y ago
> When we introduced a library for a new project
Great, a real data point! From this and previous comments, I'm guessing the library was React? And from another comment on this page, you haven't bolted-on multiple libraries for form handling, routing etc.
A few questions:
* What is the projected lifetime of the new project?
* Will the code be updated continuously (vs write once & freeze)?
* What does your ecosystem around React look like?
* What library/framework were you using before which you replaced with React?
* Have yoiu committed to using React on new projects for the next.. 24 months?
It'd be great to learn more, as it sounds like a non-Facebook scale project, i.e. more relevant to most of us...
AFAICT no one in this thread is saying they don't like React, or if $Company paid them to learn it they wouldn't (paid learning time, what's not to love?). It's about the pace of change, reinvention, and expectation to use latest and greatest and be future-proof.
- 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...