I hope you sighed deeply and then said "well, guess I have to murder your friend now too".

As with every software/product: they have different features.

ZFS is not really hip. It's pretty old. But also pretty solid. Unfortunately it's licensed in a way that is maybe incompatible with the GPL, so no one wants to take the risk of trying to get it into Linux. So in the Linux world it is always a third-party-addon. In the BSD or Solaris world though ....

btrfs has similar goals as ZFS (more to that soon) but has been developed right inside the kernel all along, so it typically works out of the box. It has a bit of a complicated history with it's stability/reliability from which it still suffers (the history, not the stability). Many/most people run it with zero problems, some will still cite problems they had in the past, some apparently also still have problems.

bcachefs is also looming around the corner and might tackle problems differently, bringing us all the nice features with less bugs (optimism, yay). But it's an even younger FS than btrfs, so only time will tell.

ext4 is an iteration on ext3 on ext2. So it's pretty fucking stable and heavily battle tested.

Now why even care? ZFS, btrfs and bcachefs are filesystems following the COW philisophy (copy on write), meaning you might lose a bit performance but win on reliability. It also allows easily enabling snapshots, which all three bring you out of the box. So you can basically say "mark the current state of the filesystem with tag/label/whatever 'x'" and every subsequent changes (since they are copies) will not touch the old snapshots, allowing you to easily roll back a whole partition. (Of course that takes up space, but only incrementally.)

They also bring native support for different RAID levels making additional layers like mdadm unnecessary. In case of ZFS and bcachefs, you also have native encryption, making LUKS obsolete.

For typical desktop use: ext4 is totally fine. Snapshots are extremely convenient if something breaks and you can basically revert the changes back in a single command. They don't replace a backup strategy, so in the end you should have some data security measures in place anyway.

*Edit: forgot a word.

IDEA isn't Java-only. Most of the other languages are available as plugins. IDEA is typically the go-to IDE for multilanguage projects.

"Der Lockdown war unnötig, sieht man doch an den geringen Infektionszahlen."

Some idiots keep using one of my email adresses for god knows what, ending up in me receiving newsletters and shit. Since actual user accounts are associated, I typically recover the password (since its my email adress) and then delete the account.

There are a few websites with similar restrictions though. They are completely fine sending shit to email adresses they never bothered to verify, but reject logins from countries (or even US states!) that they don't want. Morons.

This doesn't add up....

She's taking the picture in landscape mode but the post clearly shows it as portrait!

Looks like they should have called that function sortOf()

Wird langsam Zeit, sich mit auf die Straße zu kleben...

Um die Aktivisten zu schützen, stellte ein Bauarbeiter in Eigeninitiative einen Bauzaun um die Personen auf der Straße

Gigachad. Sehr geil.

Ich hab respekt vor den Aktivisten, dass die das so über sich ergehen lassen, ohne sich zu wehren (und damit aber natürlich weiter zu eskalieren, leider). Moralisch sehr respektabel.

... auch wenn ich solchen Leuten wie diesem LKW Fahrer da gönnen würde, dass der Getretene ihn einfach zu Boden reißt und ihm dabei das Bein bricht. Man wird ja noch Träumen dürfen ...

"Regenbogenterror". Schon wenn ich das lese schwillt mir der Kamm. Genau wie das rumgeheule von "Sprachdiktatur" beim Gendern.

Dabei zwingen weder LGBTQ noch gendergerecht Sprechende ihre Meinung anderen auf oder terrorisieren diese. Umgekehrt hingegen wird von den Gegnern Freiheit unterdrückt um ... äh..... Freiheit zu schützen? Fuck for virginity oder so? Dumme Idioten.

Security aside (because that's my employers problem), Teams is just aweful.

The UX is all over the place, likely because of the feature creep forcing a lot of dev departments to collaborate.

It just does too much. I don't need an all on one solution, I need a communication tool.

The chat looks like WhatsApp, not like a proper professional comms channel. Maybe there's a setting buried somewhere.

The meetings are more miss than hit. For every working meeting I have 5 meetings where something doesn't work. Multiple retries to join; or it picks the wrong mic, speaker and/or camera; or chat within the meeting doesn't work for some participants so they can't share or see links; video streams being disconnected and reconnected depending on who currently speaks (which looks extremels annoying); and probably a ton more I zoned out).

Slack on the other hand mostly just works. As a chat tool. What it is supposed to be.

Viele Entwickler setzen viel zu oft leichtfertig irgendwelche Bibliotheken und Toolkits ein, ohne sich wirklich damit zu beschäftigen, was die eigentlich genau treiben. Da ist in den meisten Fällen kein böser Wille. Da sitzt natürlich keiner und denkt sich "hehe, die dummen Nutzer zock ich jetzt ab und mach einen Deal mit Google/Facebook".

Aber es ist halt fahrlässig und zum Teil Faulheit. Man braucht Crashreports? Super, gibt's schon. Eine Abhängigkeit rein, paar Einstellungen gesetzt, läuft.

Das betrifft auch nicht nur große Firmen. Das machen einzelne Entwickler, kleine Softwarebuden, usw. Die Erwartungshaltung, dass Software in kurzer Zeit fertig werden muss und möglichst im Wochen-Turnus neue Funktionen erhalten muss, befeuert das Problem und die oberflächliche Herangehensweise nur weiter. Gute Software, die richtig durchdacht und optimiert wird, gibt es immer seltener, bzw. geht immer häufiger in der Masse an rausgerotzter Software unter.