Wikipedia officially requires articles to summarize their sources from a neutral point of view. However, Wikipedia did become overtly political with the PROTECT IP blackout of January 18, 2012, in protest of a proposed law seen to threaten Wikipedia's existence.
And you have not considered to enter offline-first, the service worker API has to load?
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.
Again, Grab has been doing this for 12 years.
And I'm curious about what the blockers for even a partial PWA implementation have been during each of these 12 years.
PWA is not new and they have chosen native apps.
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.
But most of us did not assume to know better than Grab unlike you.
I don't see where I "assume[d] to know better than Grab".
It's the Rust Foundation Maintainers Fund, "an initiative we'll shape in close collaboration with the Rust Project Leadership Council and Project Directors
It is surely meaningful that a leadership council and directors got funding before the people who were actually doing the work maintaining the code.
Bankers in America at least don't really do that. What you're thinking of are large investors. People with net worth over 500 million.
I should have said "the financial industry."
a genuine acceleration of discovery. It's the quiet kind of progress engineers love — invisible, but indispensable...
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?
The main reason that people worried about a spec in the past was to avoid vendor lock-in. An implementation which is available under a public license is a good solution to that problem also.
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
Perl 6 was released in 2015 and was even less compatible with Perl 5.
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.
My mother is a fish. - William Faulkner
