@snaums that's just for backwards compatibility, new API design laws dictate that

@PhilSalkie @robinhouston minkowski() would definitely not be my first choice here either, given the size constraints...

I should definitely try both of these libraries, but i enjoy the puzzle of coding everything from scratch too much, so the only one i currently use is https://www.thingiverse.com/thing:3215997

@PhilSalkie @robinhouston why not just minkowski() a cube for the rounding, or hull() eight spheres? is it better somehow?

Can they get even more incompetent?

"external fun" is translated to "zewnętrzna zabawa", which means "playing outdoors".

Fucking morons.

At least you can switch to English here. On MSDN you get the same useless cesspool, but the only option to switch the language is to modify the URL. And it switches back to translated one when you change the page.

What do you mean 60% compostable. What am I supposed to do, let it decompose 60% then fetch the rest out?

@munroe enter can be anywhere under the thumbs, and it doesn't matter much which one, as they all feel kinda the same, and it also can be changed at any moment in Vial.

ortholinear keyboards really shine when small (48 keys), as their charm is obscured by the need to change hand position on larger boards, although if you're not used to layers it can be a bit intimidating.

to me a 4x12 (split in halves) is the most natural thing ever, but of course YMMV

@munroe it's very hard to find a 1u enter, so here it's probably a cherry or something

@lritter oh Germans

If Artificial Intelligence may be trained using copyrighted data, why not Human Intelligence?

Content-Type: text/shitpost

We have handy words for "clockwise" and "anticlockwise" but we don't have good names for the two main 2D diagonal directions.

So I propose that the south-west to north-east diagonal be called "stonkswise" and the south-east to north-west diagonal be called "antistonkswise"

Programmers are usually fed a steady diet of features and bug fixes. But occasionally they get to work on performance problems. This development methodology is known as intermittent fasting.

If any Mastodon instances are having trouble with their costs growing out of control, ping me and see if I can help lower your bill.

Apparently a recently closed instance was paying $300/month for hosting which is insane to read considering how small of an instance it was. When we had 40k monthly users I was paying about $120/month so an instance with less than 400 total users (not MAU) should be super cheap to run even with a few TB of storage and bandwidth.

It hurts my heart to read instances closing down over costs and finding out they’re paying more than instances 10x their size. 😢

https://newsie.social/@jeff/114513118997692099

The commands 'cd $PWD' and 'cd .' in bash both look like useless no-ops which change into the same directory you're already in. But they're not, and both can be useful.

$PWD is a string variable which caches the pathname that your current directory had at the time you changed into it. It's not automatically updated in between cd commands.

So 'cd $PWD' (or 'cd "$PWD"' if you're being properly careful) changes to whatever directory _now_ lives at the pathname that your actual cwd _was_ when you changed to it.

'cd .' really _does_ just change directory to the same physical directory you're already in, but it's still not useless, because it causes bash to recalculate the value of $PWD.

For example, if one shell is in ~/test, and in another shell you rename ~/test to ~/newname and make a new directory ~/test, then in the first shell 'cd $PWD' will move to the new ~/test, whereas 'cd .' will stay in the original directory but update $PWD to reflect the fact that it now lives at ~/newname.

linkspam!

You will regret using natural keys.

https://blog.ploeh.dk/2024/06/03/youll-regret-using-natural-keys/

saved 2024-06-04 https://dotat.at/:/L1ALY.html

I know people like to make fun of niche operating systems, but for the five years I was at Microsoft I used Windows (10 then 11) as my daily driver. It’s much less stable than a professional OS, but it does kind-of work. I wouldn’t say it’s ready for the desktop. The UI is inconsistent and changes randomly between releases, a load of common software is basically useable only in a VM, it lags and freezes periodically (unlike an OS designed for interactive use, random drivers run a load of things directly in interrupt handlers, so you get latency spikes that you wouldn’t see in a more mainstream desktop OS) and the update process can hose the system, so it’s mostly of interest to people who like tinkering with their machines than people who actually want to get work done. Oh and a load of random bits of the OS have ads, but that’s what you get from a free ad-supported system instead of one developed by an active open-source community.

I don’t think I’d recommend anyone use it as their daily driver or in a work setting, but it’s not totally unusable. It’s not at the level of maturity than you’d expect from, say, Linux or FreeBSD, especially not for client workloads. If you do have to use it, I recommend that you install FreeBSD in a Hyper-V VM for real work. That’s what I did and it works quite well.

The gcc/clang excuse for changing program behavior, often introducing bugs and security holes (see https://www.usenix.org/system/files/usenixsecurity23-xu-jianhao.pdf), is performance. But a new paper https://web.ist.utl.pt/nuno.lopes/pubs/ub-pldi25.pdf modifies clang to eliminate most (all?) such changes, and finds negligible effect on benchmarks.

@lritter sorry

@lritter for a failing drive there are procedures to recover from them. How would you recover from such a collision? Even if it's a video game (as opposed to someone blaming you for losing millions per hour), if a collision happens, it's likely to repeat again and again, unless it's a roguelike or something — then i can see recovering by just starting another run. In a more persistent setup, the faulty data may have originated from 60 hours of saves ago.

@lritter how do you handle (the 128-bit) hash collisions in this setup? do i understand correctly the idea of using hashes as keys? does it mean literally discarding the actual key in favour of its hash?