LinuxSBC @ LinuxSBC @lemm.ee

Posts

3

Comments

201

Joined

2 yr. ago

Yeah, MacOS wasn't originally intended for x86 CPUs.

He's pretty much the quintessential QA tester. He wants to do things his way, regardless of whether or not the OS wants him to do that. He's usually skilled enough to fix anything he messes up, but he doesn't know enough about Linux to do that, so he ends up breaking things. I feel like most people have a better experience than he did, but his technique uncovered a ton of bugs and usability issues that significantly improved the Linux desktop to have fixed.

Tiling addons. I like having a full DE, but I also want tiling, so Pop!_Shell on GNOME and Polonium on KDE are invaluable (and yes, COSMIC looks really promising).

Yeah, but at least they've proven to be worthy of trust (contribute a lot to FOSS, offer ways to host your own iMessage server, warn about the insecurity). Sunbird has done the opposite.

/g

If it becomes an open-source, decentralized service with bridges and more users than Matrix, I'd consider it.

Beeper is pretty good with it, as they make it clear that it's insecure and use an encrypted protocol to get the messages to the server. Still, it's better to host your own (which Beeper lets you do, as it's just Matrix) or not use it.

No, it's even less secure than expected. We expected that Sunbird would have access to your Apple ID and messages. Instead, everyone in the world has access to your Apple ID and messages.

It seems that Starship, the second stage, experienced RUD from the automated FTS at around the time it was expected to shut off its engines.

Edit: RUD is Rapid Unscheduled Disassembly. Basically an explosion. FTS is Flight Termination System, which explodes a rocket if something goes wrong in a potentially dangerous way.

Thanks, though your correction is also incorrect. Display managers, like SDDM, GDM, or LightDM, are the login screen. They're called "display managers" for historical reasons, but they also run on top of the display server.

Display servers, not window managers. Window managers are built on top of X11 or Wayland.

Wayland is a "display server," which basically means it manages the way GUIs show on the screen. X (most recently X11/Xorg) was the standard for over 30 years, but it was designed for computers 30 years ago. Modern concepts like scaling and high refresh rate displays need extensions to it, but it's really complicated and hard to work with, so a lot of improvements that need to be made can't be made. It's also fundamentally insecure, as every window has access to both the contents and the input of any other window. Wayland is a modern replacement that focuses on security and expandability, and basically everything is working on switching to it. There are growing pains, but it's constantly improving, and most distros use it by default now.

Great answer. People frequently think that Android phones work just like desktops, but they are very different.

Have you installed a custom ROM on it? If not, you definitely don't have the skills for this. If so, have you built your own ROM for it? If not, do that so you learn how it works in a predictable environment. Then port something existing to it, like UBPorts. Only after you do all of that and probably a lot more should you attempt to effectively develop your own distro on hostile hardware.

VanillaOS and BlendOS also use containers to install apps, just like Fedora Silverblue. In fact, it's easier to install native packages on Silverblue than it is on VanillaOS. Just set your terminal to start a container by default.

Chrome OS makes installing Linux applications way more difficult than it is on most other Linux distros.

Chrome OS makes installing Linux applications way more difficult than it is on most other Linux distros.

I've been using Linux for ten years, and I've never done that. It's not really a part of the Linux experience anymore.

I do not like it, Sam I Am.