The 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.
Progressive React
31–40 of 88 posts
Re: Progressive React
#32Start by making your blog not crash android chrome.
Seriously it kills chrome on Android for me like nothing I've seen since those pop ups that you couldn't escape were popular.
Re: Progressive React
#33Earlier quoted context omitted.
If it weren't for Rails then maybe those small businesses would not be as successful as they are and wouldn't be around now. Rails is definitely more niche but it's still a great framework IMHO and it's not dead. Still gets feature updates to this day.
Hope it is not dead. I still haven't taken the time to learn it yet.
It's not bad, the ecosystem makes it good.
Re: Progressive React
#34As 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 amounts of data coming into the system from lots of different places. For performance, everything gets memoized based on object references. Using the immutable data structures in the store, Reselect keeps the transformed data cached with memoization until the object reference is changed in the store.
Re: Progressive React
#35It's funny because scrolling in this article is a stuttery mess (Firefox on Linux).
Yeah, this made my whole browser lag (buttons-shading-five-seconds-after-hover-level lag). FireFox Quantum on Windows 10 with a pretty badass CPU. Also slow in Opera. Also slow in Vivaldi. And it crashed Chrome Canary. For a web-tech post, this is pretty fucking bad.
Works fine in Firefox in iOS...
Re: Progressive React
#36Is that site crashing anyone else's browser? I'm using chrome on Android and it kills my browser every time.
It's crashing Samsung Internet on my Pixel 3.
Re: Progressive React
#37Earlier quoted context omitted.
Fear is the path to the dark side. Fear leads to anger. Anger leads to hate. Hate leads to suffering. Jokes aside, everything has its place. You're still allowed to hate it though. For example, I hate Redux because everyone uses it for every React app and it's got boilerplate up the wazoo. Just know that if you "hate" things, though, you won't learn as much in life, like I won't learn how to use time travel debugging…
I’m not sure this is true. For example, what can I learn from JS that isn’t in better languages? In tech we have this weird situation where many things become popular without good reason. It’s ironic, because a group of people (nerds) who think they are the epitome of rationality are actually the opposite: we make very emotional decisions when we could be entirely rational, as we have access to data other fields do n…
Frontend doesn't always mean using JS. You can use a well-designed, modern language like ClojureScript instead that isn't anything like using JS, yet nevertheless has the same access to the browser.
Re: Progressive React
#38It's funny because scrolling in this article is a stuttery mess (Firefox on Linux).
Ironic indeed, but then the blog itself doesn't use React, the slowdown most likely comes from some utility library[1].
The advice in the article may not be discredited, but this shows that learning basic profiling should come before obsessing over framework-specific optimizations.
Re: Progressive React
#39Re: Progressive React
#40As 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…
I’m mostly with you there but I’ve found saga to be a double-edged sword. The library offers some KILLER features and when you’ve got the right use case, it’s perfect, but it’s so easy to abuse. Because it does so much, I found myself putting more and more responsibilities on it and wound up with some very magical feeling, hard to troubleshoot code.
What changed everything for me was adding GraphQL and getting the majority of my API communication and data storage out of redux. Now, sagas and redux are further down the list of tools I reach for, complexity is way down across the board, and the sagas and reducers that’s remain are more narrowly scoped and easier to reason about and maintain.