The point of a terminal like this isn’t necessarily to have more features. I have the tabs turned off (I also just use tmux). The point is to render smoothly and look/feel nice.

Some people would rather spend a lot of money on a nice pen. It still is just a pen that writes. No additional features over a 25 cent Bic pen. But the smoothness of the writing, the hand feel, consistency of line thickness, etc… to some people that matters. No extra features, it just looks and feels a bit better… But if all you are doing is writing a grocery list, you may not care. And if you don’t care, you aren’t wrong. This just doesn’t apply to you. If you don’t have a reason, you don’t need to find one. It’s just not applicable.

But some people do care. They do have a reason. And they are also not wrong to care. Their reasons just may not apply to you because you have different workloads or priorities (or maybe they do, and you just haven’t realized that it’s a thing you care about)

I think this just happens to fall under the category of “some people care about milliseconds of rendering time, and some people don’t.” I don’t know if the GPU acceleration has anything to do with it, but this terminal emulator also has really good font rendering.

If you are happy with your current terminal emulator, continue using it. If you heavily use your terminal emulator for a lot of things and in some things you’ve found that it stutters a bit, and you wished it was a bit smoother, get a GPU accelerated terminal emulator.

And secret bonus option: Even if you are happy with your current terminal emulator, give it a try anyway. Ghostty has a “zero configuration” policy where their goal is for most people to never need to configure anything. Sane defaults. It’s a good out of the box experience. Give it a few test drives, and if you’re still perplexed about why you should care, then maybe it’s just not for you and you can switch back. If you go “that was pretty smooth, i dont have a reason to switch back” then maybe you’ll think about it differently.

I was using alacritty. Ghostty feels snappy like you said. I dont know if it’s “noticeably” faster in any meaningful way. but the out of the box config settings make the font rendering look much nicer than I had set up for alacritty.

I told myself “I’ll use this for a while” as well but then realized… I don’t actually have a reason to change to anything else. It gets the job done. So until some other new shiny thing comes along, this is probably where I stay for a while.

Some games can detect if they are running a VM and block that as part of their anticheat. You may not be able to get roblox or fortnite running in a windows VM.

Some games just flat out require actual Windows, so your options are “Have an actual Windows drive/partition” or “Just don’t play those games”

I would never buy Jade. I always buy snsv laptops

The cofounder of sticker mule went real hard on trump support this past year so I’ve just done without stickers.

Which version of of SDDM (and presumably KDE) are you using?

One of the comments one of those threads you linked points out that the bugs you’re sharing are for has changed.

The components have been reworked since the button was disabled so maybe that helped. It used to be a PlasmaComponents2.TextField, now it’s a PlasmaExtras.PasswordField.

PlasmaExtras.PasswordField has the button enabled! However, the implementation in the theme explicitly disables it.

If you open up /usr/share/sddm/themes/breeze/Login.qml and scroll down to line 106. You’ll see rightActions: [] – this bit of code basically overrides the default behavior. It says "normally you have some actions here, but instead use this list, but [] is an empty list.

So if you just comment that line out by adding // to the front of it… Everything should just work, since it will then revert back to using the built in value.

However, the reason this was removed in the first place is in a comment on line 105: // Disable reveal password action because SDDM does not have the breeze icon set loaded

If the icon set fails to load for whatever reason (if youre using a custom icon theme or something, i dunno why it might not be loaded), the button will fail to load again.

You can test drive the SDDM lockscreen by running sddm-greeter-qt6 --test-mode --theme /usr/share/sddm/themes/breeze/ from the terminal.

And this all assumes that you’re using the default breeze theme. If you are trying to use a different theme, not sure if any of this applies.

Because otherwise if you have too many small letters in a row it stops looking like a plural and more like a misspelled word. Because capitalization differences you can make more sense of As but not so much as.

The archinstall script has a list of “profiles” that you can select from (custom, desktop, minimal, server, tailored, xorg)… And if you select “desktop” it will prompt you which DE or WM you want to install. (awesome, bspwm, budgie, cinnamon, cosmic, cutiefish, deepin, enlightment, gnome, hyprland, i3, lxqt, mate, plasma, qtile, sway, xfce4).

By the time you’re done with the archinstall script, you basically have a fully functioning arch (ive never used the script seriously, so I have no idea what all remains not set up doing this).

The main difference between Arch and Ubuntu in this regard, is that if you want to run KDE Plasma, you download the common Arch ISO, and select Plasma at installation time. Compared to Ubuntu where you would download the “Kubuntu” spin, so you are selecting Plasma when you acquire the ISO in the first place.

There is no “default” arch DE, so when you install Arch, there is a lot of decisions to make (and you may not know how to make those decisions if its your first distro), whereas Ubuntu makes a lot of decisions for you, so you have to answer no questions to get set up (but you may be set up in a way you weren’t expecting). In this regard, Arch really does just feel like building a PC from parts, you just have to pick all the parts. Ubuntu is more like buying a pre-built.

https://theoatmeal.com/comics/design_hell

You’re not wrong, but a lot of time those webpages aren’t overengineered because the developer wanted it to be, but because the client kept making more and more demands.

