Progressive React
61–70 of 88 posts
Re: Progressive React
#62The more I deal with it, the more I hate React, and the very idea that websites must require Javascript to just show HTML.
If all you want to do is serve up HTML... you don't pick react.
Admittedly this works best on projects that don't require a massively complex interactive front-end, like news sites[0] and data reporting tools. But at some point you can just choose to start hydrating the interactive components in the browser without changing your back-end setup at all.
[0]: https://wildlyinaccurate.com/introducing-a-faster-bbc-news-f...
Re: Progressive React
#63It's funny because scrolling in this article is a stuttery mess (Firefox on Linux).
Re: Progressive React
#64Re: Progressive React
#65It's funny because scrolling in this article is a stuttery mess (Firefox on Linux).
Re: Progressive React
#66The more I deal with it, the more I hate React, and the very idea that websites must require Javascript to just show HTML.
Re: Progressive React
#67It's funny because scrolling in this article is a stuttery mess (Firefox on Linux).
Crashed my phone... (Chrome on Android, though pretty old Sony Experia)
Re: Progressive React
#68Never mind the fact that we're plowing the depths of functional programming, complex data structures and asynchronous wizardry just to make sure that displaying a few bytes of text and flat-shaded borders isn't too slow.
I don't remember GUI programming being that hard in the years before this. At least for these rather simple results. Getting a full DTP platform out on a 20 mhz machine with 4 MB of RAM required some advanced pattern wizardry, but most web UI patterns aren't that complicated. They just aren't helped by the client-server nature and Javascript being Javascript, as much as you wrap it up in the Emperor's new C# clothes.
> Sites have become bigger, more interactive and more complex and this number is still gradually increasing in an upward trend year after year.
Yeah, but is it useful complexity? The whole frontend scene often reeks of "bullshit job" syndrome. To get results customers could live without in a framework not re ally suited for it, we're developing complex tools, even more complex tools to package and deploy them and then have more coaches, trainers, video walkthrough creators and premature optimization providers than ever before.
Re: Progressive React
#69As someone who has web apps in production written in backbone.js, Angular, and React, I can say selectors with Reselect to transform all the data being passed into props, Sagas to manage all async workflows, and Ramda with Redux reducers is pure fire. There is no business logic in components or containers unless it is tied directly to the view and layout, not for the data. It is such an easy way to reason about huge…
Re: Progressive React
#70It's funny because scrolling in this article is a stuttery mess (Firefox on Linux).
For anyone else suffering stuttering, a reminder that most browsers support reader mode which makes it silky smooth again. For Firefox its the page icon in the navbar.
It works great.