How was it an obvious data breach? The attack was done via Codebergs notification system. It's no different from the notification you got from me writing this comment.

In this case it's more of a switch away from the last cool new thing. Totem (like Music) was built around a media library navigated from within the app. By default Totem doesn't even support opening videos from the file manager, which is something you would probably expect of a video player. It also crashed for me when I tried using it as intended so I'm not surprised to see it replaced by an app that really is just a video player.

That said many apps get replaced not for feature reasons but just by being GTK3, and they tend to get replaced by their own forks to GTK4 (such as the upcoming replacement of Evince). Why their devs choose to upgrade toolkits this way I cannot say.

Insightful article. I have to confess I never realized the accessibility situation was this bad.

I also want to highlight this excerpt from the comments:

Making things accessible isn't hard technically. But it requires coordination and people to care about it enough to work on it at the expense of other features. If [I] developed an application on a team and said I had 'one security guy that works on that stuff as long as it doesn't interfere with the rest of our work' I'd be dragged over the coals and have my project forked by the public.

But with accessibility? There's really no sense of priority or urgency despite it being broken for years and not putting much effort in to fixing it.

It's prettier than a TTY and you can pick whether you want a Wayland or an X11 session without having to know the correct startup commands. You can pick between different desktops too. And a Display Manager can offer on-screen keyboard and touchscreen support while a TTY can't (at least GDM does, I'm not sure about SDDM off the top of my head).

Aside from that whatever command you are using in the TTY to launch Plasma might or might not be the same commands SDDM uses, which might or might not lead to issues in setting up the environment. If your environment is fine and you don't care about having to use a physical keyboard then of course you can remove it. It's not exactly load bearing.

Try launching Steam from the terminal so you have a chance at seeing an actual error message, at least for the crashing games.

It might be the kernel as the other comment says since the 9070 is pretty new. If it works without issues on something like Fedora or OpenSUSE TW then that was probably the issue.

I am very sorry to remind everyone about the existence of Visual Basic, but it has:

• VbCrLf
• VbNewLine
• ControlChars.CrLf
• ControlChars.NewLine
• Environment.NewLine
• Chr(13) & Chr(10)

And I know what you're asking: Yes, of course all of them have subtly different behavior, and some of them only work in VB.NET and not in classic VB or VBA.

The only thing you can rely on is that "\r\n" doesn't work.

GUIs do have advantages in things like discoverability. Honestly the 1983s Apple Lisa nailed this with the idea of having clickable menus annotated with keyboard shortcuts, so users could do the same thing faster next time. For some reason we stopped doing this (especially in web apps), but that's a reason to make better GUIs, not to RETVRN to the feature set of a VT100.

I don't know why we have to go on nonsensical diatribes about "UNIX wizards" though when we're fundamentally talking about a handful of minor UI improvements to things that already exist.

It depends a lot on which specific GPU you have and whether it's a laptop.

New-ish GPU in a desktop with the monitor plugged directly into the GPU? Easy to get working, literally a checkbox on most distros.

1000 series GPU or older in a laptop and you need reasonable battery life and/or some "advanced" features like DP Alt-Mode? Good luck.

Edit: Also, no Wayland until very recently. Possibly never, depending on the age of the GPU.

I'm not sure why nix-env is so slow exactly but it's the wrong tool to use anyways as it just throws away everything NixOS has going for itself in favour of pretending to be a normal package manager. You really just want to use the configuration file.

The "normal" way to install packages in NixOS would be using environment.systemPackages. The various programs.<name> options are intended for packages requiring additional setup, like shells or desktop environments (e.g. iirc for sway it creates a systemd target and adds the .desktop files for login managers to see it). Weston has a package but not an option, so you'd have to figure that additional stuff out yourself (but running Weston from a tty should just work).

There are additional ways to install packages for single users or using home-manager but you don't need those.

This does kinda demonstrate why (I personally think) NixOS is so hard to learn: There's a million different ways to do anything and each has it's own weird gotchas. And critically most of them, even when they are honestly just legacy cruft, are not actually deprecated and may even have users advocating their use, or even if they don't nobody bothered to remove that part from the wiki (if it was ever there to begin with).

You can also see this in the flake/channel split: One person in this very thread is telling you to use flakes, while another is telling you to stick with the default (channels).

And in some (fortunately relatively rare) cases even things that everyone agrees are bad ideas still get promoted in official documentation or other prominent places, like using nix-env -i under any circumstances, ever.

And it is definitely a learning problem you are having. You are facing the same problems as a new Linux user who just installed Manjaro with KDE 6 on Wayland and is wondering why apt-get and xrandr are not working even though those are accepted answers on Stackoverflow posts from 2012. Of course as experienced Linux users we know why, but a new one has to learn a lot of stuff before "getting it" and will probably stumble onto poor advice more than once in their journey. (And learning Nix is arguably worse than learning Linux for the first time, but that depends a bit on your exact experience and background.)

If you stick to learning NixOS there will be a point when these things seem trivial, but it will be a lot of effort to get there. Is that effort worth it? Well, if the term "declarative package management" doesn't mean anything to you, maybe not. You do sacrifice a lot of things "just" to declare your entire system state in one configuration file (or more likely, directory). But I do think the things Nix does are really cool, if you can get over the, uh, everything.

The GDPR conversation is hilarious. Sure they're a US based company, but after 5 years of operation I would've expected them to have consulted a lawyer about this at some point. Forgetting (assuming it's not "forgetting") about the required documentation is not the worst thing in the world morally but it doesn't exactly make them look competent either.

To be fair this also happened to Eagle Dynamics, developer of DCS, the other "realistic" flight sim that players take far too seriously. Except there it was a Dev that got arrested in Georgia and extradited to the US...

While unfortunate, not shipping these standard Google apps is not really an option for any Android manufacturer due to Google requirements. Including them is required if you want to use anything from the GSM, which includes things like the Play Store and everything it touches. You can technically ship a different Android distribution like Lineage or /e/, but that's not really what most people will be expecting of an "Android" phone and will narrow the viable target demographic even more than the value proposition already does.