Quoting: drlamb

Quoting: Arehandoro

Quoting: minkiu

How do you like these keyboards? Did it take long to get used to them? I attempted to use one before I knew how to type properly and it was a mind bender.

I have issues typing on standard keyboards comfortably due to American football injuries to both hands. This led me to prefer chiclet keyboards over mechanical due to the low actuation force. It wasn't until I forced myself to learn to type properly that ergonomic keyboards started to "click" for me. I've now got the logitech Ergo K860 [External Link] and I love it. If this keyboard had back-lighting and the build quality of the MX keys it would be perfect in my eyes.

The open source firmware and the fact that system76 makes this keyboard makes me want it but I'm afraid it would be physically painful for me to use. Hopefully there is an ample return window as I'd really like to try it.

It's possible, by what you say, that you just need to choose the correct switches to be comfortable on a mechanical keyboard. I'm thinking linear switches with not too high of an actuation force might be what you want. Key travel might need to be addressed as well. It's possible that it could be a sticking point.

View this comment - View article - View full comments

Quoting: kon14

Quoting: mrdeathjrThis only applies in specific cases like lastest kernel hardware support case intel or amd gpus for example

For most users lts is enough for gaming (included proton)

:smile:

I'm not suggesting it's not doable, I'm just saying it's pointless and causes way more trouble and performance issues (though mostly lack of support for latest features) than a non-LTS branch ever would for a desktop use case.

Quoting: KimyrielleThat makes no sense at all. Steam will update Proton automatically and your graphics driver will update when the system does (in case of NVidia you have to add the correct launchpad PPA to your repositories, but that's all). Both of that happens whether you're using LTS or not.

Which means that depending on your distro you mind have to resort to using third party repositories or mix and matching branches which is always prone to dep collisions.
Remember, my original comment was not Ubuntu-specific, but even in that case you're still shooting yourself in the foot over nothing.

It wasn't until fairly recently that DXVK finally stabilized and stopped requiring bleeding edge drivers so as to support new features, but DXVK is not the latest tool in the shed anymore and it's far from the only one benefiting from not being stuck with an outdated system.
I'm not rooting for bleeding edge distros here, this is strictly about sta(b)le branches (LTS) vs latest releases.

It might end up being sort of ok if you're on Nvidia and have an official repository for nvidia-drivers (or your package manager supports seamlessly installing packages from different branches with little trouble) since you won't ever need to update the rest of the stack, but if you're on AMD you'll want to stick to the latest mesa which is definitely not going to play nice with older packages on an LTS branch.

Quoting: no_information_hereNo.

I have no idea how you came to this wrong conclusion, but you can easily correct your information.

Oh no, a random comment suggesting my null point should be revised without even considering the implications, how will I ever recover?

This hasn't really been my experience. It seems like you are least likely to have problems with Steam if you run the most recent LTS of an Ubuntu based distribution. If your AMD or Intel graphics card is too new to be supported by the most recent LTS release or there are improvements for it, then adding a PPA for Mesa and one for Mainline (or Ukuu before that) to get a newer Ubuntu kernel has never caused an issue for me. This approach seems a little less likely to create problems than upgrading to each 6 month release of the distribution (which I have done before).

View this comment - View article - View full comments

Quoting: dudeI miss Nvidia since I switched from Intel/Nvidia to AMD (3700X/RX6800) just because AMD pushes open source. But regarding the "expierience", It's bug hunting again instead of gaming. At least with my VR setup.
So, no, I still wouldn't recommend AMD over Nvidia on Linux right now, except if you have a very special reason. Nvidia with Manjaro was great, AMD gives me just headaches.

On the other hand, I haven't had any issues to speak of with my arrangement. However, I still have a bit older card with established support (Vega 56), I don't have any VR equipment, and I rarely use Proton. I don't know how much difference each of these factors make, but I'm guessing at least one of them is significant.

View this comment - View article - View full comments

Quoting: Purple Library GuyAnd the mome Wraths outgrabe.

O frabjous day! Callooh! Callay!

View this comment - View article - View full comments

Quoting: LinuxerNvidia as GPU makes also this one a deal breaker. Nvidia drivers eventually always break and the community can't possibly help them become better being closed source, Nvidia aren't cooperating with Nouveau of course ..

AMD all the way baby

Yes, I am reluctant to get a laptop with Nvidia graphics for this reason. The last "gaming" laptop I had was an MSI with a Core2 Quad processor and an AMD Mobility Radeon HD 4650 (I think; I know it was something in the HD 4000 series). Since then I have more concentrated on models with good battery life.

I have an old HP laptop from before 2010 (probably around 2008) with an Nvidia Quadro GPU and it had been working well with whatever version of Linux I put on it using the proprietary Nvidia drivers until I updated to Xubuntu 20.04, and then I started to have refresh issues with the terminal when running Compton (for tear free, hardware accelerated compositing; the built-in compositing in Xfce still has issues even with the version in Xubuntu 20.04). In this case, I found the easiest way to deal with it seemed to be to just use the Nouveau drivers, since they have pretty good support for video that old. I guess in a way that's a good thing, but it won't work for new Nvidia hardware.

View this comment - View article - View full comments

Quoting: IzaicToo bad it doesn't support Wayland now that Xorg is abandoned.

Well, Xorg is in maintenance mode. Perhaps by the time they drop Xorg support altogether Xfce with Wayland will be supported.

View this comment - View article - View full comments

I've played quite a bit of Children of Morta at this point. It can be a bit grindy at times, but I'm still having fun with it. I have a long way yet to go.

View this comment - View article - View full comments

Quoting: GuestIf you "agree to receive marketing" email spam, yes.

Yes, which also amounts to signing up for an account. So, if you want to use GOG, then you are signing up for their promotional emails anyway. They don't spam you terribly badly. A few emails a month about sales, usually.

I don't blame anyone who wants to avoid being on their promotional spam list, but if you want to buy from them, you can't really avoid it, and they do offer DRM free downloads. Unfortunately, they don't have a Linux version of their management software, Galaxy.

View this comment - View article - View full comments

Quoting: CyberRat

Quoting: nadrolinuxPipeWire

PipeWire?

Past: 5 audio engines "Yea lets unify the audio engines"
Current: 6 audio engines

This ends up not really being one of those cases. Pipewire (at least as it applies to audio) is a sound server for Linux. Sound servers operate at a higher layer than ALSA (which doesn't appear to be going anywhere soon). There have been several sound servers for Linux in the past (including aRts and ESD, among others), but at this point they have all been essentially abandoned other than PulseAudio and JACK. PulseAudio is supposed to be the easy to use sound server, and JACK is supposed to be the professionally capable, but complex sound server. Pipewire seeks to be capable of replacing both of the remaining Linux sound servers. If it's good enough, it could end up being the only Linux sound server that still matters in a few years.

View this comment - View article - View full comments

Quoting: GuestThank you pulse for now deciding to output audio on a completely different path and not actually save settings when I change them.

(I'm one of those people who has neverending problems with pulseaudio....just lucky I guess.)

Pulseaudio not easily saving settings changes is probably my biggest current peeve with the program.

View this comment - View article - View full comments