3 ms·
> As far as I can tell, the web is not on track to catch up to native platforms in terms of customer experience anytime soon. For apps (not necessarily games),
by pcwalton 11y ago
> As far as I can tell, the web is not on track to catch up to native platforms in terms of customer experience anytime soon.
For apps (not necessarily games), I'm convinced these days that the problem is not JavaScript at all, and so I'm not sure most of your points are relevant. Native apps on any platform barely ever use SIMD (outside of the system stack, which the Web APIs also use), for example. The problem is that the CSS rendering stack is old and needs to be revamped.
As far as games go, I'm not in the industry, and I completely believe you. But I'm optimistic, with Web Assembly and a redone browser architecture, the Web is on the right track. Not there yet, of course.
- Touche 11y ago> The problem is that the CSS rendering stack is old and needs to be revamped. I thought that was the point of the 5+ year long flexbox? Are you telling us that didn't do the job?
- pcwalton 11y agoFlexbox wasn't about performance, and these issues are largely about performance. I think Flexbox pretty much fixed the complaints about the expressiveness of CSS for UIs (unless you're forbidden from using it for browser compatibility concerns, of course).
- Touche 11y agoIt certainly wasn't sold as "not about performance". Performance was blamed on things like floats in the past, and flexbox was supposed to solve the needs without sacrificing performance. Now you're saying that CSS needs to be revamped. Great. Anyone working on that? Either way we're looking at, what, 5 years minimum before first browsers have this new thing that's really about performance this time, for real.
- pcwalton 11y ago> It certainly wasn't sold as "not about performance". Performance was blamed on things like floats in the past, and flexbox was supposed to solve the needs without sacrificing performance. That's not true. Do a search for [flexbox floats performance] and you'll see that the goal was not to improve performance of floats. Floats are only a performance problem in parallel implementations, which nobody was talking about at the time flexbox was created. > Now you're saying that CSS needs to be revamped. Great. Anyone working on that? Gotta love HN snark. I work on that every day, 50+ hours a week. And I'm not saying revamp the specs. I'm saying revamp the implementation.
- chadaustin 11y agoHi Patrick! To be clear, I think the web platform is largely headed in the right direction. It's just a question of velocity, especially relative to other application ecosystems like iOS's App Store. When a product cycle is on the order of a couple years, but even simple new capabilities (like XHR priority) take years of discussion before anyone implements it at all, then we basically can't assume anything beyond the current web capability set when planning a product. And the current web capability set is not good enough for the kinds of experiences people take for granted on native! I hope that changes! I think the web would move faster if browsers would stop cooperating so much with each other. Increase the rate of churn; let the best APIs win. Some niggles: I personally think anti-fingerprinting measures are overweighted, especially given that preventing fingerprinting is basically a lost cause. I also think there's room for more "unspecified behavior" in the web, e.g. it sucks that we have to pay a penalty so that NaN can have perfectly consistent behavior on all platforms in SIMD.js.
- pcwalton 11y agoI agree that we need to move faster. (Given my struggles as of late with trying to get 5-year-old OpenGL functionality working on the Mac, though, I wouldn't necessarily paint Apple as the gold standard here. At least in my experience, Apple is probably the worst of all the major native vendors when it comes to things graphics-intensive apps care about.)