As in many large projects, even more so with a large company,
the point is not to react when the problems are happening,
it is to preempt these problems, foresee them and prevent their happening.
So indeed, by 2018, even though Intel has not yet fallen, it's actually already late.
The roots of the problems seems to be earlier, and that's where the CEO, and the Board, should have reacted.
Wow, LZ4 high compression mode has become really fast, at least on my system.
I don't need to settle on some lower compression setting now. That's -9 all the way.
To begin with, it requires the distance between 2 consecutive matches to be exactly 65536. This is extremely rare. Mountains of files never generate such a situation.
Then it needs to employ a repcode match as the match following the 65536 literals. Repcode matches are more common after short literal lengths (1-3 bytes). Needless to say, 65536 is far from this territory, so it's uncommon to say the least.
Finally, the block splitter must be active (hence only high compression modes),
and it must decide to split the block exactly at the boundary between the literals and the repcode match.
So this is not 0, since Google found a sample, but all these conditions _together_ have an astronomically low chance to happen, as in competitive with winning the Powerball jackpot. I wouldn't worry so much for my own dozens of archives.
This guy has no idea what he's talking about.
Yet again another click-baity title, followed by an angry rant, the topic of which has nothing to do with C after all (but readers have to go through an impressive amount of noise to deduct that).
Quite the reverse actually, the btrfs estimator is way worse than the zstd one. By using the btrfs estimator, you leave a ton of compression ratio on the table, for no good reason.
My own experience with this group has been remarkably similar. Oversized ego, dismissive of others, overtly aggressive to competing ideas and technologies, the Rust core team is simply one of the worst I've ever had to make contacts with.
The overall feeling when dealing with them is that they are so sure that they represent the "future of programming" that they want the rest of the world to burn now, and no one else than themselves to benefit from the aftermaths.
(I used to be active on Rust in the 2014-2018 era, but then moved away, essentially disgusted by the attitude).
Well, indeed, there are limits to copyrights that are supposed to be applicable when using trivial common names.
But ever since a certain company decided to call itself "fruit", and then go on rampage attacking small players which themselves used to be called "fruit" under the petty reason that they are actually producing and selling "fruit", there is a sense in US that, as long as you got the balls and the lawyers, there is just no limit. Limits of the rules, even when written, are for "others".
