throwawayy1001

> The concept is called 'optimistic updating' and the intent is to make the UI 'feel faster' by assuming a positive response from the back-end, and only reverting when things go awry. Given the vast majority of messaging attempts will complete successfully, it's easy to see why the interaction pattern is used.

It's easier than making the UI and server faster for sure, I'm just not sure why engineers don't insist of fixing things the right way.

I think you’re missing the bigger picture here, google customers are marketers not gmail users.

The worst thing that google does imho is to subsidize YouTube, Gmail and other products using advertising money. They’re effectively selling your data to marketers while killing competitors.

You’re not a consumer though, you’re the product.

Google needs to sell eyeballs, so it creates products for free (subsidized by ads) and along the way destroys competition.

Google used its other monopoly, in search to aggressively promote chrome.

“Upgrade to a safe browser”.

They always use their monopolies (video, search, maps) to venture into different markets.

Google is an Adtech company.

> What's the best way to blame / troubleshoot a bad plugin?

You don't do that if the plugin is provided for free, you can just say "thanks" or "no thanks", just don't use it / develop your own.

Just take a step back and look at it, you're combining HTML, SQL and JS, on the fucking server.

Personally I took a break from frontend work, I'll circle back in a few years once web assembly is ready.

The JS ecosystem is insane once you take a step back and look at it.

> What is going to be the limit?

He suggests 1mb, personally I still think it is too much.

> How I, as a developer, make sure my website works everywhere?

1mb for a single page isn't enough?

> What with sites that use a lot of code but still work fast?

It's fast if the resources are near your device (CDN), most websites don't do that at all.

U ok boo?