For something that only uses your home folder, I recommend checking out mise https://mise.jdx.dev/
1,664 karma · joined March 30, 2019
Socials: - github.com/pzmarzly
---
For something that only uses your home folder, I recommend checking out mise https://mise.jdx.dev/
BTW how much of it is vibe coded?
- when ls started quoting filenames with spaces (add -N)
- when perl stopped being installed by default in CentOS and AlmaLinux (had to add dnf install -y perl)
- when egrep alias disappeared (use grep -E)
At least nowadays LLMs can rewrite Bash to JS/Python/Ruby pretty quickly.
Regarding phones, Google is trying to push UEFI adoption with their EFI bootloader, but that's still some time away. Recent talk: https://lpc.events/event/19/contributions/2257/
Regarding Windows/PC ARM devices, I think the best experience would be on System76 Thelio (with Ampere CPU), but that's quite a pricy machine.
I don't really care what Apple does on this regard, they were always doing things differently. IIRC, even Macs that supported EFI, only supported EFI 1.1, not 2.0, no?
There are standards for ARM, and they are called UEFI, ACPI, and SMBIOS. ARM the company is now pushing hard for their adoption in non-embedded aarch64 world - see ARM SBBR, SBSA, and PC-BSA specs.
I heard the state of the wiring also wasn't great, sometimes apartments had twisted pair wires, while some straight wires, some only have 2 or 3 out of 4 wires connected, etc.
Good to know this technology still exists.
The gap with Podman is closing though, and most users don't need any of these in the first place.
In the meantime I'll give Orion a try as soon as they introduce cross-device sync.
DOOM and Battlefield 6 are praised for being surprisingly well optimized for the graphics they offer, and some people bought these games for that reason alone. But I guess in the good old days good optimization would be the norm, not the exception.
I try to install all software via homebrew, mise (https://mise.jdx.dev/), and scoop (https://scoop.sh/), and setting up a new machine now takes me minutes. Meanwhile I don't need to deal with Nix language.
Seems like there are VPNs, and then there are VPNs.
As long as it doesn't mean 10x worse performance, that's a good selling point.
Unless your servers and clients push at different time, thus are compiled with different versions of your specs, then many safety bets are off.
There are ways to be mostly safe (never reuse IDs, use unknown-field-friendly copying methods, etc.), but distributed systems are distributed systems, and protobuf isn't a silver bullet that can solve all problems on author's list.
On the upside, it seems like protobuf3 fixed a lot of stuff I used to hate about protobuf2. Issues like:
> if the field is not a message, it has two states:
> - ...
> - the field is set to the default (zero) value. It will not be serialized to the wire. In fact, you cannot determine whether the default (zero) value was set or parsed from the wire or not provided at all
are now gone if you stick to using protobuf3 + `message` keyword. That's really cool.
But if you're in the same boat, at least use something that has an adblocker, like Brave, Vivaldi or Opera.
Thankfully modern BIOSes tend to implement HTTP boot option, where you can point to any HTTP or HTTPS URL (as long as the URL ends with ".efi", which is a pretty dumb limitation if you ask me).
If not, then I still need to have a custom app/browser extension... at which point why would I pay for subscription anyway?
https://github.com/rhinstaller/anaconda-webui
I wish RedHat made an easy-to-use framework out of it.