Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React v17.0 Release Candidate: No New Features

reactjs.org

Post reply on HN
Print view View original

51–60 of 120 posts

Re: React v17.0 Release Candidate: No New Features

#51

Post by skinnymuch »

rubber_duck wrote: post #21
dawnerd wrote: post #5

Earlier quoted context omitted.

I 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.

Big 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…

Which 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.

Re: React v17.0 Release Candidate: No New Features

#52

Post by nightski »

oaxacaoaxaca wrote: post #40
Karupan wrote: post #30

I've become increasingly disillusioned with the JS ecosystem over the past couple of years, but React still delivers. I can still chuck it in a script tag and start writing components if needed (without JSX). I haven't really used hooks yet and don't plan to, but as long as "legacy" class based components are supported, I will use them. Thanks for maintaining backward compatibility, which is not very common in the JS…

Just chiming in to say that I too hope class components will continue to be supported. I worry that they'll announce otherwise in a couple years. Class components are so stupidly simple to read and write. I appreciate the work put into function components, but to me they make things unnecessarily complex. Just the fact that they took callbacks and other functions from methods – where things are separate, clean, stand…

You can create isolated functions instead of nested functions wherever you want. Just pass in params instead of using closures. This is entirely up to the developer.

Re: React v17.0 Release Candidate: No New Features

#53

Post by Gaelan »

acemarke wrote: post #42
jameslk wrote: post #39

It's refreshing to see a major release of a frontend library that doesn't completely redo the API (React Router and Angular, take note). I remember there was a time when a bunch of features were being considered to be bolted on to JSX which was going to be called JSX 2.0[0]. I'm glad that never happened. Maybe the next version of React can even remove features, like hooks. 0. https://github.com/facebook/jsx/issues/65

I'd still _loooove_ to have "prop punning", ie, shorthand passing of props based on local variable names equivalent to ES6 object literal shorthand: Doesn't seem too likely to happen at this point, though.

That conflicts with HTML syntax, no? is equivalent to .

Re: React v17.0 Release Candidate: No New Features

#54

Post by throwaway189262 »

wolco wrote: post #31
newfangle wrote: post #9

Earlier quoted context omitted.

I do feel like react has won

React 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.

So glad Angular is dying off. It looks nice on the surface but as soon as you try to do something outside the tutorial it gets nutty.

React is at a great level of abstraction between code and UI framework. It reminds me of the MVC frameworks of olde, which by all accounts were great, just limited because they relied on page refresh for everything

Re: React v17.0 Release Candidate: No New Features

#55

Post by acemarke »

Gaelan wrote: post #53
acemarke wrote: post #42

Earlier quoted context omitted.

I'd still _loooove_ to have "prop punning", ie, shorthand passing of props based on local variable names equivalent to ES6 object literal shorthand: Doesn't seem too likely to happen at this point, though.

That conflicts with HTML syntax, no? is equivalent to .

Which is why the current JSX syntax uses that as a synonym for `disabled={true}`. Agreed that it matches HTML better, but having written an awful lot of `someLongVariableName={someLongVariableName}`, I sure wish I could stop repeating myself there.

Re: React v17.0 Release Candidate: No New Features

#56

Post by untog »

nightski wrote: post #52
oaxacaoaxaca wrote: post #40

Earlier quoted context omitted.

Just chiming in to say that I too hope class components will continue to be supported. I worry that they'll announce otherwise in a couple years. Class components are so stupidly simple to read and write. I appreciate the work put into function components, but to me they make things unnecessarily complex. Just the fact that they took callbacks and other functions from methods – where things are separate, clean, stand…

You can create isolated functions instead of nested functions wherever you want. Just pass in params instead of using closures. This is entirely up to the developer.

You can, yes. But the developer working on the codebase you’re going to inherit might not. Class components are usefully opinionated in that way.

Re: React v17.0 Release Candidate: No New Features

#57

Post by debaserab2 »

danfo wrote: post #38
azangru wrote: post #34

Earlier quoted context omitted.

> Lags behind in server side frameworks adoption What do you mean by this? Which server-side frameworks? Are you comparing Next and Nuxt?

(not GP) with React, declarative JavaScript code can result in HTML. JS -> HTML Server side frameworks (the usual favourites) have existing ways for code to result in HTML. Ruby/PHP/Java -> HTML Vue on the other hand can sit within HTML. So you can sprinkle in client-side logic in the views while still generally going with the grain of your server side framework. https://gitlab.com/gitlab-org/gitlab/-/blob/6cece3f49e…

Does the v-if execute on the server side?

Re: React v17.0 Release Candidate: No New Features

#58

Post by pedrocx486 »

throwaway189262 wrote: post #54
wolco wrote: post #31

Earlier quoted context omitted.

React 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.

So glad Angular is dying off. It looks nice on the surface but as soon as you try to do something outside the tutorial it gets nutty. React is at a great level of abstraction between code and UI framework. It reminds me of the MVC frameworks of olde, which by all accounts were great, just limited because they relied on page refresh for everything

>So glad Angular is dying off.

Uh, I'm gonna challenge you to give a source on that. Your comment sounds extremely biased towards React and dismissive towards Angular. None of those are dying out, I wouldn't we even say they compete directly.

Re: React v17.0 Release Candidate: No New Features

#59

Post by rilut »

dawnerd wrote: post #5
simonw wrote: post #3

"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…

I 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.

From my experience, I think it's the total opposite. Airflow and even Python3 itself breaks on minor version.
Post reply on HN