431–440 of 489 posts
Earlier quoted context omitted.
No, the problem isn't that the new FB acts like an app, the problem is that it's clunky as hell. It's like a bad copy of "the new Twitter" and even Twitter isn't really good. The only end-user software from FB is Messenger Lite. It's quick and does what I expect it to do. Even the voice chat is good and I didn't expect a lite version of a messenger to have it.
Is the new FB even live yet?
Did they fix the "back" button? (I.e. if you click a link in the middle of a feed, then "back", do you get back at the same position in the feed?)
(Source: Was involved in early planning for the rewrite and fixing the Back button was one of the primary goals.)
I understand the new stack is React + Relay, but what was the old stack?
I'm actually really surprised by the number of comments in this thread about how the new redesign is slower. I've had it since yesterday and it genuinely feels much faster and more responsive than the old Facebook UI - though, to be fair, that's not a huge accomplishment give that the old UI would take forever to finish painting or respond to input. I'd consider it a success, especially when compared to the disaster…
Considering Facebook engineering has gone into detail about how the new site is much faster and transmits much less JS and CSS, I would be a little surprised if the opposite is true. I tend to not implicitly trust HN comments about things being extremely slow, because for whatever reason there are so many of these complaints I’ve never experienced myself. I still haven’t even had performance problems with Electron ap…
I'm actually really surprised by the number of comments in this thread about how the new redesign is slower. I've had it since yesterday and it genuinely feels much faster and more responsive than the old Facebook UI - though, to be fair, that's not a huge accomplishment give that the old UI would take forever to finish painting or respond to input. I'd consider it a success, especially when compared to the disaster…
It’s karma mining. It’s the same people who think frameworks are dumb and that JS is a terrible language and that codes of conduct are controversial and that you can build FB in a weekend with, at most, ten engineers I really have no clue what they do for a living Anyone who was working in the jQuery days knows exactly why the whole industry moved toward SPAs. It’s disingenuous to say it was just a millennial whim an…
I've always assumed SPAs were partially driven by it historically being difficult to combine server side and client side rendering with a single shared code base more than anything - so much of the early stuff ended up in people essentially having to maintain two entire sites between front and back end rather than just one.
Earlier quoted context omitted.
Let’s go on this tangent, why is Reddit’s frontend so sluggish and lacking quality of life improvements that should be in place by now? Surely they are hiring world-class devs, so what’s holding them back?
It's by design. Reddit doesn't want you using the website. They want you to download the app. As numerous annoying popups and notifications will tell you when visiting the website (especially on mobile).
I recommend everyone the old.reddit.com experience while it's still available. There's browser plug-ins that force the subdomain everywhere on reddit
A big point of contention in the comments here lies around the concept of what a website should be. A school of thought in web development believes the web to be the next frontier in application development. For them it makes sense that websites like this feel and act like apps, both as an end-user (animations, transitions without full-page reloading, rich dynamic content, etc) and as a developer (client-side state m…
Perhaps we should split the web into two worlds. Create dedicated browsers for just enriched document etc. Add some sort of constraints on what the browser can do, and how much control is removed from the user.
But seriously, where do you draw the line between enriched documents and apps?
CSS? JS used for styling? d3 for visualizations? WebGL?
Websites have gotten so bloated that the only sane future I see is serving people unix + x in wasm.
A big point of contention in the comments here lies around the concept of what a website should be. A school of thought in web development believes the web to be the next frontier in application development. For them it makes sense that websites like this feel and act like apps, both as an end-user (animations, transitions without full-page reloading, rich dynamic content, etc) and as a developer (client-side state m…
Perhaps we should split the web into two worlds. Create dedicated browsers for just enriched document etc. Add some sort of constraints on what the browser can do, and how much control is removed from the user.
I'm actually really surprised by the number of comments in this thread about how the new redesign is slower. I've had it since yesterday and it genuinely feels much faster and more responsive than the old Facebook UI - though, to be fair, that's not a huge accomplishment give that the old UI would take forever to finish painting or respond to input. I'd consider it a success, especially when compared to the disaster…
It’s karma mining. It’s the same people who think frameworks are dumb and that JS is a terrible language and that codes of conduct are controversial and that you can build FB in a weekend with, at most, ten engineers I really have no clue what they do for a living Anyone who was working in the jQuery days knows exactly why the whole industry moved toward SPAs. It’s disingenuous to say it was just a millennial whim an…
Writing code instead of playing with legos?