LeFantome
Other than having to know Rust, adding Rust to a C code base is not difficult. They play well together.
There is no need to rewrite old code but, once Rust is there, you are free to.
Linux is a bit of a special case as you cannot just blindly use the Rust standard library.
Having to have a Rust tool chain to build with may or may not be an issue.
For some use cases, like BSD or the Linux kernel, platform support is also a consideration.
In that talk he called C “the worst language” and said he chose it to troll the industry. How does that support your point?
He also said that you should choose “least privilege” whenever possible. That is precisely the value that Rust brings over C. So how does that talk support the idea that C is more secure than Rust?
I have seen stats that both Linux and ChromeOS have around 3.5% market share.
If ChromeOS continues to converge with proper desktop Linux, I consider it a distro which makes 10%+ possible this year.
The wild card for me is Linux gaming. It may not grow fast but it totally could.
Which had me wondering for the first time I hearing about “The Year of the Linux Desktop”, what percentage do we have to hit for this to be the year?
I don’t really expect us to hit it but, for the first time, I feel like it is possible.
You can do this, and I have, but there can be issues during the switch if you are not careful.
The machine I use as my Jellyfin server used to be Manjaro and is now vanilla Arch ( having migrated it from Manjaro to Arch in place ). It still has a few quirks though. The quirks do not matter for what I use it for ( it is rock solid for Jellyfin ) but anytime I have to reboot or use the desktop, I am reminded. Nothing too serious and nothing I could not fix with a little time of course. That machine is purely functional though and I do not want to spend any time on it. Since my video is all on a second drive, I will probably nuke it and do a fresh EndeavourOS install one of these days. It would be much faster to re-install Jellyfin than to fix all the little warts. The other Manjaro systems I had were replaced with fresh EndeavourOS installs.
There are many cases where Manjaro causes problems. For example, a package mag already be in Arch but not yet in Manjaro. Or perhaps the Manjaro package is not a high enough version number. If another Arch package requires this first package, in Arch it would grab the Arch package. The Arch package will be maintained over time. In Manajaro, the package is not there and so the AUR grabs it from the AUR as well. Perhaps it is even the Git version with an unclear version number. Over time, the AUR dependency breaks or becomes unmaintained. Even once Manjaro has the package, it may not migrate it because of the version numbers. Now things are broken. This exact thing happened to me on Manjaro where my GIMP ended up using GEGL from the AUR. My system was broken for months.
An even worse problem can happen when there are alternate dependencies. Sometimes in the AUR you will have multiple packages that fulfill a dependency. In Arch, you can see if one is from the actual repos and one is itself from the AUR. Again, if you choose the one in the repos, it will work and stay supports. In Manjaro, neither may be coming from the actual repos in which case it is easy to choose the wrong one. This sets you up to have package conflicts. In Manjaro, I would never know that the other option had now been added to the repos. More than once, I had the dependency that I had chosen break when the other would still have been fine.
Ok, this is getting long and that was just a couple of scenarios.
Suffice it to say, when I used Manjaro, I got the impression that the AUR broke all the time and that using the AUR broke my install from time to time. Now that I use Arch, I do not have those issues and I realize that it was Manjaro all along.
I used to be a huge Manjaro fan. There were many ways it let me down, some of which were just bad governance.
The biggest problem though is the AUR. Manjaro uses packages that are older than Arch. The AUR assumes the Arch packages. This, if your use the AUR with Manjaro, your system will break.
It is not a question of if Manjaro will break but when. Every ex-Manjaro user has the same story.
For me, EndeavourOS is everything that Manjaro should be.
If you are a Linux user and like commercial games, you probably would prefer them to work on Linux.
“Market share” on Linux aligns the vested interest of game makers and Linux game players. If the company thinks it can make money, it will do more to allow games to run, or at least do less to stop them.
As a long-time Linux user, I feel like it says something about the maturity of desktop Linux that it is good enough now for the kinds of users that find LibreOffice insufficient.
I realize that the major point of GIMP 3 is the port to GTK3. That said, I feel like colour spaces are what people have been waiting for and probably the most significant deficiency that keeps GIMP from being treated as a professional tool.
If they are really this close, why not set the GIMP 3 release date for when colour management is ready?
Non-destructive editing will be huge as well. GIMP 3 is really going to be a crazy leap forward. It is going to be amazing to finally get access to all this work that has been walled off for decades.
The bug situation sounds terrible. Honestly though, they should just get 3 out and then make bug fixing the number one job until it gets into better shape.
Not only is it a small team but right now there are basically two different projects ( 2 and 3 ). With only one code base, perhaps the pace of progress can improve.
Hopefully the move to GTK4 is easier.