C++: you sure you want to do this? This will either: a) blow your foot off b) be too fast to be measured in micro-benchmarks.

b. B. B. a. then B.

You have chosen to simultaneously blow your arm off and be the fastest code thing on the planet. Congrats. Yes.

name your function as malloc() and see to world burn and generate bugs at factorial rate.

Please, no, I get flashbacks from my 6-month journey (still ongoing...) of the code review process I caused/did. Keeping PR scope contained and small is hard.

From this experience, I wish GitLab had a "Draft of Draft" to tell the reviewer what the quality of the pushed code is at: "NAK", "It maybe compiles", "The logic is broken" and "Missing 50% of the code", "This should be split into N PRs". This would allow openly co-develop, discuss, and steer the design, before moving to nitpicking on the naming, formatting, and/or documentation details of the code, which is likely to drastically change. Drafts do work for this, but the discussions can get uncomfortably long and convolute the actual finishing of the review process.

Once both reviewer(s) and the author agree on the code design, the "DraftDraft" could be collapsed into a link in an normal Draft to be mocked next. The scope of such draft would be limited by the earlier "DraftDraft".

It's a FOSS project, so wish me luck, as you can now get it in the mail eventually.

I had to run a makepkg today, which now includes my self-written pieces of code in master. So I'm eating my own dog food now, and it's good. Also, the itch from before has somehow relieved.

That's because people are now aware of all of this shit happening, and some discreet day, just flip off the power from the house, doing indescribable things, and listens to the voices in their heads. And nobody will know.

Radeon RX 580 until the VRAM dies to the idle @50°C temps or the support is removed from the kernel...

The video link 100% cognitohazard. DO NOT CLICK.

There were no unit tests and previous dev had opened the pandora's box with half-written implementation. Gasp

C++: The project is now led by university research comitee optimizing essays/second and consists 1k lines of template hieroglyphs.

The shim module smuggles GPL-only kernel symbols into the non-GPL binary blob. Because the actual module using those symbols is not GPL compatible this violates the GPL license.

From Linus Torvalds mouth:

anybody who were to change a xyz_GPL to the non-GPL one in order to use it with a non-GPL module would almost immediately fall under the "willful infringement" thing, and that it would make it MUCH easier to get triple damages and/or injunctions, since they clearly knew about it.

In short, nvidia is playing with "please sue me" button.

Until you would have to replace a HDD: +23 hours of nerve racking RAID repair time for 10TB drive at 120MB/s Even with some advanced (like ZFS etc.) system you can't go around the fact the HDDs are slow.

And when the HDD fails, you can't read it. It's toast. Some cheap non-volatile memory devices are like this too, but good ones go into read-only mode and you can at least attempt data recovery from them if no better option is left.

I'm liking that it is possible get cheap+good 1TB NVMe devices for less than 100€. The consumer SATA market for large SSDs (capacity over 1TB) is unfortunately quite dry. I need replacement for HDDs and even if the speed is capped by SATA bus it would be an massive improvement.