Same person as @Gobbel2000@feddit.de, different instance.
I was momentarily confused that this article is pretty much the script of a YT video by Hardware Unboxed I saw recently, but then I noticed that he is literally the author.
While all these developments point in a very worrying direction, I think there are some positives to this: Fewer performance gains means longer upgrade cycles, longer support windows and less pressure on consumers to keep soending money on upgrades (although the eventual upgrade is now way more expensive).
Can you verify this? Maybe we should require Debian contributors to prove they are adults. /s
Nope, never use it. I know how to write code myself.
But you can just as well make an exception to allow errors when -e is enabled with something like command || true, or even some warning message.
I feel like, while it does occur, allowing errors like this is more unusual than stopping the script in an error, so it’s good to explicitly mark this case, therefore -e is still a reasonable default in most cases.
It’s wild that one of the problems is that the kernel doesn’t use floating point numbers.
Right, which occurs in particular when dealing with graphs, which are basically matrices and usually sparse. Large graphs are what I used this format for, however I also needed edge weights, so the first column was still required for that.
The CSR (compressed sparse row) format is a very simple but efficient way of storing sparse matrices, meaning matrices with a large amount of zero entries, which should not all occupy memory. It has three arrays: one holds all non-zero entries in order, read row by row, the next array contains the column indices of each non-zero element (and therefore has the same length as the first array), the third array indices into the first array for the first element of each row, so we can tell where a new row starts.
On sparse matrices it has optimal memory efficiency and fast lookups, the main downside is that adding or removing elements from the matrix requires shifting all three arrays, so it is mostly useful for immutable data.
In my opinion yes, Debian is the best choice for server machines, especially on the homelab scale.
How does this even work? I get the redirection part, but how is the command executed in a detached state?
To be fair, nowadays the Linux kernel does rely quite a bit on resources from major software (and hardware) companies.
That was so eye-opening for me when I figured out you can just grep a block device for files unlinked by the file system but not yet physically overwritten. Magically reanimating lost files can be such an incredibly simple operation.
I feel like the truth lies somewhere in the middle, but this one I absolutely 100% agree with:
Even still I find this a bit shortsighted. You never know if in the future there might be more than 4 billion bus lines and you run out of numbers.
I prefered the previous chart.
I’m all for having the ability to do these shenanigans in principle, but prefer if they are guarded in an unsafe block.
Remember that in 2023 RedHat restricted access to the source code of RHEL packages, which had a big impact to lots of server distros. This article explains really well why that’s problematic:
https://sfconservancy.org/blog/2023/jun/23/rhel-gpl-analysis/
Clearly we need self-centering support from editors.
So true. Every time I have to look up how to write a bash for loop. Where does the semicolon go? Where is the newline? Is it terminated with done? Or with end? The worst part with bash is that when you do it wrong, most of the time there is no error but something completely wrong happens.
I have no doubt that the companies will keep high margins and incentivize people to keep spending, but the customers have a choice when to upgrade their hardware and I believe based on these developments that they will choose to upgrade less frequently than they used to.