12 ms·
"It has been two and a half years since the previous major release of React, which is a long time even by our standards!" As a mostly Python and only occasiona
by simonw 6y ago
"It has been two and a half years since the previous major release of React, which is a long time even by our standards!"
As a mostly Python and only occasional JavaScript developer, it always felt like the biggest challenge in the JavaScript community was how fast everything moved - new libraries, frameworks and ideas would tumble past at the rate of one every few weeks, and it felt impossible to keep up.
I've been feeling that a lot less recently, and maybe the fact that React has been steady for 2.5 years is part of the reason.
- dawnerd 6y agoI second you on that. The number of times I've had to rewrite code because a framework decided to break everything with little warning.. I don't even want to think about it actually. I get wanting to make code better but gesh people, do some planning and figure out a direction to move a project. Also it seems JS devs don't understand semver either. Massive breaking changes in patch or minor versions are just evil.
- onion2k 6y agoI've had similar experiences with JS libraries, but not so much with React. The React team are much better at managing to keep things backwardly compatible than most.
- dawnerd 6y agoAgreed, I'm fairly new to React this year and while it's been a rough learning curve for me it's nice how stable it is considering some of the example code is pretty old and it still mostly works just fine
- jakelazaroff 6y agoI really like the React approach to upgrades: if your app works with version N with no warnings, it will work with version N+1. https://reactjs.org/docs/faq-versioning.html https://reactjs.org/docs/faq-versioning.html
- rilut 6y agoFrom my experience, I think it's the total opposite. Airflow and even Python3 itself breaks on minor version.
- rubber_duck 6y agoBig name libraries and frameworks like React and Angular manage things relatively well and in a similar way to other frameworks in other languages (you could argue about AngularJS -> Angular but if you worked with both frameworks you know that AngularJS was a dead end approach designed for a completely different stack and it just didn't make sense to maintain backwards compatibility or maintaining that dumpster of a code base past it's EOL). A problem in React ecosystem is that it's a rendering library not really a webapp framework so you need to use community provided libraries to fill in the gaps. Those libraries are often maintained by an individual so it's unreasonable to expect corporate SDK approach to development, but unfortunately it leads to a lot of abandonware and rewrites, especially since JS is not very maintainable and it's often easier to rewrite something than to pick up someone else's code.
- skinnymuch 6y agoWhich core web app framework feature’s biggest 3rd party React library has been abandoned in the last few years? Or extensively rewritten to the point of seriously effecting end using programmers? I am relatively new to React. Perhaps all of this happened 3 or more years ago. I know React Router 4 was released in mid 2017. Perhaps I was too new when I looked over the changes between 3 and 4. It didn’t seem as drastic as the general opinion that JS changes like crazy. I looked at the migration guide again. Still doesn’t look too bad. Maybe it would be in a large code base.
- emteycz 6y agoI am developing with React and TypeScript every day for the past 5 years. Everything I did then works now, not a single line of code needed to be changed. There are new ways of doing things that I am extremely happy with (Hooks, advanced types), but the old way is not even deprecated yet.
- rubber_duck 6y agoreact-router, react-router-redux, immutable.js was dead at some point when the only dev maintaining it left Facebook (AFAIK, I don't know if it got resurrected since) and people were just moving to immer.js. These are just on top of my head stuff that I had to replace when starting new projects because I didn't want to start a new project on potentially unsuported libs, there were more but I can't remember the names exactly - been a while since I was boostraping a new project.
- namelosw 6y agoReact is actually pretty decent in terms of upgrading. Also, the idea of semver is more widespread in the JS community and there are things like Angular commits and tools like commitizen. It has a tick-tock pattern so that you can upgrade and having time to fix the warnings. The API changes are carefully crafted. Sometimes there are even migration tools to help you upgrade.
- cel1ne 6y agoThere is just some kind of internal resistance increasing the major-version for a breaking change, especially when that change is just tiny. I have published a library myself and experienced it, going from 2.x to 3.x to 4.x. After you just do it for the sake of semver though, the resistance vanished for me. And the second thing: Never use 0.x.x versions, I think those should have been omitted from semver completely, as they circumvent the entire concept.
- newfangle 6y agoI do feel like react has won
- wolco 6y agoReact won the spa crowd. Lags behind in server side frameworks adoption over Vue. React won the enterprise crowd pushing angularjs out. React hasn't won over the JQuery crowd If you do primary js it probably has. If you only do some js and other things it probably hasn't yet.
- darepublic 6y agoNext.js is a very decent React based SSR framework imo, and not sure vue is more popular
- baddox 6y agoGatsby is another very popular SSR framework that uses React.
- eivarv 6y agoGatsby's a static site generator, isn't it? That's different from SSR.
- floydnoel 6y agothere’s an SSR plugin for Gatsby. also, Next has the option to do SSG.
- iaml 6y agoThere's no reason to pick gatsby over next nowadays, next can do everything gatsby can and in a sane, reusable manner.
- andrewingram 6y ago
- dane-pgp 6y ago> the biggest challenge in the JavaScript community was how fast everything moved If you don't like things moving too fast, then React does seem to be the ideal ecosystem: https://github.com/facebook/create-react-app/issues/9033#issuecomment-662745656 https://github.com/facebook/create-react-app/issues/9033#iss... TL;DR A vulnerability was discovered in a transitive dependency of "create-react-app" and announced back in March, but the one line patch to update the hard-coded reference to the vulnerable version is being held back for a future major version upgrade of the "create-react-app" package. 5 months on and the issue is marked as Closed but the new version hasn't been released.
- danabramov 6y agoTo be clear, the vulnerability has no actual effect on CRA apps. The description says it’s for a DDOS attack which is completely irrelevant because CRA doesn’t use WDS for production environments. (It doesn’t even have a production web server.) While I agree that ideally a release should be cut to satisfy people affected by enterprise requirements, we are looking at a case of an overzealous audit checker, not an actual vulnerability that affects your apps. (Edit: I've cut a release though; see my response in https://github.com/facebook/create-react-app/issues/9033#issuecomment-671847777 https://github.com/facebook/create-react-app/issues/9033#iss...)
- dane-pgp 6y agoThank you for your professionalism and humility. I too would like to apologise for not giving the full context and incorrectly suggesting that the vulnerability might actually affect apps created by CRA. I think that the real concern was not the non-existent security implications (although it's a bad habit to ignore even an overzealous audit checker), but that the release process for CRA seemed to make it very hard to cut new patch releases. Your comment suggests that it wasn't so hard after all, for which I am relieved and grateful, but the policy of expecting people to wait for (and deal with the backwards incompatibility of) major version updates[0] doesn't feel like an industry best practice. [0] https://github.com/facebook/create-react-app/issues/9033#issuecomment-648728724 https://github.com/facebook/create-react-app/issues/9033#iss...
- nicoburns 6y agoReact has actually been stable for much longer than that (say 5 years). There have technically been breaking changes, but in practice these required only minor code changes if any. They've introduced new coding styles (like hooks), but the olds ones still function just fine.
- rhizome31 6y ago> As a mostly Python and only occasional JavaScript developer, it always felt like the biggest challenge in the JavaScript community was how fast everything moved Those of us who were doing Python web dev in the years 2000s might remember that Python went through a similar period where it seemed that every week a new backend framework came out: Zope, CherryPy, web2py, Pylons, Django, repoze.bfg, TurboGears... to name a few. Nowadays it seems that everybody has settled for either Django or Flask. It might not have been as crazy as what happened with JavaScript in the years 2010s but still I tend to see a similar pattern. People try a lot of different things, going in slightly different directions and eventually interesting approaches get identified and communities build up around a couple of solutions. Meanwhile the Ruby community was able to build consensus around Ruby on Rails, with just Sinatra on the side for small projects. I'm wondering if this ability to try many different things might have been the cause for Python building numpy and eventually winning the scientific computing area as well.
- simonw 6y agoI do remember that period very well! https://simonwillison.net/2005/Jul/17/django/ https://simonwillison.net/2005/Jul/17/django/
- raziel2p 6y agoI do think there's a second wave of frameworks coming, because Django/Flask are showing their age a bit. Sanic is/was really popular and I think FastAPI is really promising.
- rumanator 6y agoIt seems that the main difference you're pointing out is Python's transition from synchronous-only/wsgi to asynchronous/asgi frameworks.
- raziel2p 6y agoSanic is indeed just an ASGI version of Flask, though who knows how it will develop in the future - but FastAPI is a whole other beast. Also, Django is adding support for ASGI so no, that's not the main difference I wanted to point out.
- andrewingram 6y agoWe definitely seem to be in an era of stability. My stack of choice (React, GraphQL, Relay, Django) has remained unchanged since late 2015. A few things have changed, i.e. I no longer have to hand-roll my own SSR solution, because things like Next.js exist. But what represents the bulk of my code is largely the same tech as it was 5 years ago.