barsoap
joined 1 year ago
Presumably when we're talking off-site backups we're talking about a separate company sitting somewhere in an abandoned nuclear bunker which can justify the price of a tape drive or twenty.
Isn't that what tapes are for.
Should all be in place. Even nvidia driver support. It's one of the rare cases where I actually support nvidia on a technical level, that is, having explicit sync is good. I can also understand that they didn't feel like implementing proper implicit sync (hence all the tearing etc) when it's a technically inferior solution.
OTOH, they shouldn't have bloody waited until now to get this through. Had they not ignored wayland for a literal decade this all could've been resolved before it became an issue for end-users.
Oh that's easy (and probably disappointing): None. Not really a hobby of mine, more of an extension to doing the laundry and being a cheapskate who can't fathom buying something new when you can fix it in the time it takes to listen to a podcast episode.
The other really valid reason is linen. Kinda unrelated to sewing itself and it's not about stopping the stuff from crinkling (that's right-out impossible), but to make sure that crinkles don't always appear in the same place so the fabric has a chance of wearing down evenly.
Found this out the hard way because my linen duvet covers are oversized -- nominal size is correct, but they're made for down blankets, not flat ones. Blanket slides inside, generally towards the bottom, leaving a fabric flap on the top that really tends to crinkle as you sleep, wash, hang up, the crinkles don't straighten out, exact same crinkles appear in the exact same spot and get chafed while sleeping, rinse and repeat for two years the first hole starts appearing, a month later there's more than you can be bothered to patch.
Luckily it was a simple matter of running a stitch down the length of the thing to shorten it a bit, but given that an iron and ironing mat (not a full table, mat is completely sufficient) is significantly cheaper than linen covers or just the material for them, definitely worth the investment and time.
Oh and yes linen covers are definitely worth it because moisture regulation. It's also nice and soft -- not in the silky smooth sense, it has definitive grip to it. So are linen kitchen towels because they actually dry stuff instead of spreading water around. Half-linen is already a massive upgrade over cotton in that area and it's much cheaper (the main reason why full linen is so expensive is because it's a bugger to weave, not because the yarn is that much more expensive. Weaving linen wefts into cotton warps OTOH is pretty uncomplicated).
Programs can't set position or size of windows, period, at most they can ask and then hope they don't get ignored and it's good that way. Window management is responsibility of the compositor, not of applications.
At least KDE has support for it that's about on X11 level, a proper-proper solution is still in the pipeline. And yes you're seeing right it's been there for four years.
And nobody wants to rewrite Xorg or understand the code (other than very basic security maintenance).
That's precisely the point: All the devs got tired of it and started wayland instead.
X12 might happen at some point when wayland is mature, as in a "let's create and bless a network-transparent protocol so we might have a chance of getting rid of XWayland in 50 years" kind of move.
Yep that'd be Wayland devs maintaining XWayland, which is part of the x.org codebase. There are no "X11 devs", they're the ones who started Wayland to get rid of that bowl of spaghetti!
I argue that X11 would have hyperactive development, if we did not have Wayland
Wayland was started by the X developers because they were sick and tired of hysterical raisins. Noone else volunteered to take over X, either, wayland devs are thus still stuck with maintaining XWayland themselves. I'm sure that at least a portion of the people shouting "but X just needs some work" at least had a look at the codebase, but then noped out of it -- and subsequently stopped whining about the switch to Wayland.
What's been a bit disappointing is DEs getting on the wayland train so late. A lot of the kinks could have been worked out way earlier if they had given their 2ct of feedback right from the start, instead of waiting 10 years to even start thinking about migrating.
Making screenshots does, too, which is why that functionality gets implemented at the compositor level. And so will screenreaders. In fact looking at my settings panel KDE does have support for Orca. Dunno how well it's working but it's not like the issue is being ignored.
That does not seem to be a stray and yes there's definitely reasons to take potshots at Gnome. They still don't support server-side decorations. Everyone is absolutely fine with them not wanting to use them in their own apps, have them draw window decorations themselves, and every other DE lets gnome apps do exactly that, but Gnome is steadfastly and pointlessly refusing to draw decorations for apps which don't want to draw their own decorations. It'd be like a hundred straight-forward lines of code for them.
And that's just the tip of the iceberg when it comes to breakage you have to expect when running Gnome.
view more: next ›