Nope, Godot is open source, the current version can never become paid. If someone decided to make the next versions paid the community would just fork it and keep working on the free version. It’s happened with some other projects in the past.

I didn’t understood your criticism, what are they unwilling to release? What are they claiming all of? Why would ownership rules cause an OOM?

Sharing stack memory is a bad practice in C as well btw.

I just got to work and plugged my surface pro into my external monitor. It didn’t switch inputs immediately, and I thought “Linux would have done that”. But would it?

Nope. My laptop for example doesn’t automatically use an output when plugged in, but that doesn’t bother me because I know other DEs would do that, and it’s my choice of having a minimal window manager that causes that.

And this goes into your next point, because I know that this comes from decisions I made, I’m okay with that. I also know I could probably fix it somehow, even if just by running a script in the background that checks if an output is plugged and tries to use it.

And for me that’s the big difference. As a general rule when things break or don’t work are not the fault of Linux as a general, but of a specific piece of the stack, and more often than not it’s because that piece was backwards engineered without any help from the manufacturers of the hardware it’s meant to be controlling, so I can be very tolerant of these errors since the bad guys here are the third-party who’s refusing to make their things work on Linux. But even things that don’t work as I want to, I can make them do so, and that’s a huge change in viewpoint.

In other words, on Windows I used to be of the thought of things you can do, and things you can’t, with time I noticed that in Linux this thought shifted, to the point that the only question I ever ask myself is: “HOW do I do this?”. This implies that there are no impossible things in Linux, which is obviously false, but I would argue that the correct way to think about this is “things that are impossible on Linux, for now”, and that’s a huge difference, because Linux is always evolving and getting better and better, things you thought are impossible now might be trivial in a few months or years whenever someone with the knowledge to fix it gets bothered with it.

First of all you’re missing the point.

Drivers are automatic during setup.

That still means third-party drivers, so it’s still not a Windows win but rather a “windows is so ubiquitous that Logitech (or whoever) was forced to release a driver for it”, which is what the comment you’re replying was talking about.

Secondly, bullshit. In my 20 years using Linux I have never, ever, plugged in a mouse that didn’t get immediately recognized and worked as expected. What mouse do you have? You said Logitech, which model? The only thing that I ever needed specialized software on a Logitech mouse was to configure extra buttons or to pair it to a different dongle (both stuffs that also need specialized software only provided by Logitech on Windows)

Those are the usual problems in Linux, they can be summed up by “Third party companies don’t support Linux”, and they are especially annoying because with time you learn that there’s no reason that thing shouldn’t work, other than because the company either purposefully figures out if you’re running Linux and crashes the program (e g. DRM, anti-cheat, etc) or because they created their own closed proprietary protocol and refuse to share the public API for it so it needs to be reverse engineered.

At the same time I think most people don’t think about how much prior knowledge you need to just be able to use Windows or Mac. And for someone without ANY prior knowledge all of them are the same.

Story time, my MiL is a zero when it gets to computer literacy, to the point that every week I had to solve something for her. Eventually I gave her a laptop with Linux in it to make it easier for me to do support, and to my surprise she had lots of problems the first months when setting things up and until learning the ropes, but afterwards there were almost no problems.

The thing is that people have a lot of Windows knowledge, so when they try Linux they expect it to be Windows and get frustrated when it’s not.

I’m fairly certain that SSH and whatever else you’re exposing has had vulnerabilities fixed since then, especially if modern distros refuse to use the ssh key you were using, this screams of “we found something so critical here we don’t want to touch it”. If your server exposes anything in a standard port, e.g. SSH on 22, you probably should do a fresh install (although I would definitely not know how to rebuild a system I built almost 20 years ago).

That being said, it’s amazing that an almost 20 year old system can work for almost 10 years without touching anything.

Any OS can break and need reinstalling if you screw stuff up, but the majority of them would have a hard time running constantly for almost a decade without so much as a side glance.

Came to say this, I remember when I first looked at VLC version and saw Rincewind (I think it was), and was like “this has to be a Discworld reference”

Realistically whatever problems you see in python will be there for any other language. Python is the most ubiquitously available thing after bash for a reason.

Also you mentioned provisioning scripts, is that Ansible? If so python is already there, if you mean really just bash scripts I can tell you that does not scale well. Also if you already have some scriptsz what language are they on? Why not write the function there?

Also you’re running syncthing on these machines, I don’t think python is larger than that (but I might be wrong).

Or maybe it causes other bugs or security issues that are not widely known because most people use it with different flags.

It’s no more or less secure, it’s just more customisable.

Not really, on Gentoo you can set use_flags to disable entire parts of a binary. Is it useful? Is it worth it? I personally think not, which is why I stopped using Gentoo, but it’s definitely more customisable than Arch.

However that has nothing to do with doing illegal stuff, not sure where he got that idea from.

The block thing is nice, would love to have that. Not willing to sign into a cloud thing to use a terminal though.

