3 ms·

Not just 1000kb. netflix.com (which doesn't even do anything): 1.6MB CNN: 3.4MB NYT: 4.1MB Guardian: 5.7MB IGN: 69.5MB I still use jquery when I'm targeti

Not just 1000kb. netflix.com (which doesn't even do anything): 1.6MB CNN: 3.4MB NYT: 4.1MB Guardian: 5.7MB IGN: 69.5MB I still use jquery when I'm targeting ancient devices. Some of them still run Presto. Performance is fine, file size is fine - and drastically smaller than any of the sites above! (I can see why one might not want jquery as a dependency of a dependency though.)

t0astbread 5y ago
Are you sure you weren't loading a video on IGN?
- Ardren 5y ago
  Yep, looks like it's a video. But it's auto-preloaded and playing even when not visible...
beebeepka 5y ago
I used to work on low power/ancient devices running presto or blink. Performance was much better on opera 12.80 or so. At some point I had to support an outside team working on external application running inside ours. These guys used jQuery in ways it shouldn't be used when performance is an issue. Had to spend a few hours reducing their code to mostly CSS and just a tiny bit of honest to god js that even presto can understand and render. Point is, it's really easy to overuse and that can have an effect on performance, even on presto
- sanitycheck 5y ago
  We may know the same devices - designed to run Flash Lite acceptably then made to just barely support HTML/JS with heroic engineering efforts later. Nobody believes how slow they are until they try. I think if someone queries the DOM a lot on these things, especially in response to keypresses, they're in trouble whether or not they're doing it with jquery.
  - beebeepka 5y ago
    The lowest common denominator I had to deal with were some quite expensive, for the hardware, Arris devices. Roughly 10 times slower than a 2 core skylake and similar. I wish I was joking. As you say, people have no idea what slow is until they have to code for these. I've played with some fairly decent machines as well. Quite a bit faster and cheaper but you can't just magically replacement millions of devices every time something new comes along

t0astbread 5y ago

Are you sure you weren't loading a video on IGN?

Ardren 5y ago
Yep, looks like it's a video. But it's auto-preloaded and playing even when not visible...

beebeepka 5y ago

I used to work on low power/ancient devices running presto or blink. Performance was much better on opera 12.80 or so. At some point I had to support an outside team working on external application running inside ours. These guys used jQuery in ways it shouldn't be used when performance is an issue. Had to spend a few hours reducing their code to mostly CSS and just a tiny bit of honest to god js that even presto can understand and render. Point is, it's really easy to overuse and that can have an effect on performance, even on presto

sanitycheck 5y ago
We may know the same devices - designed to run Flash Lite acceptably then made to just barely support HTML/JS with heroic engineering efforts later. Nobody believes how slow they are until they try. I think if someone queries the DOM a lot on these things, especially in response to keypresses, they're in trouble whether or not they're doing it with jquery.
- beebeepka 5y ago
  The lowest common denominator I had to deal with were some quite expensive, for the hardware, Arris devices. Roughly 10 times slower than a 2 core skylake and similar. I wish I was joking. As you say, people have no idea what slow is until they have to code for these. I've played with some fairly decent machines as well. Quite a bit faster and cheaper but you can't just magically replacement millions of devices every time something new comes along