3 ms·
This reads like incoherent rambling around one thought without ever finding any justification for this thought. There are exactly same dynamics between hardwar
by scotty79 4y ago
This reads like incoherent rambling around one thought without ever finding any justification for this thought.
There are exactly same dynamics between hardware and software in free as in proprietary. The only difference is that free software is not sold directly. But it still is created and still acquires new features that need better hardware.
- sbierwagen 4y ago>This reads like incoherent rambling around one thought without ever finding any justification for this thought. That is the house style of The Register, yes.
- livrem 4y agoI did not really understand what they were trying to say, but I think the dynamics for free (especially non-commercial, community-driven projects) vs non-free are different The former do not have the same strong need to keep adding stuff beyond what makes sense. I am increasingly happy to see small tools that does what they need to do and can almost immediately move to maintenance-mode forever and just provide important bug-fixes and every now and then add support for new platforms. But what about progress? A fork can do that. Or some competing free tool. Also the link to the article by Wirth at the end of the article, A Plea for Lean Software, was great and I never read that before, so I am happy that The Register linked to it (https://cr.yp.to/bib/1995/wirth.pdf https://cr.yp.to/bib/1995/wirth.pdf).
- AtlasBarfed 4y agoI think the overarching point, if there is one, is that with Moore's law and Dennard scaling running out of real-world impact between generations, the churn of new hardware is becoming more forced-consumption / deck chair rearrangement on the software side rather than delivering value / efficiency that utilizes new hardware capabilities. The software industry has been slowing down with worse and worse runtimes, It used to basically be compiles C/C++ type stuff in the 80s/90s, 2000-2010s was JVM/dotNET, and now it is Javascript, although with Typescript the industry can probably get VM performance back to the JVM days. (very coarse paintbrush there of course). At some point the industry will need to wring out optimization from the software stack to get closer to hardware again. The good news is that hopefully dependency churn will reduce, because interfaces may finally become more stable, as will implementations. Because ye gods is dependency churn a headache these days. As I get older it just gets more annoying.