UnityDevice @ UnityDevice @startrek.website

Posts

0

Comments

141

Joined

2 yr. ago

If this was done by multiple people, I'm sure the person that designed this delivery mechanism is really annoyed with the person that made the sloppy payload, since that made it all get detected right away.

Because Bedrock runs on phones, tablets, consoles, and a host of other random crap

And it also removes Linux support. Typical Microsoft.

Then they'll just identify you by the sound of the printer being audible from down the street.

Seems to me that a lot of the world's problems start with "well, the managers think..." They all seem extremely bad at the whole managing thing, good thing we don't overpay them or anything like that.

TIL there are Linux people that don't use OpenWRT. I always assumed everyone in the Linux community used it. It's great.

Works great with mt7621 based routers if anyone ends up looking for something compatible.

Linux and a windows virtual machine with a dedicated nvme hard drive and GPU using PCI pass-through. Windows is boxed in but easily accessed when you need it, and the performance is 95% of native, or more. And because of the dedicated hard drive, you can still dual-boot it like normal if you want.

Also, I recommend installing windows 10 enterprise in the VM, minimal bloat.

I believe they're called "logicool" in Japan. So maybe it's some form of logo consolidation.

I use gnome for the most part. I have been checking out kde recently to see how the newer versions stack up (gave up on it during the 4.0 days). As you mention kde supports dpms changes on wayland because they have their own protocol extension for that.

That's actually my biggest gripe with wayland - the huge amount of fragmentation it has caused. I'm pretty confident that almost all the missing features I talked about are possible on one or two of the compositors, but not all of them. And definitely not on the one I use. I'm sure once some pragmatism takes hold that all the issues will be ironed out, but my plan for now is to stick to X11 until that happens.

For me it's a million little details that just don't work. Stuff like positioning windows, removing decorations from a window, remapping buttons on a trackball, setting a graphics output to tvrgb, disabling a display via ssh and enabling it again, etc.

It's not just about hardware compatibility. It has to be compatible with existing workflows, and it's currently very limiting.

set -euo pipefail at the top of every script makes stuff a lot safer. Explanation here.

It's an American obsession.

It's like calling all fuel diesel.

But now you're stuck in the woods with a libertarian. You're worse off than before.

You tend to lose count after the first few hundred.

Or libcinder. Or even simply Arduino.

Eyes dont have lens flare

Me, with astigmatism: I'm gonna have to disagree on that one.

Dave Jones of the EEVblog always says to beginners "I hope your project doesn't work." He thinks it's a much better learning opportunity that way.

They're doing this at the OS level, so Firefox can't protect you from that, the issue is with Windows. They could do the same to Firefox, they just don't bother.

Not sure what you mean, they've always used Snapdragons? The S23 from 2023 uses one, and the S3 from 2012 uses them in some models, and most galaxies between those do as well.