I believe Inkscape is still working towards GTK4, but yes they are much farther ahead, to be expected when there are more developers active, after all.
GTK has long outgrown GIMP, it’s much more general purpose now, though the acronym remains. Who knows, maybe it’ll be renamed to GTK Toolkit in full MIT hacker style one day
I use NixOS for University and would highly recommend it if you want a highly configurable system that’s declarative, however, NixOS doesn’t have great documentation for certain features and usually does things differently, so you’ll have to learn the Nix way of doing things. On the plus side, I’ve never been unable to fix my OS when it broke, you simply rollback, or if there isn’t a suitable rollback, you can plug in a live usb and set the system to use a specific commit (can’t remember the exact command for this and that’s presuming you store your config with git). Also according to these statistics nixpkgs has more packages than the AUR.
I think you just mean “declarative”. Highly configurable is literally any distro. I’d say NixOS is actually LESS configurable by design, but that is sort of the point: a repeatable image based on a template no matter what.
This actually makes it sound like Xorg will be supported longer than I thought.
I understood RHEL9 to already be Wayland based and so I was expecting the clock to runout on Xorg when RHEL8 went off support. RHEL9 does default to Wayland but it sounds like Xorg remained a fully supported option for those that wanted it. The move to Wayland only being proposed for RHEL10 did not happen on RHEL9.
RHEL8 goes off support in 2029 but RHEL9 is supported until 2032. The implications of this article are that Red Hat will not put much energy into Xorg after 2025 ( RHEL10 ) but they will still have to support their customers. This at least means security fixes but it likely means continued viability of modern hardware to a certain extent as well.
Regardless, this also highlights one of the “hidden”‘contributions of Red Hat and how much the entire ecosystem relies on them. This can be seen as good or bad but I wish the public debate involving them would at least accurately reflect it.
And even beyond that, because any distro that ships Wayland by default does so because it has XWayland as a backup, which is essentially running an X server inside Wayland.
Xwayland is likely to be with us a very long time. I do not see Motif adding Wayland support anytime soon for example. How long for GNUstep to hop on board?
Agreed ( on the code ). Wayland and Xorg also share libinput, libdrm, KMS, and Mesa.
The biggest difference is that Red Hat will stop bundling this stuff up together, testing it, and created releases. Most of the actual code will still be maintained though.
The instructions say ALLOW_EMPTY_PASSWORDS=yes. They also say this is meant for development purposes only, I assume they mean you should build a dockerfile for something more pressing like a prod environment.
Looking for similar myself. I love cbpp, based on openbox, it’s just out of my way and lets me do my work. but I want to move to wayland, thinking kde plasma, spend for ever changing it to my liking and some how export all changes. probably a bash script first but thinking long term write it in ansible.
But i’d much perfer to find a stock/sane solution.
Not enough yet, made a list of apps I need, moved the dock/bar to the top of the screen. only have kde installed on my personal laptop, I don’t any where near enough time to spend on it, my desktop isn’t for playing around on.
you should have no problem doing Python dev on nixos, it’s basically made for doing development environments like this without the need for containers. you should just be able to set up a nix shell for your project that contains python and all the necessary dependencies, and then enter the shell. then, you’ll have all the right dependencies installed for your project and still have access to any editors you have installed
Both are more on the tinkerer-side, and for university you need something reliable and easy to use in my eyes.
And that might be Fedora Silverblue/ Atomic (or universal-blue.org to be more precise for QOL-tweaks).
It is definitely more simple, stable (release cycle) and also more reliable, since there’s only one base (Fedora packages + your DE), and therefore less configuration variability.
I’d also lose access to the AUR
No, you wouldn’t. Neither on Nix, nor on Fedora Atomic. Especially on Silverblue you layer and containerise a lot, and you can always use the pre-installed and self updating Distrobox to install Arch and use the AUR. That’s also what I do, and it works fine, even though I almost never feel the urge to use it.
It would be the exact same amount of effort you'd use to get new software on other distros. Both Arch and NixOS have very straightforward methods of installing new software that aren't any more difficult than doing so on Debian or some other distro. Both Arch and NixOS support independent package managers like flatpak and snap + they support Appimages.
I'd also add that OP doesn't even need to use NixOS to use nix packages, whereas Arch or Debian would require systems based on those distros. So if anything NixOS tries to make it very easy to add and configure software. Where does all the effort come in?
Nix is kind-of-immutable, and you can always roll back to your old build if necessary.
But Arch on the other hand is notorious to “just break” if you don’t exactly know what you’re doing. Of course it will work perfectly reliable (apart from the few paper cuts you get when using bleeding edge stuff) if you are experienced, and optimally, if you set it up with BTRFS and Snapper/ Timeshift.
But honestly, unpopular opinion, I absolutely see no reason to use Arch today. The only exception is the DIY-aspect, which I totally understand and respect. But, for every other use case, there are better options out there, may it be Tumbleweed or Nix for a rolling release, Arch in Distrobox on Silverblue, whatever. It sounds like way too much effort for what I would get. But each to their own.
It’s kinda sad that Arch has this “unstable” reputation, while it is very solid distro. I’ve been running it on my laptop for a long time and I honestly don’t even remember the last time it broke. Thing literally just works.
It’s yay, which took up ~160 GiB. It was storing previous versions of AUR binaries which I guess added up over time. I posted a screenshot of ncdu outputs for a more detailed breakdown in one of the other reply threads
In the early 90s at the dawn of my programing/sysadmin career. I showed up to my first week of work at “Initech” in dress pants, shirt, and tie. The senior gray beard UNIX sysadmin wore wholey jeans and ratty t-shirts. I don’t recall whether he sat me down and told me, or I figured it out on my own that to be taken seriously in a technical field you must dress down. Brilliant people look disheveled (see Albert Einstein, Steve Wozniak, et al). I ditched the stupid tie & began dressing more comfortably.
Anthropologists call this antagonistic aculturation. Us IT geeks intentionally set our selves apart from the business drones & we had to exercise our privilege of dressing comfortabley while working ungodly hours to solve impossible problems.
Now I’m the gray beard and I’ve mentoed the brighter of the pimple faced youths I’ve hired in the ancient customs of our tribe. Looking back, It seems that IT’s greatest influence on business has not been the increased efficiency of the paperless office, but the casual attire that most office workers now enjoy.
I ended up briefing some very senior leadership…in a hoody.
I brief that specific group on a regular basis and it’s usually fairly laid back but this particular meeting a new, very high profile person was attending to get up to speed. Apparently everyone knew but me because they were suited up and all of the ladies were wearing makeup and had their hair all nice. And there I was, the lead brief, in my hoody and jeans and scruffy beard.
After the meeting I realized that it probably worked in my favor. Some sort of psychological “this guy must be really good because he dgaf about dressing to impress”.
Plus I think their is exactly as you said a stereotype that the better you are at your IT stuff the less put together you have to be.
I’ve already considered Debian, but… I dunno, this isn’t what I’d call the most logical reason, but I just kinda don’t like it as my desktop OS. I’d use Debian over basically anything else for a server, but as a desktop OS I don’t like the vibe.
Keep in mind, I started using Linux this summer and in a few years I’ll probably look back at this wondering why I was such an idiot, but I gotta fall and get a bloody nose first to notice ;3
I’ve already considered Debian, but… I dunno, this isn’t what I’d call the most logical reason, but I just kinda don’t like it as my desktop OS. I’d use Debian over basically anything else for a server, but as a desktop OS I don’t like the vibe.
I was on the same boat as you are, flatpak essentially made it all perfect.
For me, the issue with Debian stable currently isn’t the applications, but the DE. Wayland support and UX gets better with every update of Gnome/KDE, and that isn’t something you can install via flatpak.
My friend, when you install something using the apt package manager you are using a .deb file. It’s something getting downloaded in the background from a server (debian.org or the brave one in this case) without you realising it. Make sense?
My brother in Christ, installing a .deb is downloading the .deb directly, as you would when downloading discord from discord.com, and you use dpkg to install it (apt uses dpkg to install the deb file).
You saying “the deb file” is not the same as “using the official repo”, as dependencies might not have been installed by only using the .deb file.
“apt uses dpkg to install the deb file” Apt is a frontend for dpkg which needs a .deb file to install stuff. Apt searches for deb files in repos listed in sources.list, downloads them and then uses dpkg for installation.
yes, but you missed an essential step of the process: apt handles dependencies for you. maybe not in this case, but installing .debs directly requires installing dependencies manually and it’s not uncommon for people to forget about this and then saying that the program does not work.
installing from an apt repo is always better as long as the repo is trusted (and it should be if you’re installing .debs from it anyway) because it handles dependencies and updates automatically. If you just install the .deb, you’ll have to repeat the process per each update.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.