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

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

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.

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".

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.

A far better solution is green hydrogen fuel cell based EVs

The physics are agaist this, batteries are more efficient than fuel-cells, so fuel-cell EVs would put infact more load on the grid in the end than battery based EVs.

Itse olin myös sen +10v löyhässä hirressä, mutta terveyden huolto petti lupauksensa ja kiskaisi mut mäkeen:

"ei kannata hoitaa koska potilas liian huonossa kunnossa, että voitaisiin toteuttaa hoito joka oikeesti auttaisi"

Nyt olen sitten paikallisen arvauskeskuksen vaiva ja sain Kela Black cardin^tm^, mutta hintana oli myydä oma tulevaisuus.

The video link 100% cognitohazard. DO NOT CLICK.

It gets more cursed the more you look at it:

• you have to convert the coordinate axes (swap z,x,y)
• then you find out the right/left handed is flipped
• now your brain melts if you even try think how to solve this with transformation/rotation, what ever.

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

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

I think the difference with Dolphin is that it now emulates an extinct system(s), so it cannot possibly compete with the actual thing. They did have a close call last year, if I remember, and they pretty quickly went into "jettison all illegal shit out of the code base NOW." -mode.

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.

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.

This cannot be an coincidence. I may actually finished something this time.

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.

Bugs that have existed for +3 years in a component and are nearly immediately visible to the end user. Oldest source line I touched was from before 2010.

std::chrono::neutronstar_clock

On 1st gen ryzen cpu (until rzen3), don't have branch recording with "perf record -b" So no way to make your program +15% faster with profile data/PGO/FDO without effort. 😞