The Promise of the Web(alertdebugging.com) |
The Promise of the Web(alertdebugging.com) |
It provides a sandbox for executing untrusted machine code (or PNaCl for more portable LLVM bytecode), downloaded on the fly, which would enable efficient implementations of things like HTML/CSS/JS.
I look forward to the day someone gets a browser rendering engine compiled and running in NaCl.
> Finally, the process can chain, so a particular [data/DSL] file might be given to a display program which is a Ruby script which would in turn be given to a generic-runtime interpreter for the appropriate version of Ruby.
So it's untrue that using NaCl or something similar means that all code (let alone all data) has to be sent to the browser already compiled down to assembler (or PNaCl bitcode or whatever). Among other things, this is one important reason why Mozilla is wrong to claim that adoption of NaCl (or whatever) would mean that HLL/scripting-language/whatever code distributed over the Web would no longer be able to benefit automatically from speed improvements to the browser's HLL runtime(s). Chained content negotiation is your friend TM.
"Now imagine a world where the browser ran something
lower level. Where Google, Mozilla, Microsoft, Opera,
and Apple’s jobs in providing a browser more resembled
Intel’s job of providing a chipset: they simply
provided hooks for basic technologies like sound,
camera, movies, geolocation, etc. And on top of that,
we the developers wrote HTML, CSS, JavaScript"
There are 2 main problems with the web right now that I can see being brought up repeatedly
1. Devices / Lower level API's, new android devices have access to the camera but all things considering that is very weak, why do we not have standard solutions for clipboard access, device apis, filesystem apis, storage etc
Phonegap are doing great work for this on mobile, Mozilla have also talked about this in their mobile browser, if phonegap can do this cross platform then how in the hell can browser manufacturers not? why doesnt firefox already ship with this support on the desktop?
2. is performance, is javascript going to ever be fast enough that we can build rich applications and games, right now the smallest page animation triggers ridiculous stuttering, is it javascripts problem or the doms? is it fixable with current solutions? blazing fast hardware accelerated webgl or canvas doesnt matter if the host language cant lookup a variable without random second long pauses.
nacl is often brought up as the solution here, but I have a hard time seeing how providing a sandbox to execute native code is gonna help me build a nice mobile app that uses web technologies (forms, links, standard tools for accessibility) and can still do a decent page transition without stuttering
This article doesnt seem to draw any conclusions about how to solve these, and the "everyone can be the owner of the web" seems almost like its apologizing for Joe Hewitts confusingly completely off base conclusions.
I dont have any answers either, but happy that the conversation is being started.
Having thought about it more, I think the real issue here is standards. All these other problems are a function of that in my opinion. The problem with standard stagnation and lack of competitiveness, whether it be missing features or hardware access, is not a coincidence in my opinion. This isn't some rut we are currently in that if we work hard enough we'll get out of. Instead, I think that the structurally process itself is predisposed to it. 5 years from now, the web will just have a new set of technologies that its behind native on. In other words, the way things are headed, the web can never be cutting edge. And sure, there will always be things that work well on the web, but I would personally like a cutting edge web.
Additionally, I'd like to add that as I stated in the article, I have discussed these thoughts with Joe on more than one occasion, and even had him look this over beforehand to make sure I wasn't putting words in his mouth. I don't think I was apologizing for Joe, I just think this is a really complex situation where the same analysis can take different shapes.
Recently the new iCloud applications show that sexy animations are also possible on the web, if you're willing to put time into polishing it!
Performance on the web hasn't _really_ been an issue in years. The real issue is bad developers set the bar for web applications very low.
So ... where are they now? It was a nicer webapp, but no substitute for Keynote. Having worked with ObjJ/Cappaccino, I found it to be a frustrating attempt at working around the browser, rather than an actual solution.
Performance on the web hasn't _really_ been an issue in years. The real issue is bad developers set the bar for web applications very low.
That's poppycock. In terme of performance, you simply can't come close to what native apps are doing. We invest enormous effort in leveraging threading and extremely low cost implementations in native code, even dropping down to NEON/etc where appropriate.
There is room for higher level languages (arguably that's what ObjC is, plus ARC) but JS simply is not a replacement for what native app developers are doing. NaCL is.
1. The web is losing ground to mobile apps. The New York Times should have been the perfect use case for the web, yet they are a native app on mobile platforms. If we extrapolate this rate of change, five years from now people will be self-publishing blog apps instead of sending you a URL.
2. That's because the web lags behind native apps in features and polish of user experience.
3. Which is because innovation on the web is gated on major browser vendors, who are slow and prone to political infighting (e.g. over video codecs).
4. The only way for little guys to add features to the web (e.g. video) is to make browser plugins (e.g. Flash). So the crusade against Flash and plugins was a bad thing.
Then the article goes on to propose a solution that I don't think is very good, but hey, at least it's a try.
Web developers will be the least receptive audience possible to the idea that web applications can't compete as-is with native platforms. Native development requires a whole new skillset -- one that is likely beyond that of many existing web developers, and it requires abandoning years of cognitive training. It requires admitting that you can't necessarily have both a great app and search engine indexible app.
Google may succeed with NaCL, but I don't see how anyone else will. Mozilla is steadfastly opposed to progress beyond HTML/JS, and Apple has no interest in undercutting their own platforms.
Some relevant links:
HN Discussion: http://news.ycombinator.com/item?id=3024342
The article: http://joehewitt.com/post/web-technologies-need-an-owner/
The original Post on TC: http://techcrunch.com/2010/04/30/joe-hewitt-web-development/
I pointed to the trend of traditional web properties moving to native apps when it came to mobile. Things like nytimes, economist, and even Facebook.
I discussed how most new social networks on mobile that have gained any traction or attention (such as FourSquare and Path) were largely a native phenomenon (even Google+ chose to have a native iPhone app).
I talked about very real examples of how Flash was important in the development of the web.
I believe that there are a lot of valid counterpoints to my argument, and I'm actually really interested in hearing and thinking about them. However, I don't think hand-waiving it away as "theology" is one of them.
This is looking only through the perspective of the content creator, ignoring the client. We're only just know trying to add some structure to the content, and we already have Microformats, RDFa and Microdata, all with incompatible formats and semantics. Now we couldn't even rely on the semantics of HTML?
He sees the web as a app distribution mechanism and the browsers as just dumb viewers. I think the web is much more than that: it's an information distribution mechanism, and that's only possible if there is standardization of protocols and formats.
Perhaps this is my fault for ending on that point, but do you also disagree with all the other paragraphs? I ask this honestly, because if we can just agree on that much, then I totally agree that there are a number of options that are worth discussing to make the web competitive in a way that scales again.
As for plugins, I've never seen them as benefit. Either you're a big player and then you can influence the direction of the web, or you're just some random guy and your plugin is irrelevant because no one will download it just to see some websites.
There was an SVG plugin way before browsers supported it natively, but could any web dev actually rely on it?
I bet we'd have seen the video tag on browsers years ago if Flash wasn't there with a poor (GPU acceleration only last year, FFS!) but working solution.
You can talk benchmarks all you want, but it doesn't change the fact that for 99% of consumer facing applications you won't have any noticeable benefit from those native speed.
I'm not talking about benchmarks, I'm talking about actual application development, and the real impact the tremendous number of hours we spend as consumer app decelopers on performance has on the user experience.
I honestly can't even fathom your position, given the context of my experience maximizing application performance. All available CPU cycles are spent quite directly on performance and functionality.
Your position implies to me a myopic inexperience with development beyond the web.
Your position implies to me a myopic inexperience with web development.
All of them. You don't necessarily need C, you simply need to not waste CPU cycles on things that neither improve the user experience nor decrease development costs. You could achieve this with a higher-level language, including something like ObjC and ARC.
Your position implies to me a myopic inexperience with web development.
I'm very familiar with the space. Every cycle counts -- if a cycle is not spent on user experience or decreasing development costs, it's a completely wasted cycle. Browsers waste mountains of cycles.
Modern desktop and mobile software makes heavy use of SMP (threads), SIMD, specific CPU-optimized code paths (in addition to SIMD, and requires that the basic platform infrastructure be as low cost as possible. You simply could not achieve glassy-smooth scrolling and other near-instantaneous UX otherwise.
I seriously doubt that you've ever built a desktop/mobile application given that you "can't think of an application I use on a daily basis that can't be done equally well in the browser.".