8 ms·
Folks, the big point of this article is not that Hanselman likes C#, it's that his list of options does not include Objective-C or Java. It's that he thinks tha
by skrebbel 13y ago
Folks, the big point of this article is not that Hanselman likes C#, it's that his list of options does not include Objective-C or Java. It's that he thinks that the web will win (over app stores). I strongly believe that he's right there.
At some point, app stores had "discoverability" as an advantage over the web. This has been one of the strongholds of native app proponents. These days however, with the enormous amount of apps available on popular platforms, this discoverability feature has become a joke. It's akin to searching the 1999 web for interesting sites but you can only use a badly managed, bribe driven version of Yahoo.
Whoever can make the Google of app discovery might make a temporary splash, but i bet that, not long after, people will return to plain old Google Search. You only need 1 major mobile OS to change paradigm and hide the difference between apps and web apps, and your mom won't care anymore. Given that the world's #1 mobile OS is made by the worlds #1 web company, this change is not difficult to predict.
- juu4 13y ago> his list of options does not include Objective-C or Java He mentions Java, twice. There is nothing wrong with making web-apps in Java, and there are some nice web frameworks to help doing that.
- skrebbel 13y agoHmyeah, you're right, he does. But I doubt he would've included Vala if Android apps were typically programmed in it.
- collyw 13y agoDepending on the type of web app you are making, there are generally better (more productive) tools for the job than Java.
- edwinnathaniel 13y agoIn general, the productivity gap has dimnished signficantly. Unless if we are discussing prototype/quick throwaway/very small web app. In that segment, Rails is still the king.
- collyw 13y agoI was under the impression that you could build pretty decent robust apps with Rails / Django. OK, you wouldn't want to run the size of Amazon on those, but the majority websites are orders of magnitude smaller.
- fossuser 13y agoI don't think it's just discoverability though. I think the main question is if mobile web applications will be able to match native on both quality and performance. Facebook attempted this and failed badly, but that doesn't mean it can't happen or that native will always have an edge. If native does continue to have an edge though then I think web has an uphill battle.
- Joeri 13y agoYou can remove the word mobile. Web apps are still heavily inferior to native desktop apps. The answer to 'why mobile web apps?' is the same answer as to 'why desktop web apps?'
- fossuser 13y agoI generally agree to this, but at least with mobile you carry your phone with you all the time. I could see the benefit of a web interface on any machine you use rather than having to have your laptop with you for the desktop app. Though I guess I usually have my laptop with me anyway.
- MoosePlissken 13y agoDepends on your definition of inferior. I can count the number of desktop apps that I use on a daily basis on one hand, and they're all development tools. I have more than twice that number of pinned tabs in my browser that are open at all times.
- Iftheshoefits 13y agoAre those pinned tabs all running applications or merely displaying information (websites)? Are you sure the ones running apps would not run better were they written as a native/desktop version? Are the apps trivial (e.g. to-do lists)? There's a lot of context you left out.
- MoosePlissken 13y ago
- rimantas 13y ago> hide the difference between apps and web apps Frankly, this is only possible by web apps not being web apps. Do you have any experience working with eiterh native SDK? Because I cannot imagine any one having experience (not just cursory hello-world glance) thinking that web apps are somehow superrior. I also don't get how web apps are better (or will be better) discoveralbility-wise. Or why it matters.
- grey-area 13y agoFrankly, this is only possible by web apps not being web apps. I'm not sure I agree with that, though it might never happen because the owners of the major platforms have absolutely no interest in being turned into a dumb foundation by the web (or a badly debugged set of device drivers, as Andreesen put it in 1995). The reasons for the ascendance of mobile are political and corporate though, not technical. There's little reason webkit performance cannot approach that of native, particularly if it used something like nacl rather than js, and no reason APIs cannot be exposed to web apps too (Apple exposes quite a few). Web apps are currently superior in: deployment,future-proofing, IMO discoverability, platform independence, and most importantly cost Native apps are currently superior in: performance, accessible APIs, 3D Their relative strengths will change over time, but note that performance is not usually an insurmountable obstacle, while some of those areas where the web has strengths are inimical to the way Google, Apple, MS or Amazon want to do business - for corporations to tie in their customer as tightly as possible to their ecosystem and tightly control what is available to them (as Apple have for example banned kindle selling on their platform) is the best possible outcome. App stores are broken by design, just as the MS desktop monopoly was, and I don't think they will be able to surmount those problems, because they are fundamentally user-hostile. Why can't I buy kindle books on my ipad? Because Apple wants to make money from that transaction. The web has other problems, among them a worse is better approach in many areas, but I think it's ultimately going to prevail over other solutions bound to a specific hardware/software stack.
- bad_user 13y ago> There's little reason webkit performance cannot approach that of native, particularly if it used something like nacl rather than js, and no reason APIs cannot be exposed to web apps too (Apple exposes quite a few). While I agree with that sentiment, I disagree with the example provided ... if you talk about NaCL, you're not talking about web apps or "the web" anymore. It's not a standard, it has portability issues and it will probably never be implemented by anybody else other than Google. We can bitch and moan about how broken the W3C standardization process is, but the existence of this process is also why the web is open and why it's awesome. The alternative asm.js, while not being an answer to all issues addressed by NaCL, is a much better approach, because it's still standard JS and even if the browser does not optimize for the asm.js instructions set, the app still works - and if it takes off for games (and I believe it will), then all browser vendors will be forced to optimize for it - because it's one thing to not support some plugin (e.g. NaCL) and quite another to have clear instances in which the browser is much slower than the competition and thus directly comparable. For unbelievers that haven't seen asm.js in action, checkout this famous demo that works well in both Firefox and Chrome: http://www.unrealengine.com/html5/ http://www.unrealengine.com/html5/ - that's pure JS right there and I don't think the limits have been reached.
- binocarlos 13y agoIt is also performance - I think Facebook scared a lot of people into hiring Java + ObjC programmers when they announced 'HTML5 is too slow'. Web applications had this problem circa 1998 - i.e. a perception of slowness - look at SalesForce now!
- forgottenpaswrd 13y ago"It's that he thinks that the web will win (over app stores). I strongly believe that he's right there." "Whoever can make the Google of app discovery might make a temporary splash, but i bet that, not long after, people will return to plain old Google Search." You remember me to Kodak's "people will return to make analog photos, people want to hold something in their hand". You are deluding yourself, and you can't see what you have in front of your eyes. No, there is not a single platform that works in everything. In my company we do both low level programming(c, c++[small controlled subset so we control it]. embedded, microcontrollers, hardware) , and high level programming (python, java, web programing in general) for scripts, testing , rapid prototyping or deployment... Both of them work very well for what they are designed for. If we paint something in the screen in c we could do it in 0.001 seconds(without hardware accel!!), in python it is 0.5 seconds, 500 slower!!. In the browser is like 500 if we were to do things on javascript. Most people fake and call webgl with hard pre calculations done in a server(native) "web programming". It is not. And we use python a lot. Because we don't care if something takes 5 seconds to draw if this saves hours or days of debugging. In the future communications will be better, and program interaction will be stronger, but that does not mean that all software will be web. Multiplattform native works also very well, and much better for some things. "Given that the world's #1 mobile OS is made by the worlds #1 web company, this change is not difficult to predict." Android is not web for a reason. It sucks for lots of things. It is not that Google has not tried, as it is in their best interest to do so. The interest of a web company are something, and the interest of consumers are something else. Consumers probably don't like having to be connected all day, all what they do in their computers being monitored in real time and stored forever by the NSA. You probably are American but there is people living in other countries, with different interests. As Snowden said the NSA uses their tools for industrial espionage(as should be expected). If you have a company outside the USA you will have no brain if you used web for your secret sauce. They will take it from you, they will give it to an American company and even patent it. With native it is orders of magnitude harder to do this.
- bad_user 13y ago> "In the browser is like 500 if we were to do things on javascript." That's more like 1.5x: http://asmjs.org/ http://asmjs.org/ http://www.unrealengine.com/html5/ http://www.unrealengine.com/html5/ https://hacks.mozilla.org/2013/12/gap-between-asm-js-and-native-performance-gets-even-narrower-with-float32-optimizations/ https://hacks.mozilla.org/2013/12/gap-between-asm-js-and-nat... > "Android is not web for a reason. It sucks for lots of things. It is not that Google has not tried, as it is in their best interest to do so." Google hasn't tried deep integration of web apps with Android. Their competing Chrome OS does and Chromebooks are a bestseller in 2013. Mobile Chrome doesn't have "apps" or plugins, like Firefox does, which is kind of disappointing. "Add to Homescreen" of favorite links was added in version 31 and current stable version is 32, so that's one version ago. The reasons for this state of affairs can only be guessed, but given that you probably don't work for Google and you don't claim to have insider knowledge, I guess that quoted phrase is just pure speculation - and a much more sensible guess would be that delivering a native SDK that works well was faster than trying to push for new web standards (since Android was competing with iOS and second to market) ... something which they are doing with Chrome OS and Mozilla is doing with Firefox OS and it's a very different reason than your claim. And if I am to make a prediction, I bet that in the future either we'll see Android and Chrome OS merging, or we'll see Chrome OS mobile devices, in addition to Android. > "Consumers probably don't like having to be connected all day, all what they do in their computers being monitored in real time and stored forever by the NSA." Web interfaces and offline access are not mutually exclusive. Chrome's offline GMail is pretty good these days. For PGP encryption in GMail's interface, I've been using: http://www.mailvelope.com/ http://www.mailvelope.com/ Surely Chrome's permissions for extensions could be improved for better security, because as we've seen, perfectly legitimate extensions can turn over night to mallware/spyware/adware. And we would need new web standards for extensions and probably for doing client-side encryption, however these are not insurmountable problems. Either way, if you're using GMail, your unencrypted emails will get stored on their servers, whether you're using GMail's web interface or not. > If you have a company outside the USA you will have no brain if you used web for your secret sauce. They will take it from you, they will give it to an American company and even patent it. With native it is orders of magnitude harder to do this. I don't like the insult inherent in this message. I'm using web GMail and I'm not an US citizen. The problem is that Google is an US company, not that GMail is a web interface. And in regards to clients and native apps - my trust for binary blobs is equal to my trust for web interfaces, which is zero. Basically I don't trust anything that's not open-source and developed in the open - as in, are you sure your operating system doesn't have backdoors planted? ... just saying, seeing that you're playing the trust card.
- grayrest 13y ago> It's that he thinks that the web will win (over app stores). I strongly believe that he's right there. For anybody doubting this, please read Clay Shirky's "Permanet, Nearlynet, and Wireless Data". [1] [1] http://shirky.com/writings/permanet.html http://shirky.com/writings/permanet.html It's a fun read in a post-iphone world but the money quote is: The permanet strategy is to start with a service that is good but expensive, and to make it cheaper. The nearlynet strategy is to start with a service that is lousy but cheap, and to make it better. The permanet strategy assumes that quality is the key driver of a new service, and permanet has the advantage of being good at every iteration. Nearlynet assumes that cheapness is the essential characteristic, and that users will forgo quality for a sufficient break in price. What the permanet people have going for them is that good vs. lousy is not a hard choice to make, and if things stayed that way, permanet would win every time. What they have going against them, however, is incentive. The operator of a cheap but lousy service has more incentive to improve quality than the operator of a good but expensive service does to cut prices. And incremental improvements to quality can produce disproportionate returns on investment when a cheap but lousy service becomes cheap but adequate. The good enough is the enemy of the good, giving an edge over time to systems that produce partial results when partially implemented. The people on the web platform have much greater motivation to improve perf and the developer experience than the people working on native platforms have to expand distribution.
- Silhouette 13y agoIt's that he thinks that the web will win (over app stores). I strongly believe that he's right there. I agree, but not for the technical reasons most people are mentioning so far. I think there is a much simpler driving force: mobile app stores have set both the quality bar and pricing expectations so low that it's almost impossible to develop good, non-trivial software for them and make money. On top of that, the app store platforms tend to want a big cut and/or restrict the use of other payment models and/or want developers to jump through hoops just so users can install their application and/or require developers to build in a specific programming language that produces executables for their specific platform and/or a bunch of other obstacles that web development simply doesn't have. Meanwhile, the only major benefit native apps have to offer in return these days is access to a few native features. Given how much success many web applications have already enjoyed, it's clear that those features aren't compelling in many of the application domains where this kind of decision is being made. It's also clear that if performance was ever really an issue for most web apps, it's an ever diminishing one and mostly irrelevant by now. The two major business models that have made serious money from mobile apps other than in outlier cases are in-app payments and advertising, which are probably the two most widely abused and consumer-hostile payment models in widespread use today. I suspect mobile apps in their current form were already dead as a serious software platform as soon as people were selling $1 gimmick applications and $5 puzzle games in app stores. The industry just hasn't quite realised yet because there's still too much hype from the (mostly now over) gold rush, but fortunately we have high quality and great value apps like Dungeon Keeper at the top of the promotions screens to show us just how good mobile apps can be if you want to make real money from them. Meanwhile, as numerous HN regulars can attest, plenty of B2B web apps are making money like it grows on trees, and plenty more people are making a decent amount of money with other B2C business models that simply aren't compatible with today's mobile app world but work fine on the web.
- Fasebook 13y ago>and hide the difference between apps and web apps, and your mom won't care anymore Completely wrong, imho. There's no benefit to obscuring information about what the user is doing. This also implies a universal cloud storage where authors of software have more access to user's personal information than the user. You're basically yearning for what Google's Chrome crap is trying to do, so you're not going to do it better. > Given that the world's #1 mobile OS is made by the worlds #1 web company, this change is not difficult to predict. I think I see where you're coming from here. If you just want to suckle at the tit at what ever company is #1, then sure, learning their stack and developing whatever for it is a sure way to make steady income. Shit, how about a steady job while you're at it. Then it really doesn't matter what widgets you're pumping out. Wait, is this an entrepreneurship forum? Anyway, trying to play Google's game or Apple's game is just a good way to be their bitch. I'm sure you're aware of why "discoverablity" has been removed from appstores. This is a culture war, at some fronts. If you want to build a digital prison for your mom, go right ahead, but don't expect your kids to embrace this "cloud" stuff in any way that you're dreaming of. You're just building outdated virtual landfill techgarbage the moment you touch any of these paradigms you're talking about.