Do you get upset everytime you see it?

What does it do on new hardware? Not a lot of people are running normal desktop Linux on phones / tablets, are they? Which, totally cool if it works better on those things… but I guess I’m just surprised by how much hype there is for Wayland when X just works for me and would presumably just work for most people’s use cases. Like… who are all of these people that are emotionally invested in display servers, and what am I missing?

I mean, 20 years ago or whatever there was always the pain of black screens and X configs… but it just kind of works now in my experience?

What’s so much better about Wayland than X? I mean, I’m not really a fan of X and the security nightmare that it is, but as a user it’s all pretty plug and play these days. What does a normal user get out of Wayland? Would they even know they’re using it?

I’d love to try it, but it currently won’t work with some software I use, so I haven’t bothered… And honestly I’m kind of confused about how everybody is talking about how amazing Wayland is (and how it seems to suddenly be the one true path for a bunch of distros) when my only experience with Wayland is people talking about how great it is and then not being able to screenshare or whatever… Which doesn’t make it seem great from the outside? That maybe sounds a bit flippant, but I genuinely don’t understand why “normal” people are so excited? I mean, I can see people caring about features like HDR and maybe that’s easier to build into Wayland than ancient X11, but I’d be more excited about the specific feature than Wayland itself which may make implementing these things easier?

Huh. I’ve used chirp under Linux before and I just installed it with my package manager. Maybe it wasn’t available on your distro? Then it can get a lot more tricky. The other problem with these things can be permissions… once you have chirp installed maybe you need to add your user to the dial out group in order to be able to use the serial port to flash the radios.

There’s operations that treat bits like floats and operations that treat them like various kinds of ints, but the meaning of bits is in the eye of the beholder. There’s even good examples of mixing and matching integer and floating point operations to clever effect, like with the infamous fast inverse square root. I feel like people often think mathematical objects mean something beyond what they are, when often math is kind of just math and it is what it is (if that makes sense… it’s kind of like anthropomorphizing mathematical objects and viewing them through a specific lens, as opposed to just seeing them as the set of axioms that they are). That’s kind of how I feel with this stuff. You can treat the bits however you want and it’s not like integer operations and bitwise operations have no meaning on supposedly floating point values, they do something (and mixing these different types of operations can even do useful things!), it just might not be the normal arithmetic operations you expect when you interpret the number as a float (and enjoy your accidental NaNs or whatever :P).

The difference of static and dynamic typing being when you perform the type checking is partially why I consider it to be a somewhat arbitrary distinction for a language (obviously decidable static type checking is limited, though), and projects like typescript have shown that you can successfully bolt on a static type system onto a dynamic language to provide type checking on specific parts of a program just fine. But obviously this changes what you consider to be a valid program at compile time, though maybe not what you consider to be a valid program overall if you consider programs with dynamic type errors to be invalid too (which there’s certainly precedence for… C programs are arguably only real C programs when they’re well-defined, but detecting UB is undecidable).

I kind of feel like “untyped” is a term that doesn’t really have a proper definition right now. As far as I can tell when people say “untyped” they usually mean it as a synonym for whatever they consider “dynamically typed” to mean (which also seems to vary a bit from person to person, haha). Sometimes people say assembly is untyped exactly for this reason, but you could also consider it to have one type “bits” and all of the operations just do things on bits (although, arguably different sized registers have different types). Similarly, people sometimes consider “dynamically typed languages” to just be “unityped” (maybe monotyped is more easily distinguished from untyped, haha) languages at their core, and if you squint you can just think of the dynamic type checks as a kind of pattern matching on a giant sum type.

In some sense values always have types because you could always classify them into types externally, and you could even consider a value to be a member of multiple types (often programming languages with type systems don’t allow this and force unique types for every value). Because you could always classify values under a type it feels kind of weird to refer to languages as being “untyped”, but it’s also kind of weird to refer to a language as “typed” when there isn’t really any meaningful typing information and there’s no type system checking the “types” of values. Types sort of always exist, but also sort of only exist when you actually make the distinctions and have something that you call a “type system”… In some sense the distinction between static and dynamic typing is sort of an arbitrary implementation detail too (though, of course, it has impacts on the experience of programming, and the language design makes a bit of a difference in terms of what’s decidable :) (and obviously the type system can determine what programs you consider to be “valid”)… But you can absolutely have a mix of static type checking and dynamic typing, for instance… It’s all a little more wishy washy than people tend to think in my opinion).

Running Jellyfin off of a VPS provider seems needlessly expensive. I guess server hardware has an upfront cost, but having real hardware to host it on at home will be far more cost effective long term, especially for storage.

Yeah, that’s my main concern. I believe the Immich developers have said they have no desire to implement it, though… Which is fair enough, it doesn’t work for my desired use case though.

I want all data to be encrypted before it even reaches the server. Yes, I don’t want to trust even my own server for my image backups :), particularly since I would want to use something like Immich to provide photo backups for friends and family and I don’t even want to technically have access to their unencrypted photos unless they explicitly share them. I kind of want the attack surface for my photos to be as small as practical too. It’s almost certainly worse to have them available on my device unencrypted than a dedicated server, but it’s worse to have them unencrypted on both (and I want photos available on device so, thems the breaks).

I get that a lot of people won’t care about this and that they’d rather be able to run the image recognition features of Immich on the server and stuff, but I don’t think it’s entirely unreasonable to want encryption for this. If nothing else I’d love to be able to back up photos for friends and family and legitimately be able to tell them that it’s encrypted and I can’t see any of it. It’d be even sweeter if they could do image recognition on device and sync that metadata (encrypted) to the server as well.

I’m kind of disappointed by the lack of encryption. It sounds great, but I don’t want to trust the server.

What game were you comparing?

60 fps when you were getting 20 on windows…? Wat? Were shaders still compiling on Windows?

I think it’s flatpak?

For what it’s worth I also haven’t had any problems. Maybe we’re just lucky, though.

It depends what you’re comparing against, but I had plenty of games on Linux when steam released their Linux client. 10 years ago was the start of a huuuge shift. It died down a little bit after a few years (I think a lot of developers stopped caring when steam machines petered out and developers started to decide the Linux releases weren’t worth it), but then after a little while Proton started kicking off and the rest is history. Obviously you didn’t have nearly the selection of windows, but there was still selection.

It definitely wasn’t as good of a situation as it is now, but 10 years ago was actually pretty good for Linux gaming too. At that point Valve was already starting to support Linux and there were a bunch of native Linux releases for games at that time, including lots of indie titles in Humble Bundles and even a good chunk of AAA titles were getting Linux releases (e.g., Bioshock Infinite). If you had specific windows games you wanted to play you could very well have been out of luck, but there was actually a really solid number of native Linux ports at the time. I was personally pretty happy with it and just completely blew away my windows partition at that point. Of course you didn’t have access to the full catalog so to speak, but honestly you probably had access to more titles than on many consoles at the time, which arguably made it a viable gaming platform at the time (I made do with it!) Naturally, like any platform, you may or may not be okay with the selection of games available so it really depends on the person, but I was a pretty happy camper.

Every digital system is also secretly analog.

Seems like it might be fine: https://nextcloud.com/blog/nextclouds-push-notifications-for-ios-and-android/

I’m pretty sure this is on a public mailing list.

Audio drivers have never really been a problem in my experience, but maybe you’re referring to pulseaudio? In which case, pipewire has been great!