4 ms·
More walled gardens. Hooray. This is why we need WASM and web-first development. If the platforms won't empower us to develop and distribute without levying th
by echelon 6y ago
More walled gardens. Hooray.
This is why we need WASM and web-first development. If the platforms won't empower us to develop and distribute without levying their tax, we need to take our business back to the open web and spend our money on making it the best platform.
Besides, it's a nightmare to have to develop for every single platform when the web is universal. Platforms should pay the cost of making things work on their devices and operating systems, not tens of thousands of independent developers and engineers paying this price N-many times for each walled garden.
We also need to get Google's claws out of the open web (AMP, standards balkanization, etc.)
- tonyedgecombe 6y agoThe cure is worse than the disease. We will just end up with a handful of companies holding our data to ransom.
- recursive 6y agoThat may be, but not because of a barrier to entry. (the wall around the garden)
- kevingadd 6y agoThe barrier to entry for integrating with the web ecosystem is way higher than native. I can interop trivially with basically any native app on my machine, meanwhile even basic tasks like 'export my data from this web service' are often difficult or impossible because vendors don't care. If you are building a custom product from scratch with no need to integrate with users' existing data and services, the barrier to entry is low. But most users have lots of existing data to use and it lives on other services, so you have to integrate... if you can
- recursive 6y ago> I can interop trivially with basically any native app on my machine. You must have different native apps than most users. In any case, there's nothing special about WASM and DOM that makes it less interoperable than native stuff.
- kevingadd 6y agoThe problem isn't WASM and DOM, it's that in the web environment because the storage and expressiveness are so limited most of your data lives on a third-party server and now you have to integrate with that. My Outlook and Thunderbird inboxes are files on my local disk, so if I'm determined enough I can dig through those files with custom software. If I want to process my gmails no amount of time in a hex editor will help me because that data lives on a server somewhere. In practice, Thunderbird acts as my interop tool here, because the developers of that program did the work to keep up with whatever method was offered to pull content out of gmail. In this case there are standardized APIs (network protocols) for talking to mail servers, and lots of software that implements those. What's the equivalent if you want to do this in a webapp? Is there a common API that I can use in my webapp to access a user's gmail, apple mail, outlook mail, etc? In practice you need to do 1-off integrations with almost every given web service a customer's data might live on, and some of those services don't have any APIs so it's screen-scraping or nothing. It's as if every user's photos were stored in a mix of 50 different custom image file formats.
- danieldk 6y agoThis is why we need WASM and web-first development. This is only going to make things worse. If everything is a web application, why would users even need access to their hardware or be able to modify their operating system? Boot from an locked bootloader that only loads a FAANG-signed shim OS, that only loads a FAANG-signed web browser. Next, disallow extensions and ad blockers and we are in the brave new web world were a small number companies more powerful than nation states continuously monitor your behavior for ad impressions. Sure, now you can install a web browser on your Linux or BSD machine. But once they are in that position, they will make sure that it will be a miserable experience without necessary DRM, disabling or not investing in hardware acceleration, breaking random things on 'unsupported combinations', etc. Moreover, as usual on the web, any competitive player the becomes a threat will be bought by the increasingly large FAANG companies, ending their 'incredible journeys'. Even though it will probably never happen, what we need is Linux on the desktop, with good native applications, plus a truly open mobile platform.
- chooseaname 6y ago> This is why we need WASM and web-first development. This is why we have Linux. Personally, I don't want to live in a web-first world. I don't want everything I do on a computer to have to have internet access. And I certainly don't want the browser to be my OS.
- kevingadd 6y agoCode-signing and certificates are still necessary even in a WASM environment. Once all your software moves into the web browser, all your important data lives there too and the risk profile of all the third-party code loaded into your websites is incredibly high, just like it is for Chrome and Firefox extensions. Right now if you're a Windows dev you get harassed by SmartScreen, but if you're a web dev you get to either reinvent the entire stack from the ground up (to control it) or pull in 20 different third-party dependencies, none of which are code-signed, without any easy methods to ensure integrity other than manually listing specific hashes in a fashion that causes your website to break any time a vendor pushes new code. Don't get me started on software that currently only works if deployed as an extension - being an extension developer is one of the worst development experiences on earth
- the8472 6y agoweb-first means you don't have an immutable application on your machine anymore, it's always loaded from a server on every use. They can change their terms at any time and if you granted them access to a directory tree via the fileystem API they can change the code under your nose and start exfiltrating those files. Native applications can be forced to run without network access with a single command (e.g. firejail or unshare). The web is always-online.
- pjmlp 6y agoWeb makes your OS irrelevant, the browser is the VM, it can even be running bare metal for what I care. Best way to kill all alternative OSes.