4 ms·
Sadly it's a shrinking list and as sites replace static content with things like React it's shrinking even faster. Good: HN works well and handles the downgrad
by koolba 8y ago
Sadly it's a shrinking list and as sites replace static content with things like React it's shrinking even faster.
Good: HN works well and handles the downgrade gracefully (ex: upvoting becomes a POST rather than AJAX).
Bad: The original Reddit site works ok but the new React based one one fails miserably as it shows a loading screen that never changes.
- StellarTabi 8y agoReact is actually capable of sever side rendering, in fact one of the Reddit announcements specified that React's SSR was a key factor in choosing it. I'm curious why they're not using it? The new site is still in beta though.
- TeMPOraL 8y agoProbably because React having this capability was enough to silence the opposition, without actually committing to using said capability. (Also, they probably save money on electricity by externalizing more and more processing to users.)
- madez 8y agoThe new reddit interface is horrible without JavaScript. One can get back the good one under old.reddit.com
- oldcynic 8y agoThe new reddit interface is horrible period. Even with JavaScript on.
- tannhaeuser 8y agoThe new Reddit React site hijacks right-click so you can't even open your responses/user page in a separate tab. Fail. This is how Slashdot.org lost their user base. Who in their right mind would use React for a content-based site? But reddit seems to know they suck at websites: you can still access https://old.reddit.com/r/<whatever> https://old.reddit.com/r/<whatever> and even https://old.reddit.com/r/<whatever>/.compact https://old.reddit.com/r/<whatever>/.compact for the old site and the old old site.
- p49k 8y ago> Who in their right mind would use React for a content-based site? People who are also writing content-based apps and want to write once but still obtain native speeds on mobile? The lack of right-click functionality is just bad design, not React's fault.
- TeMPOraL 8y ago> obtain native speeds on mobile With browsers and heavy JavaScript frameworks? That's an oxymoron right there. The truth is, people/organizations doing this simply put other concerns above user experience and friendliness.
- SmellyGeekBoy 8y ago"Native speeds" in this case meaning "needlessly slow". But at least it's consistently slow across devices!
- tannhaeuser 8y agoAre you talking about Reactive Native? Sounds good on paper, but it's just as fast or slow as a browser because it is a browser, and is far from creating a native app experience on either iOS or Android because it tries to do animation on a JavaScript-style single-threaded execution model among other things. What content-based apps do you have in mind? The Reddit app nobody is using because it doesn't add value to the web site, and which Reddit keeps nagging about in the most annoying way possible (thereby signaling users to never ever install it)? React is fine for browser-based line-of-business (and I guess also collaboration) apps; for content, not so much because you have to go through hoops to parse content into React's vdom [1]. [1]: https://stackoverflow.com/questions/50420248/how-to-parse-a-string-containing-html-to-react-components/50526629#50526629 https://stackoverflow.com/questions/50420248/how-to-parse-a-...
- StellarTabi 8y ago> Reactive Native [...] because it is a browser Reactive Native's primary selling point (and nature of existence) is that it uses native components instead of wrapping a webview. This is the most obvious, relevant, and hyped detail of React Native. So your statement, "React Native is a browser" implying the same performance penalties as visiting as a website or using Cordova/PhoneGap, is false.
- JoshMnem 8y agoWhen old reddit goes away, there will still be this: https://github.com/michael-lazar/rtv https://github.com/michael-lazar/rtv I think there needs to be a movement to bring the WWW back to basic, readable, low-JS, animation-free, content-based sites.