6 ms·

Actually, yes. The conventional wisdom these days is to do everything in React (or something similarly bloated). Because, you know, users just love seeing a b

Actually, yes. The conventional wisdom these days is to do everything in React (or something similarly bloated). Because, you know, users just love seeing a bunch of grey boxes shimmer and dance on a white background for several seconds before the magic really starts to happen. So any exercise which demonstrates that there just might be an alternative to this philosophy should be applauded.

madeofpalk 3y ago
I don’t think this is the “conventional wisdom”!
- hereforcomments 3y ago
  I've just joined a team recently and had a chat with the head of product. We will work on a tiny internal app, it has 3 pages: sso login page, Excel template upload page where earlier uploaded templates are shown as a card and if you click on them it opens a dashboard: a map with markers, a bar and a pie chart. This is the whole thing. This guy asked what we will use in the front-end. I said react and he was like "amazing, good job, it will be great" and the talked about we should always use react. So yes, there are places where react is used without question. Also, we will use snowflake as a backend while indexing would make everything a lot faster and the budiness logic is done by 800+ line sql (stored procedure).
- arrowsmith 3y ago
  It's been the conventional wisdom at every company I've worked for in the last ~5 years, and I hate it. I ranted about this in another thread a few months ago and I stand by what I wrote: https://news.ycombinator.com/item?id=34857513 https://news.ycombinator.com/item?id=34857513
whoknowsidont 3y ago
> users just love seeing a bunch of grey boxes shimmer and dance on a white background for several seconds before the magic really starts to happen. This has nothing to do with React, this is a placeholder rendering strategy employed by many different frameworks and languages.The rendering strategies are orthogonal to the framework. I've written many websites entirely in React but you'd never know it, because they're all SSG. I've done hybrid SSR + SSG + placeholder/delayed load. I could have done all of that with .NET, Elixir, etc. too because it has nothing to do with the language/framework.

madeofpalk 3y ago

I don’t think this is the “conventional wisdom”!

hereforcomments 3y ago
I've just joined a team recently and had a chat with the head of product. We will work on a tiny internal app, it has 3 pages: sso login page, Excel template upload page where earlier uploaded templates are shown as a card and if you click on them it opens a dashboard: a map with markers, a bar and a pie chart. This is the whole thing. This guy asked what we will use in the front-end. I said react and he was like "amazing, good job, it will be great" and the talked about we should always use react. So yes, there are places where react is used without question. Also, we will use snowflake as a backend while indexing would make everything a lot faster and the budiness logic is done by 800+ line sql (stored procedure).
arrowsmith 3y ago
It's been the conventional wisdom at every company I've worked for in the last ~5 years, and I hate it. I ranted about this in another thread a few months ago and I stand by what I wrote: https://news.ycombinator.com/item?id=34857513 https://news.ycombinator.com/item?id=34857513

whoknowsidont 3y ago

> users just love seeing a bunch of grey boxes shimmer and dance on a white background for several seconds before the magic really starts to happen. This has nothing to do with React, this is a placeholder rendering strategy employed by many different frameworks and languages.The rendering strategies are orthogonal to the framework. I've written many websites entirely in React but you'd never know it, because they're all SSG. I've done hybrid SSR + SSG + placeholder/delayed load. I could have done all of that with .NET, Elixir, etc. too because it has nothing to do with the language/framework.