I never realised that for most people terminals don’t have intuitive shortcuts. But most terminals use Emacs shortcuts, so if you get used to that it becomes quite intuitive. I know those shortcuts are not universal, but it’s not that the shortcuts aren’t there, or that they didn’t used a standard, it’s just that the standard they use didn’t become the standard most people are used to.

I’m sorry, but I think we have a mismatch on our understanding of the word proprietary. A desktop PC has some proprietary things, firmware, and the likes are almost always proprietary, as in they’re the propriety of the company that made it, which means that if someone else tried to make them they’ll get sued. But most of the schematics and connectors are an open source standard. Which means that if something breaks, you can buy a replacement from a different company and everything should work.

Laptops are mostly the same as well, in fact they use much of the same standards, the thing is that the form factor makes it difficult for third-parties to make the pieces, but they exist, and are legal.

A company can charge as much or as little as they want to fix their device, that has no impact in whether the device is proprietary or not. If you are legally allowed to open, repair it and change parts with third-party ones it’s not proprietary. If anything in that chain breaks, e.g. you’re not allowed to open or repair, or third-parties are not allowed to make replacements then it’s proprietary.

Besides having made a device that’s essentially as proprietary as a desktop (which is to say almost no proprietary at all), Valve is also offering their own replacement parts and cheap repairs, which are all things to commend, but if Nintendo did it for the switch the switch would still be proprietary.

Most of what you mentioned is right to repair, which is important and all the more reason the Deck should be praised, but it’s not what proprietary means.

The PC ecosystem has all of that though, including different vendors providing parts on open standards such as power delivery or data transfers. Yes the Deck is open and awesome, but so are PCs. In fact part of what makes the Deck awesome is that it’s essentially a PC.

Depends on what the average user wants to do, here’s a list of random things off the top of my head that require system wide changes, i.e. they will get overwritten with the next update (which btw means you’ll need to do these at the very least monthly, but might be daily if you also want the latest SteamOS updates):

• Configure a Logitech gaming mouse, while the program to do this (piper) has a flatpak, it depends on a library (libratbag) being installed system-wide. There are technical reasons for it, but in short it means it doesn’t work. This is not a problem on most Linux distros because you can just install libratbag using your package manager.
• Use something that’s not KDE. If you wanted to use GNOME, XFCE, i3, or whatever else, you couldn’t. You’re stuck with KDE, if you find a way around it better automate it, because next update it will be gone.
• Plug non-standard stuff that requires custom udev rules, e.g. using ADB on android phones. If you want to install things from your computer onto an android phone or of you want to root your phone you need to use ADB on it, however ADB depends on some udev rules for some android devices to be properly recognised, most distros have a package called android-udev-rules or something similar that has those configurations.
• Change your boot manager. Doing this is likely to fuck up the deck, since the next update your boot manager will be deleted but the standard one might not get reinstalled. I don’t know exactly what would happen, but my guess is that every update you would need to either go to the bios to temporarily set the old boot manager back, or boot using a live image and reinstall your boot manager.
• Change kernel parameters. There are plenty of reasons to want to change your kernel parameters, and whatever changes you make will need to be redone every update.
• Install custom kernels.
• Install firmwares.
• Install drivers.

That’s just what I came up with half-asleep in 5min, I’m sure there are plenty of more examples. Yes a user might go his entire life without needing any of that, but someone who doesn’t know Linux will get frustrated if he needs any of it and nothing that he does work and when he gets it to work it’s reverted the next day. On the other hand, someone who knows Linux doesn’t need to be told any of this, because they understand the limitations and why they exist, and can work their way around it, but most importantly probably wouldn’t ask if the steam deck can be used as a PC or if it’s proprietary, since the steam deck in kind of a big thing in the community.

What’s wrong with that phrase though? In your opinion Is the deck more or less proprietary than a PC?

I’am not, those are flatpaks, that’s not the same as system wide installation. You can’t change system files on the deck unless you unlock it, and even if you do that your changes will get reverted next time there is an update, because that’s how he system is designed to work, every update a clean slate.

I own a Steam Deck, reserved it on the first 15 minutes. I use Linux daily as my main OS for almost two decades, coincidentally most of my machines are also Arch based. I know what I’m talking about. You don’t want to use SteamOS for your daily computer, the system is purposefully handicapped to work as a console, if you’re doing the occasional browsing or text editing it works, the moment you need to touch system things it goes down the drain very fast.

I’m not shitting on the deck or SteamOS, I have a deck and never even considering switching the system. But you need to know the limitations of it. The system is designed for gaming, trying to use it as your main computer is bound to give you headaches even if you know your way around Linux and can think on appropriate ways to bypass the limitations, from things like podman to user services to overlay fs.

SteamOS has the root filesystem set to read only, this is because of the way the system gets updated, and also makes it sure that every deck is running the same system. So you can’t change system configs or install things on the system. You can get around these by installing things for your user and creating services for your user. It’s doable if you want a gaming device that you use for some other things, but it’s not very convenient for a day-to-day drive.