2 ms·
I believe there's a spiraling pattern, where the same ideas reappear every N years but with slight internal or ecosystem changes. I'm not sure if we're running
by agumonkey 3y ago
I believe there's a spiraling pattern, where the same ideas reappear every N years but with slight internal or ecosystem changes. I'm not sure if we're running or circle of if there's a real slow progress.
- hutzlibu 3y agoI think it is mostly just adopting. To new hardware, new demands, new plattforms. There is maybe some progress on a academic level, but I don't think we progress fast on the fundamental level, on how to write better code. There are slight improvements here and there, but it is mostly just different. And more complex. Or rather new tools are needed because everything gets more complicated (some say bloated). That being said, the new thing that I am learning is general purpose GPU compute. That is quite new and useful (but hard). But it is an improvement.
- agumonkey 3y agoYes, that is indeed part of it. Everything changes, the ideas have to swim on top of that moving soil. And at times some integration occurs where a lot of ideas suddenly merge into a new cleaner brick.
- hardwaresofton 3y agoI think it's real slow progress, and sometimes even, quite fast. It's the same ideas, but I will assure you that most of the large things that people get crotchety about are legitimate moves forward. People were complaining about "docker" (i.e. cgroups + namespaces + some CLI UX) not too long ago and now you'd be dumb to try and deploy most applications without at least having that there. How many people are wrangling their own cgroups and namespaces (not counting systemd, which is another thing people fought, tooth and nail)? Should we all be doing 1 user per workload like the good 'ol days? Or maybe 1 machine/VM per workload like the 'ol 'ol days?