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.

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

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.

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

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

The video link 100% cognitohazard. DO NOT CLICK.

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.

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.

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

std::chrono::neutronstar_clock

Lettme introduce you to ackermann's function:

int ack(int m, int n) {
    if (m == 0) {
        return n+1;
    } else if((m > 0) && (n == 0)){
        return ack(m-1, 1);
    } else if((m > 0) && (n > 0)) {
        return ack(m-1, ack(m, n-1));
    }
}

You won't run out of stackoverflows any time soon.

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

X Y problems are absolutely crud when you have to ask first the stupid version to be able to ask the actual question about X.

I recently switched my default search from Google to DuckDuckGo: Google has begun refusing to find anything while exact same search on DuckDuckGo just works. Google is slower because I have to think+ignore first half of the page due to Ads/SEO crud.

The video link was surprisingly SFW. My expectation was piercing a nail through my skull make me UwU.

The day I configured git to use Geany for commit messages with a separate config specifically tuned for this, it improved my life by 300%

~$ cat ~/bin/gitedit
#!/bin/sh
exec /usr/bin/geany -i -s -t -c ~/.config/gitgeany $@

Then in git config: git config --global core.editor "gitedit"

My most common typo is gti and I'm considering to alias it as rm -rf --no-preserve-root /

If you clicked, please purge YT history and apply amnestics to your ears and eyes.

• SCP staff probably

I have bought a few ukranian beers if that matters. Every time I take a sip I feel their pain and terror. It is not a nice feeling. I think there is some quantum entanglement or just fear of losing your ground.

The Putfuck re-started a 1940 era war by breaking their former promises, in a time period the entire humanity is burning up due to our collective failure to take care our future.

The time and resources wasted by this war has no number and no cost other than denying our own future existent on this blue marble. The clock is ticking, and my only hope is that humanity survives, despite its arrogant and violent nature.

More likely a group of neurons, and they fight the rest of the network to try get more basil. And within single cell that shit is hard-coded into the genome.

On arch, UEFI boot vars are mounted at /sys/firmware/efi/efivars. It's unwise to rm -rf them....

I had a similar debacle, when I managed to corrupt a btrfs file system to point it wouldn't mount again...

I was preparing it to have as my main system on bare hardware. I had accidentally mounted the same block device simultaneously in the host and guest: kablamo silent corruption and all 5 hours of progress lost.^*^ :(

*shred the guest VM, host was ok.

I read the entire article, thanks.

volatile int blackhole;
blackhole = 1;
const int X = blackhole;
const int Y = blackhole;

Compiler is forbidden to assume that X == 1 would be true. It's also forbidden to assume that X == Y. const just means the address and/or the data at the address is read only. const volatile int* const hwreg; -> "read only volatile value at read only address hwreg". Compiler can assume the hwreg address won't magically change, but can't assume the value read from that address won't.

Holy cow.

I clicked the link with SUS knob set to 900% and the other hand on the main breaker. It did not disappoint.

After 362879 wrong answers you will pass. Or after 2,0922789888×10¹³ tries if it's a fancy 4x4 grid.

I'm considering to replace the TIM (repasting) + thermal pads at some point... The card is now ~5 years old, and if the paste goes bad that would be end of it. The dust that all boards accumulate overtime is also a risk factor of how long components last.

gdb> break before it crashes
gdb> record full
gdb> continue
(segfault)

gdb> set exec-direction reverse

To produce 1 commit, I end up rebasing the damm thing at least 3 times. If there is an problem, it's at least 2³ times.

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.

Tätä odottaessa, kosmos24.

I fckd up a git rebase -i today with git commit -a --amend...

Thankfully git reflog allowed me to assemble the branch again ... from pieces.

GameBoy Color with a single game: Pokémon Red.

Next time I was able go to the shop they had upgraded to GameBoy Advance and no GB/GBC games were to be never found again. It was the best/worst thing I ever got. :'(

I was suspicious as heck of this link, but I thank you for being benign.

<tinfoilhat>This post is literally an pwns-list of users admitting what they use as password manager that may be stolen.

I encrypted an file, I put it on a device and mostly forgot it exists. Now if service locks me out I have go hunting.</tinfoilhat>