58 ms·
I have been thinking about why we have ended up here, and why not just native apps. The obvious answer is that it makes applications portable, which is great.
by ehnto 9y ago
I have been thinking about why we have ended up here, and why not just native apps.
The obvious answer is that it makes applications portable, which is great. The other key component I think is delivery. You don't ever install anything, it just exists when you ask for it. That is something native applications have never done, and not even something like JVM has done even though it addresses portability too.
It is also nice that it is seamless with the browsing experience, but I have to wonder if it hasn't just turned out that the typical browser interface is a better interface for computing than most popular OS have been? As the OS and browsers start to see parity, are there lessons from browsers that we can integrate into the OS?
- wlesieutre 9y agoIt's definitely far behind where web apps are for instant no-install access, but Android has their "Instant Apps" feature providing similar capability https://techcrunch.com/2017/10/19/google-play-adds-android-instant-apps-via-a-try-it-now-button-among-other-changes/ https://techcrunch.com/2017/10/19/google-play-adds-android-i... Disclaimer: I don't have an android phone anymore and I have no idea how available/useful these actually are
- solarkraft 9y agoExtremely far behind schedule, but for the apps it does work for it's not even that bad. The android app architecture seems to require some heavy restructuring to do this though, so I don't think it will be attractive for developers. The portability problem of course holds this back from the insane adoption the web has gotten as well. Basically it's too little, way too late.
- mathgenius 9y agoAnd things like dropbox allow the OS to go in the other direction, towards being distributed.
- sillysaurus3 9y agoMost users spend >80% of their time in the browser. It's probably that simple. If you have a thing and you need users, are you really going to deliver it as a Qt app? Unless you're bitcoin, it's hard to think of a case. I'd say "or a game," but many are webapps. And at this point some of the hollywood-grade games might figure out a way to be coming to browsers soon. Unreal did it.
- solarkraft 9y agoIt is that simple. And a bummer because I think HTML is a pain for things that aren't documents. And JS UI frameworks feel like hacks too. Unity already supports the web, but I don't think that'll matter for AAA games. People who buy computers specifically to play them will care about the slight performance hit and not want to keep the games they bought and spend a lot of time with as bookmarks to web pages. Non-performance intensive tools, even large ones, have already moved to the web. This will likely continue because there is not other platform delivering its level of portability and ease of delivery. It's a bummer because the web just kind of sucks. It was made for documents, damn it. Something like a java browser could've succeeded as jars are already very portable. This could've worked pretty well for small and large tools alike. But since the HTML stack is already widely adopted I guess we'll have to make the pain go away somehow. At least webassembly solves the problem computationally intensive tasks. The UI component is still quite a mess, but that's getting better too. I just find it annoying that they have to call everything Web-(what it traditionally was). It's basically the new reality, being used on non-web platforms as well as on the web.
- ehnto 9y agoUnity also has the slight delivery hitch of needing the browser plugin to run games in the browser. I tinker with Unity and I still didn't install the browser plugin. That is the same hitch the JVM had. For a non-technical user, that extra step feels risky and unintuitive. "Why doesn't it just work?" feels a bit unfair when you know what's going on, but to a normal user I think it's a fair question. We are the professionals after all, why can't we make it "just work"?
- doomlaser 9y agoIt's optimizing for the path of least resistance. No context switching, no decisions necessary, just click and go.
- Yuioup 9y agoThe other key component I think is delivery. You don't ever install anything, it just exists when you ask for it. That is precisely why I made the jump from Delphi to ASP.NET back in 2003, and now the jump to Angular2+.
- modeless 9y agoThe answer is that browsers provide something that users desperately need and no operating system has ever provided: a sandbox strong enough to run completely untrusted code. The success of browsers is an indictment of the entire field of operating systems research. They have either failed to recognize the need or simply failed to deliver that kind of security. For one example take WebGL. For decades OpenGL had been a native API prioritizing performance first and security last. It wasn't until browsers decided to expose OpenGL that the necessary work was done to make a graphics API safe for untrusted code. And who did that work? The browsers had to do most of it themselves.
- oconnor663 9y agoIt is a bit of a chicken and egg problem, though. It's not enough for researchers to write a paper about APIs that should exist. The APIs have to get implemented across major platforms, which requires major applications using those APIs to motivate them. I don't see how it would ever have happened with a giant slow incremental process, and the web has been that process for us.
- oconnor663 9y ago* without
- dullgiulio 9y agoI agree a lot with your comment. But it should also be noted that users have very little choice on what code they run when surfing the web. So in one way, browsers cause the problem they then have to solve.
- blub 9y ago> a sandbox strong enough to run completely untrusted code No browser has provided that either. In fact, browsers are by definition a security anti-feature because they are always connected to the network and the customer/user data lives on the network. Even if they manage to solve the problem of computers getting hacked when visiting websites they are very unlikely to solve the problems of tracking and private data vacuuming.
- cm2187 9y agoYou can add even more pros to asm web apps. - Sandboxed, web apps can't wander around in your filesystem, and you can even prevent them from knowing anything about you (private mode). That's good for privacy and security. - You bypass the apple/google store, their paytoll, capricious criteria and how they promote apps And I think asm apps (not websites) will have a great success when asm has become a full VM not just because of these reasons, but also because it will make it possible to develop cross-platform in a language that isn't javascript. Some people love javascript, I personally hate it. C++ devs will be able to develop in C++, I expect C# and Java dev to be able to write their apps in C# or Java, and I am sure even more languages will join the party. That's a great thing.
- vasco 9y agoPrivate mode is about hiding a trail from yourself rather than the websites you visit. They still get all your request logs.
- cm2187 9y agoWhen you launch private mode (save for browser fingerprinting and other super cookies), you are a new user to the website. When you close it, anything the website attempted to store on your machine is gone. Of course it can track you during that session but not before or after.
- proaralyst 9y agoUnfortunately techniques like browser fingerprinting[0] still work in private browsing and can be used to link your private browsing to your normal browsing. [0]: https://en.wikipedia.org/wiki/Device_fingerprint https://en.wikipedia.org/wiki/Device_fingerprint
- geocar 9y agoCan, but usually aren’t. Advertisers aren’t interested in advertising to you unless it’ll “work” (in terms of sales, clicks, or whatever the KPI is). If I think you want to not see my ad, I don’t want to buy your eyeballs. My own experiments with GL and the timing-based methods is that they just don’t work well (compared to say, cookies) when delivered via an advertisement. Plugins and fonts work very poorly as well, lately. I don’t think anyone is using these methods to target advertising, and state-level actors don’t have to (they just bug your ISP). Who are you trying to protect against?
- aaronblohowiak 9y agoJvm certainly tried this with applets
- Iv 9y agoDon't forget sandboxing. Browsers routinely execute unsafe scripts (hopefully) without compromising the user's account or event the browsing session. OSes are still far behind. I always say that this situation is a bad solution to a bad problem. Had Apple, Microsoft and the FOSS world agreed on some standards, native code could be portable and the norm.
- jes5199 9y agosince browsers originally only displayed documents, some of the assumptions are nicer than the assumptions that came out of desktop metaphors. For example, most UI text in a browser can be copy/pasted, and that's almost never true in native UIs.
- shams93 9y agoIt also makes it hard to pirate your software. Cracking native software is relatively trivial which is why legitimate licenses cost insane amounts. Contrast soundtrap charging $15 a month for their web based DAW to Ableton having to charge $750 to make up for piracy costs.
- blub 9y ago1. Ableton is a great DAW with a long history used by many well-known producers. They can and deserve to charge more than 15 bucks. It's laughable to think that anything other than a todo app would cost so little. 2. It's not $750, there are multiple editions available, the more expensive ones include more plugins, instruments, loops, etc. 3. Cloud-based startups are nice until they reach the end of their wonderful journey, sell out and you're out of a tool. Soundtrap is charging $15 because that's what it's worth. Although if the cloud is mandatory it's worth zero in my opinion.
- inDigiNeous 9y agoThis, a hundred times. An insane amount of work has gone into making something like Ableton Live. The general idea that applications should cost something in the range of 2 - 30 usd is ridiculous, when you compare it to any real world physical examples. For example any instrument costs much more than that, and the same time could have gone into developing the software and building the instrument. Or heck, any handbag or fashion item can cost a ton of money, and people are ready to buy them, but when software actually costs something close to real value produced by that software, people get pissed these days. I blame the iOS/Android markets that have created a biased and untruthful image for the costs of developing software. You can't expect to make a living from developing software that costs 1.99/2.99/9.99 unless you sell a ton of those, and most never do, but this market has effectively changed the mindset for normal consumers to get things either free or for a price of three cups of coffee.
- badsectoracula 9y agoOn the flip side of that coin, as a user, it also makes hard to control your own software - you are not in control of the version you are using, not in control of the features the program has and above all not in control of the availability of that program as whoever owns the server you are accessing it from can revoke that access at any point for whatever arbitrary (but of course always mentioned in the Terms and Conditions that nobody reads) reasons. I'd be aware of promoting anything that takes control away from the user. The web is fine for sharing knowledge and communication (and pictures of cats) but let's not put everything in it or we'll certainly regret for giving away the power to control our software.
- gjvc 9y agoAlan Kay has an excellent and relevant talk as to why we shouldn't have ended up here (from 1997), which I think will answer your questions. https://www.youtube.com/watch?v=oKg1hTOQXoY https://www.youtube.com/watch?v=oKg1hTOQXoY
- MaxBarraclough 9y ago> not even something like JVM has done Not counting applets and Web Start?
- netheril96 9y agoWell, perhaps to be more accurate, > not even something like JVM has done successfully.
- pjmlp 9y agoIt was such a bad idea that Google now has Instant Apps on Android and ChromeOS.
- vog 9y ago> You don't ever install anything, it just exists when you ask for it Relevant XKCD: "Installing" https://xkcd.com/1367/ https://xkcd.com/1367/
- joaomacp 9y ago> are there lessons from browsers that we can integrate into the OS? Windows 10 is working on adding tab navigation to all windows: https://arstechnica.com/gadgets/2017/11/tabs-come-to-every-window-in-windows-10-sets/ https://arstechnica.com/gadgets/2017/11/tabs-come-to-every-w...
- mmjaa 9y ago>I have been thinking about why we have ended up here, and why not just native apps. In my opinion its because operating-system design wasn't sexy after browser-companies came and ate the OS-guys lunches with all that big bubble fuss. So the OS guys went all apathetic and forgot that a majority of their OS is a freakin' browser, and .. here we are. Inception. Its great we can compile C++ to 'native' assemblies now. We've always been able to do this, btw. The only difference is the delivery mechanism ..
- Goladus 9y agoI think delivery is a bigger deal than portability. There are many ways to make applications portable in 2017. The big deal is that browser SPAs don't need to be installed, they just run when a user clicks a link or loads a page while browsing the web (something they already do anyway).
- inDigiNeous 9y agoThis seems to follow natural evolution, everything coming and going in waves, each time reaching a new evolution and better version of that older wave. Before personal computers, terminals were the thing, just connecting to a mainframe and executing programs there, then we reached the state of standalone computers being offline for a while mostly, then the Internet boomed really fast and computing went more to server/client model, and now we are going towards back loading code from a server, but having more intelligence in the client and executing more offline. It's interesting to notice these things repeating themselves, I bet at some point maybe the OS and the computer merge more and we will have again more systems like we did when the Internet became to rise.
- vsund 9y agoThat's the conclusion I also came up with. It's pretty clear that the browser is the new platform for apps. Though I wonder why Firefox OS has failed this hard. I never looked more into it, but isn't it a platform centered around having web apps as native apps? I think some day every OS will be similar, so was it ahead of time?
- narag 9y agoThe obvious answer is that it makes applications portable, which is great. That's an understatement. Anybody trying to write a multiplatform complex desktop application around 2000 would have learnt that it was way much harder that it sounds today. Browsers were in a very reduced group of success cases. Edit: also dont forget that there was a war about what tools and languages would become dominant. Unlike alternatives, most web tools were free.
- ryandrake 9y ago> You don't ever install anything, it just exists when you ask for it. That is something native applications have never done Actually, this used to be common, and still is for things like game consoles. You used to stick the floppy disk in, and run the program directly from there. No concept of installing anything. Indeed your computer may not have even had writable storage to "install" anything onto. At worst, if you did have a hard drive, you were free to copy the (single) executable onto your drive so you didn't need to rummage through your stack of floppies to find the program every time you wanted to run it. That was the extent of installing something. The situation where your program consists of multiple files, each of which had to be copied into some special location on your hard drive by an "installer"--is a relatively new (since the 90s?) concept. It's actually refreshing nowadays when I stumble upon one of those rare applications where everything comes in a single executable file and it can be run from anywhere. Dying breed.
- 1024core 9y ago> I have been thinking about why we have ended up here, and why not just native apps. That's what Java was supposed to be.
- whiddershins 9y agoThe obvious answer is that web-based apps are effectively access restricted so the developer can charge any price they want including free, change prices at will, and enforce it effectively over the long term. Native apps struggle with this. Things that are easy to monetize tend to attract more effort than things that are possibly impossible to monetize, or have very limited monetization options.