I want to see the trend of maximal libraries in javascript now.
Show HN: 2 MB JavaScript library for building front end applications with a lot of useful interactive ui components.
Show HN: 2 MB JavaScript library for building front end applications with a lot of useful interactive ui components.
The fight for really small frameworks is most relevant for consumer apps, especially ones consumed on mobile.
But even on mobile, it's primarily relevant because customers get minimal value from your app or are bad at accurately assessing the value they get.
In my day job, I work on a system where business users spend several hours a day using it. Loading a MB of minified JS has such a limited effect on the overall time it takes users to get their work done, it's almost irrelevant. Though, per the point about accuracy above, I wonder how it affects our demos.
I sure missed the simple, small, usable, multi page site we used before the "upgrade" to the single page app competitor! (On top of that, the old one worked fine on mobile. The new one, not at all.)
Still, I can't help but think that the real low-hanging fruit is the slow VPN. How much time was wasted waiting for the network? So many companies are penny-wise pound-foolish.
It's not impossible but it's a tough sell arguing for a 50k expenditure for better hardware for the VPN will actually save the company time worth >50k.
I'd say that there's a point where the overhead of spending money becomes high enough that companies will waste a lot of expensive employee time to avoid requisitioning something.
And although companies track high level time costs in a project management context, I'm not sure whether they're conscious of the way that time use can be driven by bits of waste.
That sorta fits "penny wise, pound foolish", but sorta doesn't.