Email or username:

Password:

Forgot your password?
samir, talks too much

Said it earlier, but I want to say it again.

If you are copying Google after, I dunno, 2008, or Facebook after 2012, or Netflix after 2016…

You are not copying a successful technology company. You are copying a gigantic corporation that makes most of its money through inertia, lobbying, and monopoly power.

Google didn’t use Kubernetes when it was a wee little search engine. Facebook didn’t use React until after it wanted to own the entire web.

You probably don’t need them either.

8 comments
Rich Felker

@samir And all of them had products that *stopped working* around the time they made those changes.

Rich Felker

@samir React literally turned Facebook's web app from the best ux ever to appear on a website, with actions reflected immediately and consistently, on 2006 hardware, into glitchy garbage that's unusably slow on 2020 hardware.

LisPi

@dalias @samir Was it really that way? I never used it so I don't actually know.

Rich Felker

@lispi314 @samir Yes. It was ultra light ajax and basically the first major site to use it to have replies and other actions have immediate effect on the page rather than having to do a klunky reload.

Rich Felker

@lispi314 @samir Then they rewrote it entirely as a client side web app where all the rendering, rather than changes by user action, were implemented in js with lots of round trips to server and a heavy client side data model outside the DOM. It's completely analogous to difference between how a shell with readline works vs how curses works.

Rich Felker

@lispi314 @samir Google did a similar rewrite to Gmail around the same time with exactly the same effects. Went from fast on 2006 hardware to painfully slow on much later hardware, and worse UI.

Rich Felker

@lispi314 @samir It's really a shame that this isn't well documented anywhere, only existing in the memories of folks who experienced it. I wonder if copies of the js they served back then ever got saved anywhere...

Go Up