24
Equipment costs might (probably?) be amortised over time, but still requires upfront expenditure.
Unless it’s a load of gloves. I always lose gloves.
RecallMadness
joined 2 years ago
I last tried KDE when it was KDE3. Then Gnome, xfce, and finally settling on i3/sway
But I got given an old Windows tablet so decided I’d see what is usable as a tablet and I was pleasantly surprised by KDE.
So much so, I’ve ostree-rebased all my machines to it.
The tiling could be better (and it sounds like it was, then wasn’t?), but it’s passable. And simple stuff actually seems to work. Unlike the gnome+sway kludge I have now.
Hoagie and a Stogie
when the US goes right, NZ goes left
The NZ election was unfortunately a year too early.
Usually NZ has less restrictive visa requirements, and is often called “Australia’s back door” due to Au/Nz free travel agreements.
Even when I’m coating them in cheese and grilling them. Still gonna use the cheese ones.
Nobody says no to double cheese.
We had the WiiU which had an entire screen in the controller.
Fallout4 had the “pip boy” phone app.
The independent city state of Galway.
oh that looks like hard work. You’re going to need to hydrate, let me go get you both some electrolytes.
5 minutes at 30% in an inverter microwave.
view more: next ›
In my experience, it’s a manageable trade off.
You allow for Python “magic” at the cost of type safety. Or you forgo magic for types, and the resiliency that comes with it.
Day to day, you don’t need magic. With good application of hinting you can stop many bugs before they appear.
When you do need magic, you can usually construct it to work within the type system, or at the very least easily ringfence the tainted typeless code the magic introduced.
The sync/async contradiction is much worse to wrangle.