Random thought after reading: I wish macOS / iOS / iPadOS would have a version without tons of new features.
Remember Snow Leopard? I miss that.
The version that you wipe your main user account if you used the guest account?
React v17.0 Release Candidate: No New Features
41–50 of 120 posts
Re: React v17.0 Release Candidate: No New Features
#42It'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:
Re: React v17.0 Release Candidate: No New Features
#43"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…
> 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#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.
Re: React v17.0 Release Candidate: No New Features
#44It'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.
While not as sexy, you can do:
Re: React v17.0 Release Candidate: No New Features
#45Amir Articles is home for learning blogging, knowledge of Games, and Best Articles in different categories for free.
https://amirarticles.com/
Re: React v17.0 Release Candidate: No New Features
#46I wish this approach to be followed by all major repos and maintainers and become a new trend across all the tech industry.
By creating `bridge` release, the React community created a safe, well know and stable release that works as bridge for the upcoming complex, feature rich, release.
So: Complex Release -> Stable `bridge` Release -> New Complex Release.
Anyone can stay as long as they want in the bridge release, others can quickly move forward to the next release cycle.
Re: React v17.0 Release Candidate: No New Features
#47No new feature, yet contains breaking changes.
As stated in the post, the breaking changes are intentionally minimal. For example, we haven't removed any of the APIs that were originally slated to be removed in 17.
This is actually amazing, by making the next release with only breaking changes, and without new features, devs can focus strictly on what needs to be fixed.
Allowing code to be properly ready and tuned for the next major release. Where the new features will be actually introduced, hopefully, without new bugs.
Re: React v17.0 Release Candidate: No New Features
#48Earlier 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.
Next.js is a very decent React based SSR framework imo, and not sure vue is more popular
Re: React v17.0 Release Candidate: No New Features
#49Earlier 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.
While not as sexy, you can do: There's a lot of "gets you most of the way there" hacks with JSX that will fill most needs. Where as you can imagine the incredible cacophony of screaming developers who maintain TypeScript, Preact, IDEs, etc. that would be incensed by breaking changes to JSX introduced just to solve some inconveniences.
Trust me, I'm well aware of both of those facts :)
Doesn't mean the syntax _can't_ change . After all, the `` shorthand syntax for fragments was added via cooperation with the Babel and TypeScript teams, and the work on the new `jsx()` replacement for `createElement()` is going the same way.
Re: React v17.0 Release Candidate: No New Features
#50It'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 bet a lot of money that the next version of React will not remove Hooks.