Well, technically, it’s not broken, just slower

I’d pirate it but I find the story just not interesting or worth my time.

I read Philosopher’s Stone about 25 years ago as a teenager and wasn’t impressed. Didn’t read any other because that one already felt like wasted time. Went to a movie in 2007 (no clue which one that was) and again forgettable. Not bad, in fact I still remember Die Hard 4 that I also watched back then because it was so bad. That HP movie? No idea about plot or anything. Another one? Thanks, I’m good.

Even if Rowling wasn’t a disgusting person, I feel like what I’ve seen of her work is just not great. It’s not terrible, but I don’t care for it at all.

But also, she can get fucked.

It’s a choice I can live without, I see the appeal of !! but usually, history is informative only, if I want something reusable, I write a function.

Ah, okay.

It shows that I’m not using POSIX shells

Yeah, I wasn’t sure there, the question mark was supposed to apply to all shells…

These additions are about user familiarity, not inter-shell compatibility is my point. Fish and bash are fundamentally incompatible. Just because they share keywords doesn’t mean they’re compatible. You wouldn’t say Rust got Python compatible just because it introduced a keyword or a concept from it.

Yeah, fish is a very comfortable shell in all regards. The standard installation does basically about 90% of what you typically want, probably more. Just very sensible in all aspects

No, but I feel bad when I need to deploy a big package for a bit of scripting.

For example, nushell is about 160 MB installed… which I find a bit much. It’s fine on my desktop, but I also have machines where this would be a significant addition.

I’m not the biggest fan of bash either, there’s a reason I use fish, though I also like elvish for interactive use (though it’s rather young all things considered) and in maybe going to use YSH for my next script project as that shell is very small (2MB or so) and yet makes sense.

Fish is really a pleasant shell, nothing groundbreaking but it’s just nice.

That said, I wouldn’t speak of “bash compatibility” just because another symbol/ operator from bash can now be used in fish (this happens sometimes), but this isn’t for compatibility but rather so that you don’t need to learn the fish equivalent. Fish has a different syntax from bash (e.g. command substitution doesn’t use $, no do in for loops…) so they’ll never be compatible. There are bash compatible shells out there (I guess zsh, dash and probably oil?), but fish isn’t and doesn’t try to be.

There’s always TempleOS.

NixOS is very tightly coupled to systemd, though there are efforts to change that

NixOS went from not being visible to… beating Manjaro!

Whatever that’s supposed to tell

👉👈

nix

Today is 11827 September 1993

https://kilyig.github.io/eternal-september-calendar/

Well I sit kind of between these

Like I’m not getting a dedicated router and have no server room in my apartment, and my consumer router only supports two VLANs (main and guest). But I’d say the rest is rather sophisticated with all machines defined in my NixOS config, including automated generation of firewall and reverse proxy rules for which I wrote custom modules.

Media server isn’t super full but connected to jellyseer and the rest of the stack, accessible over TLS (Let’s Encrypt certificates) only, with the option to have users managed via IDM.

However, I only have devices on my network that I somewhat trust, with an Android TV box being the worst offender. The smart TV was never connected to my network.

Would be cool to isolate my work PCs somewhat (I work from home with company provided equipment) but it’s just not worth the trouble in my opinion. Not switching out a low power device that does most for two different devices that both use more power (since you usually need a router and a modem).

I don’t only run a reverse proxy because of having only a single public IPv4 address, but that probably is the best part

In general, I’d say reverse proxies make things somewhat easier to manage, especially when it comes to TLS. No need for every service to integrate it.

That would have been a brilliant move with wav vs MP3

How would a new format be backwards-compatible? At least JPEG-XL can losslessly compress standard jpg for a bit of space savings, and servers can choose to deliver the decompressed jpg to clients that don’t support JPEG-XL.

Also from Wikipedia:

Computationally efficient encoding and decoding without requiring specialized hardware: JPEG XL is about as fast to encode and decode as old JPEG using libjpeg-turbo

Being a JPEG superset, JXL provides efficient lossless recompression options for images in the traditional/legacy JPEG format that can represent JPEG data in a more space-efficient way (~20% size reduction due to the better entropy coder) and can easily be reversed, e.g. on the fly. Wrapped inside a JPEG XL file/stream, it can be combined with additional elements, e.g. an alpha channel.