Live data from Hacker News

Rebuilding our tech stack for the new facebook.com

engineering.fb.com

451–460 of 489 posts

Re: Rebuilding our tech stack for the new facebook.com

#451
post #412
post #265

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…

Under the document-like school of thought, less "engineers" would need to be employed. Also, less computing resources would be required on both the client side. Money, not to mention time, could be saved. Perhaps application-like school of thought probably allows for more user manipulation. metrics and tracking.

Not sure about the resources part. One key point in having app like interactions Is that you forego the complete page request/render cycle a document oriented implementation requires.

Re: Rebuilding our tech stack for the new facebook.com

#452
post #343

Earlier quoted context omitted.

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…

Really? I assume you don't have slack installed on a Mac then eh? What a horrendous piece of shit.

I’ve had Slack running on multiple Macs for years. I have plenty of complaints about Slack, but none involve performance. What’s the actual complaint? Do people just look at their memory usage and see Slack taking a lot, and if so, is that actually a problem?

Re: Rebuilding our tech stack for the new facebook.com

#453
post #343

Earlier quoted context omitted.

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…

> They work fine for me. They generally work fine. They just annihilate battery life and processing capacity while doing so.

I’ve never had any noticeable issues with that, and I’m almost always running and heavily using VS Code and Slack on my Macs.

Re: Rebuilding our tech stack for the new facebook.com

#454
post #414

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?

I got it-and I did not opt in, it just appeared

Re: Rebuilding our tech stack for the new facebook.com

#455
post #265

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…

[deleted]

Re: Rebuilding our tech stack for the new facebook.com

#458
post #265

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…

I'm currently reading "The Dream Machine", and it makes me instantly go back in time and imagine reading the same comment on discussions around "batch mode" vs "time-sharing" and the development of CTSS [1].

[1]: https://amturing.acm.org/award_winners/corbato_1009471.cfm

Re: Rebuilding our tech stack for the new facebook.com

#459
post #122

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…

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?

Angular

Re: Rebuilding our tech stack for the new facebook.com

#460
post #387

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).

Yeah they sure are driving me to the app. The Apollo app that is.
Post reply on HN