Post
Omg commentary from someone who was there at Google! I was going to get around to Omaha but it's possibly too in-the-weeds. It's unfortunate so many rely on weaker less mature and secure update system alternatives to it, but they are dumb-simple. bsky.app/profile/h.ol...
We actually started this with the Windows Google Talk client. We wanted a native app that had a lifecycle similar to the web. The update code got pulled out as a project called Omaha (github.com/google/omaha) and was then used in Chrome.
Yes! How Google taking absolute end to end ownership of update results was an incredible bar to raise. No more blaming users they hit the update button when something breaks, or didn't when they were hacked. You have to own the entire lifecycle including breaking changes. bsky.app/profile/h.ol...
Of course! More lore: Auto update is *hard*. If you get it wrong you either strand users on old versions or turn it into a DDOS against your update servers.
Most people talking about Chrome's innovations would first highlight the security sandboxing and V8 JavaScript, but it was truly a revolutionary epoch in ecosystem norms. Or, why don't you hear about PDF hacks much anymore? ~Adobe adopted Chrome sandbox code. (Fun fact IE7 had sandbox long story)
3 reposts95 likes