they have nice cameras. but the battery life is attrocious and sometimes will run into radio issues (iirc fixed only one or 2 generations ago)… lack of otg support is also one minor issue

also Huawei laptops. Jfc what a trashy counterfeit of a MacBook and if you get an AMD one, better also get a good cooling stand. The keyboard is terrible and costs a fuckton to replace and generally the repairability is like with macs, the USB ports are built in a way that just begs for either them or your peripherals to be broken, they might overheat while charging, they ship bloatware and the speakers are ridiculously quiet. My friend’s mom bought her one contrary to my advice to get a second-hand thinkpad or just any other business-line laptop and it she had to return the first shipment because the screen got bent during shipment.

MIUI… don’t even get me fucking started on this garbage. It literally removes numerous features from vanilla android, presumably to relocate some performance budget to the bloat they add.

Beyerdynamic or Jabra are also quite good, depending on your budget. Cheap Sennheisers might have overly strong bass and bad breathability.

premature optimization is a root of all evil.

also when those morons decide to do ‘microservices’ but end up creating glorified SOA with one messy DB where half the tables are not even used by anything, updates in place are the standard and there is nothing like one team per service, but instead everyone is expected to navigate millions of lines of spaghetti code with poor documentation, barely any reuse and inconsistencies all across the board with this oh too-fucking-common entity service anti-pattern.

and so much fucking coupling that you better start deploying your dev cluster just right after waking up so it maybe is up and running by the time your daily is over.

Fun fact, I used to work at a company where a lot of projects use Elixir and a bulk share of my coworkers have been outspoken critics of microservices precisely because OTP manages to power fault tolerant and scalable systems but not by insane levels of complexity like kubernetes does but by CoC that rarely gets in your way.

yeah sysctl > regedit

'tis a meme… ;)

the real question is whether you use git variants. Which is another way of not making arch (and Gentoo) certainly not free as in free beer, especially if you live in Europe and need to deal with those outrageous energy prices. btw imo one should be suspicious of projects with long tagged release cadence since it’s usually a sign of technical debt and the need to look for alternatives.

The X server has to be the biggest program I’ve ever seen that doesn’t do anything for you.
Ken Thompson

I see Wayland’s flaws but X is such a bloated piece of hardly maintainable spaghetti code that it is sadly beyond saving or prospects for anything in terms of significant improvement

well in this particular case it’s initramfs’ fault for not designing for all-or-nothing atomicity (a operation either completes fully or not at all). which you can work around with a terminal multiplexer where a session can be re-attached later in such cases btw.

well in my experience it was opensuse tumbleweed or Manjaro that were significantly less stable, but perhaps my perception is a little bit skewed since I use artix and it’s certainly not too rarely just the bloated, tightly coupled nature of shitstemd that causes some of arch’s issues.

a decentralized file hosting/sharing protocol that powers library genesis, for example

come and destroy the IPFS, then!

not enough AI features! /s

one of the best

(link in alt text)

And then for no good reason a “FOSS” app’s binary grows by a couple MB…

>no GUIX, Parabola or Gentoo on a DRMed SaaSS platform
fitting

simple is often the opposite of easy

Good that you’ve enjoyed it. But a fundamentally wrong thing about systemd is that it is actively harming the best thing about Linux – freedom. Some programs won’t work on a non-systemd distro because how tightly coupled and vendor non-agnostic anything that becomes dependent on might become at times. Of course it’s not as bad as glib(loat)c, but still if something can be done without any degradation of functionality via standard POSIX facilities, WHY either incur additional maintenance overhead for non-systemd implementations or punish people for their computing choices if there’s no one to maintain it?

systemd is more like, uhh, ignition that takes care of way too many things beyond starting the engine

*devuan, artix or alpine

I’d like to interject