|
|
|
|
|
by KingMachiavelli
1709 days ago
|
|
It's the other way around. WebApps at the time would have been a complete joke since mobile browsers were so limited. At least that's how I understand it. He just didn't want any third party apps. He wanted to make every app in-house. (For example the original YouTube app was an in-house project.) It sounds crazy but at the time the wild west of apps on the desktop meant that the user experience was pretty poor and allowed malware to explode. It has been said that Microsoft's failure to fix these issues is really what drove web application development. No one realized a viable alternative was to lock down the device to a single store/publisher and then take a 30% cut. Now that WebApps probably could replace nearly all native apps, it's in Apple's best interest to not fully support PWAs, WASM, etc. because the app store is so lucrative. |
|
Nah, what drove web development was 100% ease of deployment. No more dealing with installers that don't work and people who don't know how to use them, the browser is already there; no more dealing with the pain of rolling out updates, you push to your own server and it's done. And you don't have to care about Windows stack vs Mac stack with completely different teams, a few css/js tweaks and you're done. Sun understood the issue and tried to put up a fight with their Java Web Start, but in the end the JRE still required an installer, with all the related issues. MS eventually got something like that working seamlessly, but it was 15 years too late.