61–70 of 179 posts
I wonder if wasm is feasible to target in hardware. I mean, there were hardware Java bytecode implementations, and that's a lot higher level, so it's definitely possible - but is it worthwhile? Are there any idiosyncrasies in wasm that make it slower than x86 or ARM, that could be fixed if the underlying architecture was more accommodating?
Earlier quoted context omitted.
They won't add functionality that would compete with the app store. Add to home screen is a good example
Serious question: Do non iOS users actually add PWAs to there home screen?
Browsers have been working had to make people not want bookmarks, but everybody that I show how to get them is just loves them.
(But well, they would be better if the mobile web didn't suck.)
Apple has shown and continues to show willingness to embrace web technologies once they show clear promise or stability[1]. They might not implement "hemorrhaging edge" technologies immediately, but if the technology supports it, and it contributes positively to the user experience, they will do it. [1]: https://twitter.com/mhartington/status/1089292031548145666
Earlier quoted context omitted.
They won't add functionality that would compete with the app store. Add to home screen is a good example
Serious question: Do non iOS users actually add PWAs to there home screen?
Earlier quoted context omitted.
Not really. Progressive Web Apps are a much better model for users than the App Store because they get to use the app immediately then decide later whether they want to keep it on their home screen or not. We've all become very used to the App Store but honestly the experience is pretty crappy.
Web apps are inherently mediocre on every platform. There’s enough advantage from being accessible via URL, usable on any device, live updating, etc. to compensate that for many uses. But using web apps daily for any serious work is a huge loss in resource use, usability, polish, ... The one that makes me saddest though is that web apps seem to be getting worse over time. For example most of Google’s suite of web app…
Apple has shown and continues to show willingness to embrace web technologies once they show clear promise or stability[1]. They might not implement "hemorrhaging edge" technologies immediately, but if the technology supports it, and it contributes positively to the user experience, they will do it. [1]: https://twitter.com/mhartington/status/1089292031548145666
I don't think that's right. Apple are consistently late to the party as far as Safari goes. I mean, they don't even support web push notifications yet, while other browsers have been supporting them for years. It's down right annoying.
Earlier quoted context omitted.
I don't think that's right. Apple are consistently late to the party as far as Safari goes. I mean, they don't even support web push notifications yet, while other browsers have been supporting them for years. It's down right annoying.
Case in point. Why do you need web push when you have websockets which safari supports?
Apple has shown and continues to show willingness to embrace web technologies once they show clear promise or stability[1]. They might not implement "hemorrhaging edge" technologies immediately, but if the technology supports it, and it contributes positively to the user experience, they will do it. [1]: https://twitter.com/mhartington/status/1089292031548145666
They won't add functionality that would compete with the app store. Add to home screen is a good example
iOS 12.2's main updates are with regards to state management and authentication flows for PWA's.
https://hub.packtpub.com/apple-releases-ios-12-2-beta-1-for-...
I never expected WebAssembly to be as fast as native only to be significantly faster than JavaScript. Considering the popularity of Electron, if WebAssembly does get as fast as native or at least 80% there (and that's a really big if) it would easily become the cross platform language for the vast majority of desktop applications. For mobile we will always be dragged down by Apple and its reticence to embrace web tec…
What's the point of using this for native applications ? I mean yeah, it might be a little easier to distribute but it's kind of absurd to agree to throw away 20% performance for a bit of convenience and then sched tears on how the latest intel chips only delivered 5% improvement over the previous ones.
The point is that javascript isn't actually a bytecode (javascript as the "bytecode for the web" is just a metphor and a necessary evil,) and compiling to javascript isn't as efficient as compiling to bytecode. Also, that webassembly provides an open (non-proprietary) general purpose compile target for multiple languages, as opposed to Flash or Java, which are proprietary and meant to target only a single language. Also, to allow for seamless transitions between applications on the web and off the web, allowing the web to serve as a primary channel for the distribution of native software.