3 ms·

Been watching this thread all day and I’m dumbfounded no one has spoken up for React with a modern router like found[0]. Once you learn to use these things, mak

Been watching this thread all day and I’m dumbfounded no one has spoken up for React with a modern router like found[0]. Once you learn to use these things, making an SPA is really nice, and you can easily introduce universal rendering which takes your SPA to the next level by rendering it on the server. I find it strange that people talk like server rendered pages with progressive enchancent a la 2013 aka Stack Overflow aka GitHub are easy to make and maintain. It’s 2018 and when you close an issue on GitHub the count doesn’t change until you refresh the page. It’s 2018 and when you go back on Stack Overflow the alerts you just dismissed are suddenly unread again. These are companies capitalized with hundreds of millions of dollars yet they are incapable of making server rendering with progressive enchancement work. It’s not their fault, it’s the technology, it’s busted. Yet for some reason people are lauding server rendering as effective and desirable and capable of producing rich UI that’s sane to build and maintain. It’s not. It’s unmanagable at any scale. With React etc in 2018 all of these problems have been solved, and as I said above, the SPA is not even something to argue about anymore because you can render your app on the client or the server. This whole article is moot. All these problems have been solved and the solutions are free for anyone who has the interest and bandwidth to build products like it’s 2018. [0] https://github.com/4Catalyzer/found https://github.com/4Catalyzer/found

subsection1h 9y ago
> I’m dumbfounded no one has spoken up for React with a modern router like found. You're dumbfounded that developers aren't powering their companies' multi-million dollar websites with tools that have a bus factor of roughly one[1][2]? A couple years ago I was handed a web app built by a team that had used tools with low bus factors. Many of these tools had been abandoned only months after the team starting using them! [1] https://github.com/4Catalyzer/found/graphs/contributors https://github.com/4Catalyzer/found/graphs/contributors [2] https://github.com/4Catalyzer/farce/graphs/contributors https://github.com/4Catalyzer/farce/graphs/contributors
- tendencydriven 9y ago
  What do you mean by a "bus factor"? I'm assuming its related to the number of contributors / contributions over time, but I've never heard the term before. Edit ---- Oh! I get it now https://en.wikipedia.org/wiki/Bus_factor https://en.wikipedia.org/wiki/Bus_factor
- linkmotif 9y ago
  You’re right, of course. But that particular repo was one example. Yes that repo is brand new. But at the same time it’s the product of basically one person’s work. On the other hand you have these multi million dollar companies—if their tech stacks were the end all of stacks, wouldn’t they be able to accomplish what this lowly repo accomplishes? But they don’t. And why? Because this repo stands on the shoulders of many attempts and failures in routing with universal rendering, while GitHub and Stack Overflow are stuck in 2013, when people only rendered on the server, progressively enchanced, and back only kind of worked. Anyway there’s also react-router, which is a project with probably 10k stars. I didn’t cite it because I think it’s not as good as “found”. But it works and will get you back functionality that works in client rendering and server rendering. So if you’re looking for bus factor, react-router has got that in 2018.

subsection1h 9y ago

> I’m dumbfounded no one has spoken up for React with a modern router like found. You're dumbfounded that developers aren't powering their companies' multi-million dollar websites with tools that have a bus factor of roughly one[1][2]? A couple years ago I was handed a web app built by a team that had used tools with low bus factors. Many of these tools had been abandoned only months after the team starting using them! [1] https://github.com/4Catalyzer/found/graphs/contributors https://github.com/4Catalyzer/found/graphs/contributors [2] https://github.com/4Catalyzer/farce/graphs/contributors https://github.com/4Catalyzer/farce/graphs/contributors

tendencydriven 9y ago
What do you mean by a "bus factor"? I'm assuming its related to the number of contributors / contributions over time, but I've never heard the term before. Edit ---- Oh! I get it now https://en.wikipedia.org/wiki/Bus_factor https://en.wikipedia.org/wiki/Bus_factor
linkmotif 9y ago
You’re right, of course. But that particular repo was one example. Yes that repo is brand new. But at the same time it’s the product of basically one person’s work. On the other hand you have these multi million dollar companies—if their tech stacks were the end all of stacks, wouldn’t they be able to accomplish what this lowly repo accomplishes? But they don’t. And why? Because this repo stands on the shoulders of many attempts and failures in routing with universal rendering, while GitHub and Stack Overflow are stuck in 2013, when people only rendered on the server, progressively enchanced, and back only kind of worked. Anyway there’s also react-router, which is a project with probably 10k stars. I didn’t cite it because I think it’s not as good as “found”. But it works and will get you back functionality that works in client rendering and server rendering. So if you’re looking for bus factor, react-router has got that in 2018.