If we assume “half a day” is 4 hours, and 500 pounds. That’s 125 pounds per hour. Which isn’t the worst rate. Assuming it’s actually capped at 4 hours and we all know that if it’s your dad’s friend, this is not going to be a set and forget kind of thing. So that 4 hours quickly becomes 10. And suddenly you’re down to 50 pounds per hour. And then if it’s actually static and simple and good, you still have high odds of getting insane feedback demanding changes to make it worse. A motherfucking website would actually be the best option, but wouldn’t get you paid. At that point youre just doing it for the lols.

But ultimately, this isn’t even about the rate or how much time this will take. this whole scenario depends heavily on the son here. Is the son unemployed and living in dad’s basement for free? Then yeah. Sorry, he should probably take any work he can get for any rate he can get. His dad gets a lot more say in how things work financially if the son is relying on him financially. But if the son is already working a full time job and living in his own house? Then no, I don’t care what the rate is. Don’t commandeer other people’s time. Don’t make deals that people haven’t agreed to. Come to me with opportunities, not demands.

Apparently it works retroactively and now you are on Windows.

That didn’t take long.

You’re right. There are multiple definitions of the word stable, and “unchanging” is a valid one of them.

It’s just that every where else I’ve seen it in computing, it refers to a build of something being not-crashy enough to actually ship. “Can’t be knocked over” sort of stability. And everyone I’ve ever talked to outside of Lemmy has assumed that was what “stable” meant to Debian. but it doesn’t. It just means “versions won’t change so you won’t have version compatibility issues, but you’ll also be left with several month to year old software that wasn’t even up to date when this version released, but at least you don’t have to think about the compatibility issues!”

Debian aims for rock solid stability

To be clear, Debian “stability” refers to “unchanging packages”, not “doesn’t crash.” Debian would rather ship a known bug for a year than update the package if it’s not explicitly a security bug (and then only certain packages).

So if you have a crash in Debian, you will always have that crash until the next version of debian a year or so from now. That’s not what I’d consider “stable” but rather “consistent”

Oh look. Debian changed the keepassxc package and now the keepassxc repo is getting all the bug reports for it. Their stance is “it will go away in a year or so”

Regardless of whether or not it is a good idea, it’s undeniable that Debian makes a lot of decisions that negatively impact their upstream. And since it’s someone else’s problem, oh well.

There is a reason upstream repo maintainers wind up angry about problems that someone else caused.

too lazy to type this obvious thing in?

This has been the thing for me. I get really bored and lose focus when doing all the obvious repetitive stuff. And the obvious stuff is the stuff I find copilot does best. For anything that requires thought I’m engaged. Those are the fun parts of the job. It lets me do more of the fun part.

The one major downside that I’ve found is that sometimes I just want to tab complete a long variable/function name, and because of copilot i dont have “old style” tab completion anymore. (I could definitely still handle this myself, but i haven’t)

edit: this all to say that I don’t use copilot to write code that I don’t know how to write, I use copilot to write code that I’ve written 1000 times before and don’t want to write again. Copilot does a good job of looking through all the open files for context to help make sure the suggestions actually fit into the codebase’s pre-existing style.

A lot of people don’t know this though. They think it is the “won’t fall over” type. They hear “use debian over ubuntu, because it’s more stable” or “use debian for servers, because it’s more stable” and think it means “You want uptime, so you dont want something crashing”. So when they see a bug, it is concerning to them. A distro focused on not falling over must super care about reducing crashes, and don’t realize the exact opposite is actually true. The bug was fixed a long time ago, but you don’t get it because “don’t change” is more important than “don’t crash”.

If the bug is in a popular package (ie, a super common screensaver) in a very popular distro (and a lot of people have chosen the distro because they think it has less bugs than others), I can imagine the maintainer getting fed up with the bug reports for a bug that was already fixed.

Most people I’ve seen on Lemmy understands that “stable” means “unchanging”… But every person I’ve talked to outside of lemmy, thinks it means “less bugs”. So clearly it’s a very big misunderstanding (Which is basically confirmed by the fact that xscreensaver gets so many invalid bug reports that they felt necessary to do this.)

If you received constant complaints from users about bugs that you had resolved years ago, but package maintainers refused to package, you’d probably get sick of it too.

Daniel Stenberg (author of curl) has blog posts about how everyone in the world uses curl, and as a result include the curl license in their readme, which means he gets mail from people upset about their car not working.

Steam had a big thing recently because the snap of Steam is not official. But yet, they get a TON of bug reports for things that are only broken in the snap.

I imagine having the same conversation of “That bug is already fixed as of 8 months ago” “Well how do I install the latest release?” “I dunno, talk to your distro about that” on a super regular basis, it starts being something that is incredibly infuriating. No one wants to take the anger of aggressive upset people, especially when the fault lies with someone else. He has asked Debian to stop shipping out of date versions of his software in the past. But because open source, they are not obligated to, so he has very limited ways to protect his own interests.

Your issue sounds like it’s with Debian for shipping incredibly out of date software and putting jwz into this position in the first place and not with jwz.

This is a daily reminder that “stable” means “unchanging” and in no way refers to the quality of the code. It doesn’t mean “won’t fall over”… That’s a different type of stable which debian stable absolutely does not guarantee.

A bug in debian will remain present in debian until the next update a year from now. If the bug breaks your workflow, then find a new workflow or a new distro.