5 ms·

> This is a perfect example of why the problem isn’t... Depends on how you frame the problem. If you declare the problem is that although batteries became way

> This is a perfect example of why the problem isn’t... Depends on how you frame the problem. If you declare the problem is that although batteries became way more efficient you don't get out more hours because they are wasted, then the story is a different one. Same when you don't have an abundance in RAM but are forced to use certain programs and applications. I have 64GB Ram these days, colleagues at clients of mine only have 16GB and they face certain challenges I don't, because of the tools forced upon them by their superiors. These problems can be real, they can be "artificial" (there is a philosophical note to this somewhere ;)), but in the end, there is undeniable truth that launching a whole browser engine for each and every app can be and indeed is wasteful compared to alternatives. Of course if you don't see this as a problem "ex falso quodlibet" takes precedence and it all becomes futile to discuss :)

thrnkkm 3y ago
It goes opposite way as well. I have workstation with 128GB ram with a few terabytes of storage, I can run full stack with everything in single machine. I also have VM snapshots, versioning etc... There is simple script that installs all deps and setup dev machine. My colleagues have tiny Macs with 16GB. To accommodate them, we had to split mono dev setup into separate K8S cluster. On single machine I could easily split test build process. Now we have spaghetti of dependencies. And spinning up secondary dev instances is not permitted due to high AWS cost. So investing result binary (like this blog post) is now impossible.
- rand846633 3y ago
  > And spinning up secondary dev instances is not permitted due to high AWS cost. Time for a new employment opportunity.
  - deleted 3y ago
    [deleted]
ToucanLoucan 3y ago
> there is undeniable truth that launching a whole browser engine for each and every app can be and indeed is wasteful compared to alternatives. Wasteful and always, always a worse experience. I'm sorry if this ruffles feathers here or people feel called out, but I can FEEL the difference in these web-cruft apps every single time, full stop. I would Pepsi challenge this as many times as people want and I will eat my snow boots if I get it wrong. If you make your app with web tools, I will not use it if I can conceivably manage doing so. And if I must, then I guarantee you I will do it as grudgingly and as little as I possibly can.

thrnkkm 3y ago

It goes opposite way as well. I have workstation with 128GB ram with a few terabytes of storage, I can run full stack with everything in single machine. I also have VM snapshots, versioning etc... There is simple script that installs all deps and setup dev machine. My colleagues have tiny Macs with 16GB. To accommodate them, we had to split mono dev setup into separate K8S cluster. On single machine I could easily split test build process. Now we have spaghetti of dependencies. And spinning up secondary dev instances is not permitted due to high AWS cost. So investing result binary (like this blog post) is now impossible.

rand846633 3y ago
> And spinning up secondary dev instances is not permitted due to high AWS cost. Time for a new employment opportunity.
- deleted 3y ago
  [deleted]

ToucanLoucan 3y ago

> there is undeniable truth that launching a whole browser engine for each and every app can be and indeed is wasteful compared to alternatives. Wasteful and always, always a worse experience. I'm sorry if this ruffles feathers here or people feel called out, but I can FEEL the difference in these web-cruft apps every single time, full stop. I would Pepsi challenge this as many times as people want and I will eat my snow boots if I get it wrong. If you make your app with web tools, I will not use it if I can conceivably manage doing so. And if I must, then I guarantee you I will do it as grudgingly and as little as I possibly can.