Only in the licensing space in particular there is really no good reason to hide the exact rules what is acceptable and what isn’t. Nobody is going to circumvent your defences if they know exactly which licenses you allow.
Really though, what were they thinking. Why would anyone risk staying with unity after all their bad decisions, especially when they clearly have no intention to stop being dumb.
I moonlight as a small app developer. This is absolutely correct. I have a handful of legacy apps which uses Unity, and makes so little that moving them would cost more.
That said, if/when I do another project, it won’t be in Unity.
Which signals to investors that there is little to no expected growth. If you aren’t attracting new customers to grow your user base, then you only have the option to milk your existing customers to increase revenue.
That may work short term, but long term it signals a death knell for the company, since as the old customers retire or the studios close down, the new crop of game developers would have been trained on or adopted a different engine so aren’t going to switch to Unity. Eventually they just run out of customers.
edit: The following is off topic, but I’ll.leave it as a testament to my gray-beardedness. In my defense: Unity isn’t Unity anymore. Don’t get old.
I’ve been using Linux for 30 years now, and for a while I was an advocate for Ubuntu and Canonical (among others, I’m pan-distributive). Then things changed: GNOME 3, Wayland, Unity, something-sonething, Snaps… All too much.
As an advocate, I’m apt not to emerge with favorites, or to yuck others’ yums. Neverthekess, Canonical is a press beyond the pale, many days.
In the end, I don’t recommend Canonical distros. LMDE is solid, as are most of the *bian and redhat downstreams. I don’t recommend the others because I don’t know them, but more importantly I couldn’t help a friend un-bodge a bad installer on them (likewise for "BSD or Darwin).
But really, no love for Canonical. They went to some Dark Side, and I’ll have a hard time forgiving them for it.
I also thought of Unity the DE before reading the article
I understand the confusion. This doesn’t belong to a Linux community. I mean, I see the relation with FOSS but I’m sure there are FOSS communities out there. The article doesn’t even mentions Linux, just Windows and Android.
With ibm working hard to enshittify redhat even faster than newredhat themselves, we should consider avoiding them as a first-class porting and work target.
Look at OpenEL as a successor to the RH and an upstream for the other ELs once RH starts eating from that tasty “free stuff they can sell” trough. Having made bank on TheForeMan without actually making an effort to support it, they have a model they can use for everything.
I went to a game dev meetup in Seoul last year. Everyone was using Unity.
I went again last month. Half the people were using Godot.
For a bit more context, I used to work in the gaming industry. We used Unity because it was great for making money - drop in ads and tracking, you’re good to go. The Godot ecosystem isn’t as mature for that yet. However, even we were considering switching to Godot. It wasn’t worth switching for a number of reasons (besides the above mentioned ones, Godot is also “laggier” and we have some heavier games), but had we started shop yesterday, it’s safe to say we would have used Godot too.
Unity just laid off 25% of their workforce. That is not a small number. Their days are numbered.
Make sure you have the latest firmware for your motherboard. This sounds like unstable voltages for memory, or an overly-aggressive PBO curve. Did you try disabling the XMP profile on the RAM, disabling PBO, and upping the voltages (within safe limits) of the SOC, DDR, and VDDP? You might find some useful info here[0] or here[1] if you intend to run your memory at 3200 MHz.
Motherboard firmware is up-to-date, and I’ve already tried disabling XMP. I’ll give disabling PBO a try, thanks!
I don’t necessarily have to run at 3200MHz, if it means that the system is finally stable. But since it’s already crashing at the default 2133MHz, I suppose there’s no use in playing with the voltages?
It’s difficult to say for sure with certainty what the issue is without trial and error. I would expect that the motherboard’s manufacturer would make sure that their board can successfully pass all tests with the standard JEDEC spec for DDR4 (2133 MHz).
Since you say that you’ve tried different RAM kits, another alternative could be the cleanliness of power from the power supply. Perhaps there is intermittent voltage droop, and you need to experiment with the Load Line Calibration settings to adjust for vdroop between idle and load. Disabling frequency boosting and manually setting the CPU frequency could help check if it’s related to that. PBO curves might be undervolting too much while idle.
I’m a bit speechless right now. I’ve disabled PBO and didn’t have a single crash since then, everything’s been running fine for hours. Just to make sure that this really was the issue, I’ve enabled PBO again - but still haven’t experienced any crashes in the last hours. I have no idea how simply disabling and then enabling the feature again fixed my issue, but for now it seems like all is well.
Do you have any explanation for this weird behavior?
Anyway, thank you very much for your suggestion, looks like this actually did the trick!
Sounds like voltage droop and/or a motherboard with faulty automatic “training” settings. I don’t recall if the Ryzen 3000 had custom PBO curves, but tweaking this can fix it. Upping LLC and the SOC and CPU voltage slightly alternatively could help. Though I’ve had my most stable overclock by disabling PBO entirely and using a manual CPU multiplier.
I had a similar conundrum: what to use on a Thinkpad X60s, which is a Core Duo machine. I tried Arch 32, but after trying Debian, I stuck with the latter.
I usually only use it as a dumb terminal via SSH, but Debian was just sort of… easier.
This is interesting to me for my use case scenario, specifically SteamOS.
What I’m trying to do is run an emulated Everquest server (lookup EQEmu). The community there has several methods of installation of the server, Windows, Linux, and Docker. The hurdle to overcome is the immutable file system, specifically when it comes to the database (MariaDB). I think I may have found a work around via Linux brew and installing MariaDB through that (which I’ve done, I just have to make the final connection). However the Docker setup, when running it on a separate distro is stupid easy. If they make this a Flatpak, it can potentially be the solution I’m looking for.
Really the end goal is creating a Single player Everquest. I have a dual boot with it operating via Windows, but would much prefer to have it on the SteamOS side of the house.
Docker Desktop ≠ Docker Engine, and I think what you (and several in this thread) are thinking is actually Docker Engine. Docker Desktop ultimately includes a Docker Engine inside, but it does not appear you need that virtual machine (e.g. running non-Linux code). See: docs.docker.com/desktop/faqs/linuxfaqs/#what-is-t…
Docker Desktop is based on KVM, which already works with Flatpak. So this is not something new. For example, GNOME Boxes is available as Flatpak and provides a way to run KVM guests in SteamOS.
Starting with version 3.5 (the current stable) SteamOS already includes Podman with the default installation. And running the daemon-y Docker Engine “bare metal” is not going to be any easier with the immutable filesystem. While Docker Desktop solves this by using KVM, it adds another layer with performance loss, vs. just running Podman containers.
So what you want is already available, and no Docker Desktop is actually needed.
But so if Docker Desktop does include Docker Engine, does that mean I wiill now be able to run Docker (with a some performance loss) simply by installing a Flatpak, i.e. I won’t even need to touch the CLI?
Yes. If you mean “CLI” as for e.g. pacman install, it is a GUI (Electron) application, so I expect will install straight from e.g. KDE Discover and then run without you touching the shell.
Installing podman-compose with the immutable filesystem is fairly straight forward, since it is just a single Python file (github.com/containers/…/podman_compose.py), which you can basically install anywhere in your path. You can also first bootstrap pip (python3 get-pip.py --user with get-pip.py from github.com/pypa/get-pip) and then do pip3 install --user podman-compose.
[cosmic-randr] uses the wlr output configuration Wayland protocols.
Does this mean cosmic-randr should work on other compositors that support the wlr output configuration protocol (e.g. sway, hyprland, river, …)? It’s great to see cosmic adopting existing protocols, instead of compositor specific protocols (or worse, no external app support at all).
Also, it’s great how portable Cosmic DE seems to be, as it’s already mostly packaged on NixOS. On first look, cosmic-term seems to be a quick terminal so I might switch to it, as well as cosmic-files.
If they support the wlr output configuration protocols, then yes it’ll work fine. There are some more advanced features that we want that aren’t supported by the protocol though, so we will likely develop some cosmic protocol extensions for those features.
i think they are already mentioning it: MS has a help webpage on how to install linux, both WSL2 on Windows machine, or how to burn iso and install linux on bare metal. learn.microsoft.com/en-us/linux/install
Microsoft have quite a bit of software that runs on Linux (PowerShell, VS Code, .NET, Azure tools, Intune / Endpoint Manager, even SQL Server) so it’s understandable that they’d have documentation to explain it to their customers.
Yep, they run it themselves even. Previously their motto was “Linux is a Cancer” now they have embraced it and developed their own distro (CBL). With how everything is going WebApp these days, I can see a day when Windows will be linux based kernel.
They already have a Windows version for a handheld. The Xbox runs a modified version of Windows 11. All they’d need to do to bring it in line with PC handhelds is allow the install of third party launchers (they probably wouldn’t do this though).
Despite the CPU being 64-bit, the distro MUST be 32-bit. This is because of the MacBook’s BIOS, which prevents 64-bit bootloaders from working.
That’s the thing, you can run a 64-bit distro as long as you’ve a 32 bit grub starting it :) You run Debian 12 amd64 on a 32 bit EFI:
As of 2023 and Debian 12 the amd64 installation media (available in netinst form) includes the UEFI boot loaders necessary for both i386 and amd64 boot. By selecting “64-bit install” from the initial boot menu, debian-installer will install a 64-bit (amd64) version of Debian. The system will automatically detect that the underlying UEFI firmware is 32-bit and will install the appropriate version of grub-efi to work with it.
I am running 10.6. Chromium Legacy is for 10.7 and above, and the same is true of a lot of software. Meanwhile, on my Linux partition, I can have Firefox Nightly if I want. It’ll run heavily, but it’s possible.
As it happens, I do have a somewhat recent browser installed in OSX, but it’s not great.
Also, running an older OS like that isn’t a good idea, as it won’t have received security patches or microcode updates.
That’s the thing, you can run a 64-bit distro as long as you’ve a 32 bit grub starting it :)
I hadn’t quite considered that somebody had implemented this. Thanks for the info!
There was also another user who gave me a link to some software that modifies mixed-mode ISOs so that they will boot on my potato laptop.
I am running 10.6. Chromium Legacy is for 10.7 and above
Can’t you run 10.7 on that laptop? It seems like you can, and that will greatly improve your software situation. Another thing to consider is to replace the HDD with an SSD. That computer will run any SATA drive (I’ve tested with modern WD blue drives), just grab something like 250GB for 30€ and enjoy speed.
There was also another user who gave me a link to some software that modifies mixed-mode ISOs so that they will boot on my potato laptop.
Yes but Debian provides that out-of-the-box and officially supported. That means everything will work fine and as stable as Debian is usually.
I would suspect that making a stable desktop inside docker ensures it would work everywhere else, no matter what the hw/sw of the host is.
I've only known docker as a building environment that ensures rebuildability and I can't say I ever liked it. I think its popularity comes from some myth of safety and security.
The worst documentation of a linux distro I have ever encountered, but the declarative model has convinced me I don’t want something else. Now I’m just waiting for other distros to pop up that are declarative as well. (Guix? No thanks, I’m not a fan of endless parentheses)
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.