RFC: Intent to Ship React 18 • Hacker News Board

Re: RFC: Intent to Ship React 18

#71

Post by e40 » Fri, Mar 25, 2022, 7:52 PM UTC

pohl wrote: post #44

linkgoron wrote: post #22

Earlier quoted context omitted.

Hooks are not simple at all, are very error prone, and definitely do not put the user in the "pit of success". JSX is terrific, but React has only gone backwards since classes IMO.

Not a react fan, here, but hooks are so much better than pre-hooks react. Not sure why anyone would want to go back.

If you were choosing a framework today, what would you use?

Re: RFC: Intent to Ship React 18

#72

Post by pohl » Sat, Mar 26, 2022, 4:39 PM UTC

e40 wrote: post #71

pohl wrote: post #44

Earlier quoted context omitted.

Not a react fan, here, but hooks are so much better than pre-hooks react. Not sure why anyone would want to go back.

If you were choosing a framework today, what would you use?

I wouldn't work in the browser at all. I'm liking SwiftUI a lot.

Re: RFC: Intent to Ship React 18

#73

Post by e40 » Sat, Mar 26, 2022, 7:09 PM UTC

pohl wrote: post #72

e40 wrote: post #71

Earlier quoted context omitted.

If you were choosing a framework today, what would you use?

I wouldn't work in the browser at all. I'm liking SwiftUI a lot.

Is it really cross platform?

Re: RFC: Intent to Ship React 18

#74

Post by sophiebits » Tue, Mar 29, 2022, 9:00 PM UTC

richeyryan wrote: post #63

hn_ltl-ftc wrote: post #32

'useSyncExternalStore()' -- Gack! Now...that "little" it's-not-a-framework-it's-a-library whose scope is supposed to be confined to just the "view" part of MVC (by which I mean: "React") is inserting it's tentacles (along with a quirky architecture and proven to be error-prone coding patterns, cough, hooks) into the _model_. And it's already corrupted (at least partially) the "controller" part of MVC through React's…

React went from v0.14 to v15. The rationale was the library was stable at that point so they could switch to major versions. Why they went directly to version 15 rather than 1.0 is admittedly a bit odd. I guess it was marketing in the same vein of Java 1.4 to Java 5.

We didn't want a big hubbub around a "1.0" release, since we realized React was effectively already stable at that point and the changes from 14 to 15 were no more dramatic than from 13 to 14 or 12 to 13.

Re: RFC: Intent to Ship React 18

#75

Post by pohl » Fri, Apr 01, 2022, 5:00 PM UTC

e40 wrote: post #73

pohl wrote: post #72

Earlier quoted context omitted.

I wouldn't work in the browser at all. I'm liking SwiftUI a lot.

Is it really cross platform?

Not sure what you mean by "really". I guess I have heard some use of that term to mean that it works on watchOS/macOS/iOS/iPadOS/tvOS. In priciple one could create implementations on other platforms, but no one has (beyond toy examples).