3 ms·

What hardware advances giveth, today's beyond-ridiculous-overweight software stacks taketh away.

sliken 3y ago
I think of that as a win. Heavy software stacks create a demand for faster hardware and the market provides. Those of us with use cases that represent a tiny marketshare, but actually need the performance can do so with light software stacks. So the question is, how can we make the overweight software stacks even slower?
- Out_of_Characte 3y ago
  By going back to using interpreted languages. No more precompiled binaries where changing/adding patches and flags require full builds, just stream compiled/compressed source code directly to the target. You could also extern the software to a webserver and only cache small parts of the software on the client. Instead of gigabytes of install sizes you'll be required to have a 1 or 10 gbit network link to run and stream features as you're acessing them.
  - mmoskal 3y ago
    Oh come on! No one would ever do that!... Oh wait
    - LoganDark 3y ago
      whistles in javascript
  - pilgrim0 3y ago
    Coordinating that would be a nightmare. Interesting idea, though
- taneq 3y ago
  Make it “industry standard best practice” to provide devs with absolute top end cutting edge hardware “for productivity and efficiency gains”. Repeat this at every opportunity at conferences and industry events until it becomes ubiquitous. Profit as devs slather abstraction layers, trivial libraries, emulation layers etc. on because “developer time is worth more than CPU time” and “it’s not slow on MY computer”. :D
deleted 3y ago
[deleted]
VelesDude 3y ago
Pffft!!! No it doesn't. By the way, here is my new 'Hello World' app, it is only 380MB + dependencies.
dtgriscom 3y ago
There's a strong rationale for making software developers work on older, limited machines, rather than the latest and greatest flamethrowers. (Of course, that doesn't apply to me.)

I think of that as a win. Heavy software stacks create a demand for faster hardware and the market provides. Those of us with use cases that represent a tiny marketshare, but actually need the performance can do so with light software stacks. So the question is, how can we make the overweight software stacks even slower?

Out_of_Characte 3y ago
By going back to using interpreted languages. No more precompiled binaries where changing/adding patches and flags require full builds, just stream compiled/compressed source code directly to the target. You could also extern the software to a webserver and only cache small parts of the software on the client. Instead of gigabytes of install sizes you'll be required to have a 1 or 10 gbit network link to run and stream features as you're acessing them.
- mmoskal 3y ago
  Oh come on! No one would ever do that!... Oh wait
  - LoganDark 3y ago
    whistles in javascript
- pilgrim0 3y ago
  Coordinating that would be a nightmare. Interesting idea, though
taneq 3y ago
Make it “industry standard best practice” to provide devs with absolute top end cutting edge hardware “for productivity and efficiency gains”. Repeat this at every opportunity at conferences and industry events until it becomes ubiquitous. Profit as devs slather abstraction layers, trivial libraries, emulation layers etc. on because “developer time is worth more than CPU time” and “it’s not slow on MY computer”. :D

deleted 3y ago

[deleted]

VelesDude 3y ago

Pffft!!! No it doesn't. By the way, here is my new 'Hello World' app, it is only 380MB + dependencies.

dtgriscom 3y ago

There's a strong rationale for making software developers work on older, limited machines, rather than the latest and greatest flamethrowers. (Of course, that doesn't apply to me.)