The first time you add a website to your home screen, it installs the website's service worker. You have to use the Internet for that, just as you have to use the Internet to download an application from Apple's App Store.

And I'm curious about what the blockers for even a partial PWA implementation have been during each of these 12 years.

All I've been asking is what features of Grab combined with missing features of PWA likely led to their continuing to choose native apps.

I don't see where I "assume[d] to know better than Grab".

Even when you talk about users, it's only to dismiss them.

I don't understand what people are doing that they need to summarize Jira tickets. They usually aren't very long...

Oh good point, it explains why the article feels so wanderingly pointless.

I think if my coworkers were writing Jira tickets that were too unreadable, I would ask them to write shorter tickets.

It is surely meaningful that a leadership council and directors got funding before the people who were actually doing the work maintaining the code.

I should have said "the financial industry."

Who said that engineers love indispensable things?

My observation is that engineers like well-engineered things. I've never heard any engineer anywhere say they like indispensable things. What was the source of information, Gemini?

I'll be happy if we make it through the next three years without a world war.

In the post-chat-gpt world, if you want to SEO, you need to write for chat-gpt.

Even apart from costs associated with proprietary software, the other reason to avoid vendor lock-in is to avoid self-propagating backdoors in the compiler. Ken Thompson described how to make such a backdoor with C in his 1983 "Reflections on Trusting Trust" speech. David A. Wheeler described "diverse double-compiling", a defense against compiler backdoors that relies on the existence of independent implementations of a language. Stable Rust doesn't have that because it's such a moving target, with widely used programs relying on language and library features less than half a year old.

See also "Reflections on Rusting Trust" by Manish Goregaokar

They knew this and decided to maintain Perl 5 alongside Raku (formerly known as Perl 6) for what is looking to be noticeably longer than the 11-year transition from Python 2 to Python 3.

Seems you don't care about users either. There is nothing in your post that shows you even thought about them. You're not an engineer, you're just an asshole.

Engineers think about user requirements.

Wow, just take a statistics class. You are embarrassing yourself.

If done correctly, the inclusion of Rust wouldn't break anything. And yet here we are.

Clearly things are not being done correctly (ie, with established engineering practices). If he actually had an engineering license, it would be revoked because of decisions like this.