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

71–80 of 120 posts

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

#71

Post by throwaway189262 »

pedrocx486 wrote: post #58
throwaway189262 wrote: post #54

Earlier quoted context omitted.

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.

I've worked on Angular stuff for years because my employer won't let us switch. Angular uses too much abstraction.

Angular does crazy things to the templates, to the point that trying to build your own UI widgets is a recipe for pain.

Template meta-language is stupid. It's just similar enough to JS that you mess up the syntax all the time and never really stop. Since it's not just JS like JSX there's not good linting support either.

Related, stupid "pet features" and hydra syndrome. Like Pipes. Why does Angular use these weird pointless things when you can do the same thing with JS built-ins? Just so they didn't have to copy JSX? We may never know. And why are there 2 form implementations that both feel half baked? Why is it so bad to instantiate components for testing? Why does it mangle the code to support dependency injection when decorators and DI support don't even actually exist in JS even in ES2018? Why is Polyfills.js such a minefield? I could go on but really, why are so many things half assed and haphazard. It reminds me of Go...

Constant "expression changed after it was checked" errors because the data model change tracking is fundamentally broken

Repeated refactoring of HTML form interop and it still kinda sucks

Major breaking changes on nearly every upgrade that take days to do, even on our small apps.

Crappy documention. There's no usage examples for most of the library, just the Angular version of Javadoc.

Terrible bike shedding by Angular and Material teams. I'm following a bunch of issues and I've never seen one closed. I've been following some of the threads for years.

That was a nasty rant but I have plenty of things to hate about Angular. React on the other hand has a mostly clean core API and doesn't force all this baggage on you. IMO this has spawned a competitive ecosystem where the bad ideas get shaken out. Angular is stuck in the past and feels creaky compared to React development these days.

JSX is the future. It's exactly how MVC frameworks used to work, and it would be popular for templating even if the rest of React didn't exist. Change tracking with props is another. It's simple, it works. Angular change tracking errors are the segfaults of front end dev

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

#72

Post by tW4r »

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 .

I agree, I think works better

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

#73

Post by pjmlp »

newfangle wrote: post #9
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 do feel like react has won

Where?

Over here it is all about Angular and Vue, and this for a minority of projects.

The large majority is done on SSR, CMS based infrastructure with vanilaJS.

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

#74

Post by pjmlp »

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

Given the amount of Angular requests we get, when not doing plain CMS driven projects, that is wishful thinking from React crowd.

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

#75

Post by pjmlp »

adjkant wrote: post #62
pedrocx486 wrote: post #58

Earlier quoted context omitted.

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

https://2019.stateofjs.com/front-end-frameworks/#front_end_f... Versus 2016: http://2016.stateofjs.com/2016/frontend/ Angular is 100% fading, albeit slowly. Seems like a lot of slow moving enterprise companies are still going with it anecdotally. I'd bet on very few new projects opting for it currently, and probably near zero within 2-3 years. As to why, IMO Vue ate Angular's lunch. Single file components did everyth…

That is AngularJS.

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

#76

Post by emteycz »

skinnymuch wrote: post #51
rubber_duck wrote: post #21

Earlier quoted context omitted.

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…

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

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

#77

Post by dmoreno »

pedrocx486 wrote: post #58
throwaway189262 wrote: post #54

Earlier quoted context omitted.

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.

Not scientifically accurate, but Google trends gives a hint. And absolutely not dying, but react keeps growing at angular's expense.

https://trends.google.com/trends/explore?date=today%205-y&q=...

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

#78

Post by eivarv »

baddox wrote: post #66
darepublic wrote: post #48

Earlier quoted context omitted.

Next.js is a very decent React based SSR framework imo, and not sure vue is more popular

Gatsby is another very popular SSR framework that uses React.

Gatsby's a static site generator, isn't it? That's different from SSR.

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

#79

Post by raziel2p »

rhizome31 wrote: post #67
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…

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

I 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.
Post reply on HN