761–770 of 866 posts
I'm not a front end dev and only use JS stuff time to time for small personal project. There is so much JS framework out there that appear and disappear so fast. I don't know if we can call it innovation. I have the impression they just reinvent the wheel with so little value added. I prefer to keep on React at least it will not disappear the next time I will do some change on my project.
Like which ones?
The javascript people should stop innovating for a couple of years. To much innovation that lead nowhere. How many ways can one build a web javascript project? Browser people should pick up slack and start developing sane components for the web. How about a backend-supporting combobox, or a standardized date picker across browsers? Then we wouldn't need to constantly innovate how we manage the state of those fundamen…
How many ways can one build a web API? Why are there hundreds of options to build one? Why do people keep inventing new ones, while the problem has been solved 20 years ago?
Earlier quoted context omitted.
>I think it's very hard to argue that React is effective or well designed. This is a foolish take. React is the reason the modern web is as usable as it is. Anyone who contests otherwise is simply ignorant of web development history. >(and even Netflix is moving away from React They're not moving away from React, they're doing pure SSR with it. https://react.dev/reference/react-dom/server/renderToPipeabl... You don't…
> This is a foolish take. React is the reason the modern web is as usable as it is Theres at least one foolish take here Come on think of the 100s of comparable FE frameworks…
What are we comparing? What is there to compare?
Earlier quoted context omitted.
Go read pg’s comments on downvoting. HN has always been fine with using downvotes to signify disagreement.
> Go read pg’s comments on downvoting. Hmm. That sounds an awful lot like "It's true! Google it!"
From pg in 2008.
>I think it's ok to use the up and down arrows to express agreement. Obviously the uparrows aren't only for applauding politeness, so it seems reasonable that the downarrows aren't only for booing rudeness.
Switching to Svelte could be a massive W for a small organization, they'll get inundated with a flood of highly motivated, skilled ex-React developers. Also if react is as probablamitc as people say (I'm veteran of the Angular/Angular.js transition wars so i don't know whats going on as much). If svelt et co. it helps a business not only achieve greater speed but maintenability long-run it's a competative advantage a…
A lot of the issues stem from the fact that Meta was backing React for so long (before it got purchased by Vercel), so it always had a ton of resources dedicated to it which helped win the mindshare. It's like that saying, "No one ever got fired for picking Oracle" or however it goes. The other frameworks (except for Angular) are simply too small when compared to the massive coffers backing React. I mean, Vue is by n…
Earlier quoted context omitted.
HTMX is the antidote to React and is allowing many green shoots to show through - my favourite is https://harcstack.org … but there are many alternates in many server side languages (disclosure: i am the author)
Looking at the example on the front page, I don’t see how you can look at that and think it’s better than react.
If you want to write HTMX / HTML in a componenty and functional way then HARC stack gives you that for Raku. I grant that Raku is a step change if you haven't seen it before and that there are some awkwardnesses in the example that could be ironed out.
You may prefer PyHAT, FastHTML (Python), HARM (Rust), GOTTH (Golang) and so on...
Earlier quoted context omitted.
Hooks are magic syntax without any doubt. All magic syntax is made up of non-magic parts, that's kinda the point. The way you know it's magic is it shatters the principle of referential identity, which tells you that a variable is itself. It pretends you can use a simpler mental model but you really cannot and must not.
You can write const [a, b] = useState('x') in vanilla js and typescript. Hence it is not magic syntax .
React reactive framework: - are you moving a slider? lets re-render the whole tree every frame - oh you didn't want to re-render the whole page? shoulda used hooks ;) Modern reactive framework: - looks like your slider is only updating one value on the page, let me surgically update that for you. no sweat ;)
With the React Compiler, this isn't the case any longer.
How about simple proposition: I want to spend time on MY application logic not on "React code" aka hooks, resolvers, providers, etc etc etc?
Earlier quoted context omitted.
So JSX is pure Javascript and not, say, a dialect of XML embedded in JS? Because it sure looks like the former even though it compiles to the latter. React isn't Javascript. It's a franken-language that looks superficially like a mix of JavaScript and XML whilst following the rules of neither. That's why there is such a thing as a React compiler - a good sign that you're not writing JS, which doesn't have compilers.…
I can’t recall a single time where I would want to put JSX in an „if” statement.. In fact I can’t recall a single time where I would want to use JSX in a different context than the return value of a render phase. So from my personal experience the things you mentioned are non-issues in practice. Do you have a different experience?