![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/4271bdc6-5114-4749-a5a9-afbc82a99c78.png)
I tried using connman to setup a wireguard connection once. It was not a good experience and ultimately led nowhere, due to missing feature support.
I tried using connman to setup a wireguard connection once. It was not a good experience and ultimately led nowhere, due to missing feature support.
If anything, he gets most of his inspiration from MacOS.
It’s always been a “whole ass computer”, not some kind of simple storage device.
The joke in the OP stops at the beginning of the joke explanation. If you just share your honest opinion like that in a shitposting community, you can’t expect everyone to “play along” with your “joke”.
Pretty sure that the registry path for official images is “library” (at least it used to be). So it should be “docker.io/library/debian”, though I can’t double check at the moment.
It will probably just work, even if not officially. If any weird Windows issues crop up, Microsoft may or may not fix them. I think AMD even provided workarounds and special drivers for Windows 7, just without any official support. They may not do that this time around though, since a lot of things have changed.
Try to imagine that argument but coming from some government you really dislike. I can think of a lot of different media that might inspire violence and instability, but which would be really important for people to see or at least know about. Frankly, anyone who doesn’t see that as a potential problem is being shortsighted and really needs some historical perspective, in my opinion.
I know, I did read your entire post. As I said, it’s not unheard of for Windows drivers to be more fault tolerant in suboptimal conditions. For example: Windows GPU drivers in the early days of HDMI 2.1 needed a lot of tuning for tiny oltage adjustments to ensure signal integrity if your cable wasn’t exactly up to spec, basically compensating for a “bad” cable, whereas the Linux drivers at the time didn’t really try to do that. This doesn’t have to be the case for you, but it should be relatively easy to test.
If the cable made a difference, then that may still be the limiting factor. It’s not totally unheard of for Windows drivers to be a little more fault tolerant or better tuned for suboptimal cable connections. If you aren’t already doing that, try using a certified cable that supports the bandwidth and features you require for your setup. Besides that I guess you could only try the newest kernel version you can reasonably install.
I haven’t used TypeScript in a classically OOP way and it never felt like I was being urged to do so either.
There’s a reason for the early rise in popularity of independent gaming reviewers and it isn’t the hard-hitting, honest quality of mainstream entertainment journalism at the time. With the advent of influencers though, it feels like everyone is just regurgitating the same pre-approved, publisher-friendly nonsense. I’m sure there are exceptions, but it feels more difficult today to find an honest review when every random internet personality is signing sponsorship contracts that require them to praise the game every 20 minutes.
There are two ways to save your work in either program. You can save your actual work, so you can continue editing at some point and not lose stuff like layers, image quality and other information or you can export your work into some kind of image file, optionally compressing it and discarding extra information about the project. I think GIMP even offers a shortcut for this called “Overwrite …”. How is this an issue?
wayland doesn’t seem to support nvidia as well as X does, just due to development focus
Ymmv with Nvidia, but that has nothing to do with development focus and everything to do with Nvidia’s refusal to use the same interfaces Intel and AMD use. Most of the way Nvidia works or doesn’t work with X or Wayland is down to Nvidia’s driver stack. Personally I’ve not had much positive experiences with Nvidia on X.
Like yes major releases and distros are moving to wayland now, that just means they find it stable enough to start doing development on it.
That happened literal years ago. The reason you’re only noticing now, might be because KDE has gotten their Wayland implementation to a reasonably stable point. Gnome has supported Wayland for some time now and other DEs probably don’t have the resources to move on from X. I don’t see the distros that are only switching over now as major contributors to any development specific to Wayland.
I don’t take issue with your preferences. Maybe you’re better off with X for now, that’s fine, but you make it sound like Wayland is just full of issues and has barely even entered some kind of pre-release state for software masochists.
Except when X doesn’t fucking work ™ and hasn’t properly worked in literal decades. I don’t think I’ve ever managed to get rid of horizontal tearing with X. Calling X feature complete is pretty funny, but it isn’t. So many things were never fully implemented, because it’s just an impossible amount of work or would require some major rearchitecting. You don’t have to deal with updates because literally no one wants to develop it any further or even maintain it. The devs have moved on to Wayland or other things.
It’s fine if it works for you, but I’m getting tired of Linux conservatives projecting their own experiences on everyone else and declaring Wayland as “not ready yet” and handwaving all of X’s obvious problems away because they’re used to dealing with them. I’ve used Wayland as a default for all my machines for years. After a rough beginning where major features were still in development, now it works. XWayland works. Native Wayland apps work. I don’t have tearing anymore. I’m not going to pretend that that’s the universal experience, but a lot of people are using it just fine right now.
Then trying to nag you into saving it to some unknown unused bizarre gimp extension.
You mean saving a project file? The same way you’d save a PSD file in PS, so you can actually save all your layers and go back to make an edit? It’s been a while since I’ve used Photoshop, but I’m pretty sure both GIMP and PS offer two different workflows of saving/exporting your work and they are just named differently and have different keybinds. I have no idea how you can act like you actually tried to use GIMP as something other than a drop-in replacement for PS, but then call the default GIMP project file format “unknown, unused and bizarre”…
Consider what trace minerals actually means, then think about the tiny amounts of salt used for cooking.
I’ve been hating on the raw food movement for much longer than lemmy even existed. Drinking raw milk is especially stupid.
I want to do that, but not because of Flatpak. That’s incredibly far down the list of things I find offensive in my professional life. At the very least it does fulfill some sort of purpose and also doesn’t cost any money to use.
You mean hiding their public IP? I guess that’s a feature.
The only thing that’s slow is dnf’s repository check and some migration scripts in certain fedora packages. If that’s the price I need to pay to get seamless updates and upgrades across major versions for nearly a decade, then I can live with that.