4 ms·
As people have pointed out, that's Chrome-only at the moment but that's also a big moving of the goal-posts. Your original comment was “far behind in a variety
by acdha 9y ago
As people have pointed out, that's Chrome-only at the moment but that's also a big moving of the goal-posts. Your original comment was “far behind in a variety of features that are useful to a much bigger % of the web” — precisely how much user-visible benefit do you think comes from a feature which may accelerate the first load slightly?
If that was that critical, it'd be easy to point to e.g. webpagetest.org traces showing Chrome loading a site significantly faster. And, yes, you can find differences in microbenchmarks but it's pretty rare to find something where rel=preload is a game-changer.
- fixermark 9y agoHow much user-visible benefit? Do a quick text search of this Hacker News thread for people talking about Firefox "feeling" slower than Chrome. Preload is a big underlying "why" of that experience.
- acdha 9y agoAgain, do you have any firm data supporting the assertion that this form of network prefetching is so critical? I've read many comments where people mention performance in ways suggesting they have issues with UI performance, launch time, extensions, etc. Optimizing cold-cache performance the first time someone visits a site won't help with that at all.
- eridius 9y agoSafari Technology Preview is adding support for <link rel=preload> as well. I'm not sure what the current state is, but the last 2 releases both had changes that were related to this.
- Touche 9y agoMoving goal post? Preloading is useful on every single web page that, for example, loads a script. Not just 3D games, but any web page with scripting.
- acdha 9y agoKeep reading the entire comment: the point wasn't that rel=preload isn't useful but rather questioning the assertion that it's this huge game-changing feature which is causing ordinary people to switch browsers. If you actually run benchmarks, it's nice but hardly a game-changer, especially in the post-HTTP/2 world. If you're concerned about cold page load times most sites will see significantly greater benefit from using fewer blocking resources.
- Touche 9y agoI don't recall saying that it was "game-changing", I said that it was useful for a large number of web pages, unlike webassembly which is useful for a very small number of specialized needs. Same for modules, or Intersection Observer or many other features that FF is not shipping. Stop trying to prove me wrong and understand my point. Firefox is slow on stuff that makes regular old web developers lives easier, because they're chasing 3d games.
- acdha 9y agoThe problem is that you made a very broad and sweeping claim and then picked a very weak supporting point for it. Web Assembly may not change the game for every or even most sites but for sites which are performance sensitive it's an extremely user-visible improvement. > Stop trying to prove me wrong and understand my point. I think you should focus on making your point more clearly rather than defending what was clearly a. For example, you cite modules as something which is apparently a big deal for web developers but not shipped by Firefox. Sounds like Mozilla needs to get cracking … unless you know that only Safari has shipped it and the Chrome, Firefox, and Edge teams all have it available but behind a feature flag for testing: https://www.chromestatus.com/feature/5365692190687232 https://www.chromestatus.com/feature/5365692190687232 That doesn't support your narrative that the Firefox team is ignoring this or that they're behind the market — and since anyone who isn't targeting only the latest version of Safari is either polyfilling or continuing to use their existing strategy, so there's an upper bound on how bad that can be, too. Similarly, with Intersection Observer you can see that it was enabled in FF50 but had stability issues which lead to it being disabled and is likely to be re-enabled in FF54 based on testing. Unless you have some evidence that the developers who were working on that were pulled off to work on WebAssembly it doesn't seem like an especially compelling argument. Again, I'm not saying that any of these things are useless — only that the narrative you're insisting on where Mozilla is ignoring web developers doesn't seem to be well supported by the evidence. At least for the projects I work on, I'd level that criticism at Safari or Edge first and in the much fewer cases where either Chrome or Firefox has a bug or limitation I need to work around it's about as likely to be Chrome as Firefox requiring extra work.