lakpan
Joined 3 years ago
Joined 3 years ago
What’s possible though is a better handling of these scenarios. Don’t lock me out of my entire account, but stop the specific service/action breaking the ToS.
A million editors and you pick the least capable. My go-to is a sublime text window, even if ST is not my code editor.
In web extensions you can’t quite use sourcemaps unless you include the sourcemap in the .js file or upload it to your own server
With rollup, I can just ship it as a web extension and it’s still 100% readable.
I’m confident that someone already wrote an extension that does this automatically for every page, and that someone else is writing a Chromium wrapper.
The only thing holding us back at the moment is cost/computing.
Chrome starts a proposal, implements it and “intends to ship” it before anyone really has time to discuss it. Recently (2 months ago?) they introduced a new WebExtension API that nobody cared about nor really understood the need for, but it’s still there, making it look like it’s a “standard”
Are they? I don’t see it. They’re more profitable than ever and are still extremely competitive in multiple markets.
The arguments against this have been the same for decades: Apple is overpriced, Apple’s product are inferior to competition, and yet here we are with large chunks of the market share and larger chunks of market gains.
Some products are stupid, but it’s not like Steve hasn’t pushed dead products out before.