3 ms·
> Except you can run wasm on an iPhone. An arbitrary decision made by the manufacturer. If Apple decided they didn't want to support web assembly tomorrow, do
by AnIdiotOnTheNet 7y ago
> Except you can run wasm on an iPhone.
An arbitrary decision made by the manufacturer. If Apple decided they didn't want to support web assembly tomorrow, do you think that would kill the iPhone or WASM?
- matthewbauer 7y agoIt would almost certainly kill WASM
- deleted 7y ago[deleted]
- DonHopkins 7y agoLike it also killed not just Java on phones but also Flash.
- HALtheWise 7y agoIt depends on when, and how much adoption it has. If the iPhone stopped supporting HTML, it would kill the iPhone, and your guess is as good as mine about how wide of adoption wasm needs before it hits that threshold.
- AnIdiotOnTheNet 7y agoI'm not so sure. Flash was ubiquitous until the iPhone decided not to support it.
- tracker1 7y agoFlash was also the single largest exploit hole and cause of system crashing bugs at the time.
- DonHopkins 7y agoBesides that arbitrary decision to shoot your husband in the head, how did you enjoy the play, Mrs. Lincoln?
- Silhouette 7y agoIf Apple decided they didn't want to support web assembly tomorrow, do you think that would kill the iPhone or WASM? That's a good question, and it's certainly not one I'd want to bet on as Apple. When they managed to kill off Flash and Java applets, they were getting rid of the two awkward technologies that almost everyone in web development disliked. There were useful replacements coming down the line with HTML5, ES6, and so on. It still took several years for the plugins to die out completely, during which time the browsing experience on Apple devices was noticeably inferior to everyone else's. Arguably it was only Chrome pulling support that finally put an end to the matter. Today, Apple's reputation isn't what it used to be, with its normally loyal and enthusiastic fan base increasingly questioning the price of new devices, web developers increasingly questioning the lack of support for modern technologies in mobile Safari, native developers wary of Apple's policies around the App Store and how much of the money it's taking for its cut, and the walled garden ecosystem looking increasingly isolated in a world full of connected devices and data sharing. It's hard to see any of these trends changing in Apple's favour any time soon. Right now, WASM is in its infancy, but if you stop and look at what is being attempted, it is arguably the most important new technology in web development. It's already reasonably well supported across almost every browser that matters, but not yet widely used. But give it a little time to establish it as a target for better languages than JS and to develop supporting tools and libraries, and it's not hard to imagine that in a decade's time we'll all be wondering what we were thinking using JS for so long.
- vlaskovits 7y agoThis is the question of the day wrt WebAssembly: Will Apple continue to support wasm in Safari? Does wasm strategically impact the dominance of the App Store?
- tracker1 7y agoAt the time, Java and Flash were the main points of security exploits in practice, and flash was the single biggest cause of system crashes on Mac.
- hinkley 7y agoAn arbitrary decision made by the manufacturer of the phones of customers with the largest discretionary spending budget. I recall there being an article about how despite the fact that iPhones are 10% of the market, they represented 50% of the profits for application developers.
- jayd16 7y agoIt would hurt wasm, certainly. It was an arbitrary decision but that's the reality of the world we live in.