apt_install_coffee

What you're after, transparent wifi roaming, is actually mostly handled by the client; what you need is wifi access points that don't get in the way.

I don't have much experience with new OpenWRT supporting products, but the kicker is you only need one of them. If you have multiple routers, they will require some setup to play nice with each other. An "Access point" is just the wifi provider, can be hooked up to provide whatever the one router manages, and are generally cheaper than a router.

To that end, I'd suggest a single router, and multiple access points. I do this with Ubiquiti access points in my home, their PoE has been nice and they have been pretty "setup once and forget" for a few years now. I'm sure there are some other brands that'll do well; Ruckus and Mikrotik come to mind.

1. Get kicked from freedesktop for fostering a toxic community.
2. Ditch wlroots for your own compositor.
3. Shit on other compositors in your spare time.
4. Tell people they should just be plugging into Hyprland instead of rolling their own compositor.

Man if I was concerned about sinking the time to make a configuration for the compositor with a bus factor of 1 man-child, and a toxic community; I can't imagine anybody investing the time to make a compositor is going to want to hitch themselves to that cart.

The compositor is really solid and makes for a great user experience but I'll be fucked if every word vaxry writes doesn't make me want to move to sway or niri.

Nixpkgs has more and newer packages than the aur.

The initial time to get shit done is longer; you can't simply make install, but honestly you shouldn't have been doing so on arch anyway.

Making your own derivation is much easier than making your own PKGBUILD and should be considered in those terms because you're not just shoving some binary into /usr/bin for it to explode later when glibc updates.

When things fuck up, reverting to your previous config is at worst a reboot away.

I have much less time than I used to, so moving from arch to Nixos has prevented the time otherwise wasted in an arch-chroot trying to fix issues like the kernel upgrading past what the zfs-dkms supports.

If you're using specialised proprietary tools, working them in with Nix can be an absolute nightmare, but I use a debian container for them.

While I think the cynicism is well-earned, we should pay attention to when we're proven wrong and highlight when companies do something right. Bitwarden's fuck-up gave them an opportunity to signal that they're not intending to build a wall for their garden, and they took it.

It's unlikely; convincing people to buy two of your GPUs instead of one of your competitors has always been a hard sell, even when Radeon and NVIDIA we're kneck and kneck market share wise.

Combine that with the fact that crossfire is not a solved problem, whether you do it spacially, temporally, or you offload Async tasks to the second GPU you always run into the NUMA problem (shove all that data down the PCIE bus fast enough to stitch together well within 1 frame is a tall order) and the results is terrible tearing and super niche bugs so it's just not worth the cost of support.

Developer support could help, but why would they? A lot more work for <1% of their player base?

Moving some packages (especially libraries) onto an unstable branch while keeping others back on a stable one. It probably won't fuck you immediately, but when it does it'll be a bastard to diagnose because you will have forgotten what you did.

It is important to note that Arm has the full support of Microsoft, which is crucial for Arm’s success in PCs

Not saying windows compatibility isn't extremely important, but based on Windows on Arm's track record, collaboration with Microsoft on this project specifically seems like more of a millstone than a windfall.

It really depends on what you're most comfortable with; when you go for such a custom option most of the design decisions are about personal preferences.

I suggest you draw out some layouts on a piece of paper, adjust them until you feel happy and then plan out how you want the keymap to look. When you're happy, look for a layout that fits what you want or build your own on KiCAD.

I bought a kyria from Splitkb, and I've been very happy with the design. If I needed another keyboard, it would probably be a very similar layout, but have slightly fewer keys, be low-profile and no oleds.

maybe they're going for induced apathy; if it's close you're motivated, but if it's not at all close maybe that'll just make you depressed.

Or maybe they just really believe in the orange fascist, and have enough money to burn for betting on him.

It's also possible the market isn't as distorted as they think; it's not easy to quantify how much one individual bet has affected others' decisions.

I use PiHole+Unbound in a podman quadlet, and give it its own macvlan. Works great for me.

My parents treated my device access something they had to keep a keen eye on. They were good at manually making sure I wasn't sitting around having my brain rot, but their spying on what I was doing into my teens left me with some trust issues.

They briefly tried to use technological solutions to control my access and monitor me, but all that served was to make me very good at circumventing them. Outsourcing parenting to a computer program doesn't work, and kids notice when you try.

They're not trivializing, just noting that the different things you need to discuss for kernel development compared with other work. It is very different in a lot of ways, and does shape your perspective. I also find it interesting.