41–49 of 49 posts
I never, ever bothered to learn React. Stuck with .NET/C#. If I have to write web UI, I use Angular, Blazor, and Razor MVC. React never made any sense to me, and the more I saw people using it, the more it reconfirmed my belief that it was a no-go. Usually, people win if they do the opposite of what the mass is doing :)
.NET and C# are the opposite of what everyone is doing?
> React’s logical model of recreating the UI on change of state is incredibly difficult to do right at scale. What's much more difficult at scale is doing this without React. In the old days when building a complex front-end web app, your app would slowly devolve into complex web of event handlers changing the DOM, and you'd eventually arrive at the conclusion that you'd eventually arrive at the conclusion that centr…
If you'd worked in UI generally the popular libraries of the time like backbone, angular 1, ember, knockout, etc. clearly were flawed and chaotic (with apologies to mithril and a few others.) and would obviously quickly spaghettify.
These days between template literals, indexeddb and a simple library like morphdom you can write fast, predictable, queriable UI's that are offline first, persistent and easy to refactor and decouple components if your data model changes.
The problem with front end UI in js was that instead of being logical and operating off of some kind of persistent DBesque data model that you could query and increment.. you were stuck with ephemeral data and your UI was built off of arbitrary API calls that disjoint the consumption of and hide the underlying data model.
Rendering complex UI without the backing of proper data tools will not be clean or comprehendable over time.
I see the point but I think the article is overplaying its hand. Sacrificing performance for a cleaner programming model is a reasonable tradeoff, it's weird that it's being criticized as though it were a matter of principle. I'm very much a backend person and I don't like React either -- as far as I'm concerned raw HTML on a webpage as God intended peak UI -- but if you're writing full webapps you're going to need s…
Then you are the right audience for something like HTMX.
This seems wrong in many different levels. Not only React is getting faster, better, and more simple, but also is still the most adopted and the fastest growing web framework.
> React’s logical model of recreating the UI on change of state is incredibly difficult to do right at scale. What's much more difficult at scale is doing this without React. In the old days when building a complex front-end web app, your app would slowly devolve into complex web of event handlers changing the DOM, and you'd eventually arrive at the conclusion that you'd eventually arrive at the conclusion that centr…
React was the first front end js framework that passed the smell test, it just looked right. If you'd worked in UI generally the popular libraries of the time like backbone, angular 1, ember, knockout, etc. clearly were flawed and chaotic (with apologies to mithril and a few others.) and would obviously quickly spaghettify. These days between template literals, indexeddb and a simple library like morphdom you can wri…
React is the new Apple :)
Despite that, I actually quite like writing react in some sense - I prefer state in React to Svelte, even though I like where svelte is trying to go more.
I do absolutely hate some aspects of JSX - the nested ternaries are brutal and quite horrible IMO, so:
My ideal framework for the data work I do is probably a compiled (useMemo for performance is just inexcusable, sorry) react for the UI knobs, with Svelte components inside it for laying out the data
This seems wrong in many different levels. Not only React is getting faster, better, and more simple, but also is still the most adopted and the fastest growing web framework.
That's kinda like saying WordPress runs 40% of all websites....it's not really a testament to its quality, it's just what everybody knows how to build and deploy.
Earlier quoted context omitted.
I never, ever bothered to learn React or .NET/C#. Stuck with C/C++. If I have to write web UI, I don't. React and .NET/C# made sense to me but are nauseating abominations of mediocre corporate tech, and the more I saw people using them, the more it reconfirmed my belief that they were a no-go. Usually, people win if they do the opposite of what the mass is doing :)
Which version of C++ ? Love the comment.