Personally, I’m looking forward to native Wayland support for Wine and KDE’s port to Qt 6.
Linux phones are getting closer and closer to usability every day. I don’t care that they’ll always be less polished than iOS or Android, I want a Linux phone.
Linux phones
Will we be able to use messaging apps such as WhatsApp and Signal on Linux phones?
Yes, since you can run Android apps on them. They will be slower and have some quirks though I’m sure.
I’ve been curious about Linux phones. Can you recommended any devices or operating systems to watch? Thanks.
Pinephone has a great active community, and the device itself is dirt cheap (also pretty low-specced). There’s a pro version with a much better specs in theory, but development state is much rougher. Not that the basic model is anywhere near daily driver material yet, but the progress is very appreciable every time i check in.
AMD is planning to release OpenSIL in 2027, which should, in theory, accelerate the development of Coreboot and Libreboot and bring them to modern AMD motherboards
Better tools for graphic design. Maybe a port of the Affinity suite or a big push towards GIMP, Inkscape, and Scribus development. GIMP… I feel like people dreamed for more than a decade for essential photo editor functionalities like CMYK support and non-destructive editing. At least the first one is coming in the next version(partially).
I switched my design workflow to FLOSS tools exclusively. Krita is a perfectly competent photoshop replacement, Inkscape has been developed at a breakneck pace in the past year, the workflow is different, but it’s every bit as good as illustrator, and Scribus is great once you get used to the workflow. If anything, Scribus’ workflow helps you plan and structure your projects better. IMHO FLOSS tools are absolutely ready for professional work, but you cannot expect the workflow to match
existingproprietary tools.If Affinity apps worked natively on Linux I’d ditch Windows for good.
Krita was developed for graphic design specifically. Gimp tackles other simpler use cases
-
bcachefs; I currently use zfs and am not a huge fan of btrfs. Having another filesystem mainlined will be fun.
-
eBPF, particularly if somebody picks up after the presumably abandoned bpfilter.
-
Improved/matured support for rust written drivers. I’m not so fussed about in-tree work, but future third party drivers being written in a safer language would be a nice benefit.
-
long term: the newly introduced accelerator section of the kernel might make SoCs with NPUs and the like have better software support.
-
very hyped for plasma 6, and Cosmic both. I’ve got a lot of confidence in KDE devs, and Cosmic previews look very nice.
-
NixOS has been a really cool distro for a while, but it also looks to have a solid build system from which interesting derivatives will show up.
from which interesting derivatives will show up.
I don’t think that will happen and hope it won’t because NixOS can handle the usual preferences people might have internally.
Don’t like glibc? pkgsMusl is the entire package set but with musl instead of glibc.
Want static compilation? pkgsStatic.
Afraid of systemd? Well okay, we don’t have that right now but I don’t think anyone would be opposed to optional support for worse service managers. It’d just be an opt-in toggle that we could support with enough people interested in it.Nah, people always want to put their own spin on things and I welcome the diversity.
Arch can bring in all the necessary packages yourself, but Garuda exists and people enjoy using it. Horses for courses.
Garuda only exists because the only way to distribute a set of default configuration in regular distros is to create a whole new distro/installer. We don’t have that problem in NixOS because all configuration is declarative and composable.
In the NixOS world, Garuda would be a NixOS base config which users would import in their own config and extend with their own configuration. You’d still be using NixOS though.
If you’re packaging enough changes that somebody would say it’s a different experience, calling it the “X configuration” vs “X distribution” based on how it’s packaged is just splitting hairs.
What’s eBPF?
It’s a technology that lets you run code through the kernel’s JIT compiler. It’s an extremely flexible way to run code in kernel space; the typical example is using it to build XDP programs for networking, which can deeply analyse network packets without having to incur the performance penalty for changing context to userspace.
Just to be sure, what’s wrong with ARC and L2ARC?
My issue is not with the ARC, it’s a few things:
-
kernel integration is iffy; I don’t want to attach a module to my system every time I compile the kernel and prey that the difference in pace between the release schedules of openZFS and Linux hasn’t caused issues, and because of the licencing issues my options of having a distro with zfs built in are very limited.
-
it’s performance isn’t excellent from a NVME standpoint. It’s not terrible, but it could be better.
-
it has a massive code base, making introducing things like performance improvements and new features quite a challenge (Though the openZFS team are doing a bang-up job despite this).
Ultimately if I was still holding on to 40+TB of important data, I’d be using ZFS and be happy about it. I want snapshots on my workstation, without all the strange issues I’ve had with btrfs. I’m sure bcachefs will have its own issues but it’s better to have options.
Sure, I understand the part about having to compile the ZFS module every time alongside the kernel. But that must be some heavy-lifting you’re doing if you’re regularly compiling your own kernel. I’d be interested in what you’re running that requires such efforts.
I don’t understand why you would need NVMe for ARC. Doesn’t it run in RAM only? Isn’t L2ARC what runs on storage devices?
Not really heavy lifting, I’m just running the Xanmod kernel, and need to turn on some features I need for eBPF development. I’m also keeping up to date with kernel releases, so every 6 weeks or so I need to rebuild.
The ARC runs in RAM, but is generally best when it’s given:
- A consistent amount of memory.
- An easily predictable workload.
- Long periods of time between restarts.
Conditions great for a server but not so much for a workstation. I don’t intend for my cache misses to go to spinning rust, so I have 2 2TB NVME drives. SSDs are cheap as chips currently.
The L2ARC is a victim cache of the ARC, and while it is persistent it’s still much more effective for me to just use a NVME drive for my pool.
Just went through Xanmod’s page: the list of features provided seem exciting, although I don’t really know much about some of them. Do you need these features for eBPF development?
Well, you’re right: ARC is best used in a server. What problems did you have with BTRFS that prompted you to switch?
I use Xanmod for gaming (fsync & related tweaks), but need other flags for development on the same machine.
My issues with BTRFS were mainly in their userspace tooling; ZFS volume management is just glorious, it felt like a significant downgrade to use BTRFS.
-
-
HDR and HDMI 2.1 support would be nice.
Some TVs don’t have display ports eh.
And maybe we wanna enjoy 7.1 audio on our fancy ATMOS setups.
IIRC the next few Wayland updates this year will solve and improve a lot of problems.
Looking forward to seeing Cosmic get a alpha/beta release, I love what they’ve shown and since I can never get used to tiling window managers, it looks like a very nice middle ground between DE/WM. And seeing their Virgo laptop, I doubt I’ll get one since EU shipping is a nightmare (Though they’re supposed to open an EU warehouse soon-ish), but more repairable laptops, esp. one using GPLv3 for every bit, is amazing. Looking forward to seeing more about the FW16, not linux per se, but still cool.
Plasma 6, ofc. Way, way in the future (Probably) is seeing more DEs make their way to Wayland, like XFCE/Cinnamon/Budgie
deleted by creator
- At the least Nvidia hardware gets full support for Linux. Which in turn would help me run Wayland on daily bases.
- Ease at implementing secure boot for Linux.
- Torification/I2P being used as standard to use and adapt applications running on linux for internet access.
I2P by default would be a hilarious F U to surveillance
its Nvidias fault not Linux. Bitch to them
Flatpaks seaminglessly supporting all apps plus cli applications and drivers would be the holy grail.
Unfortunatly i don’t think thats gonna happen. Due to how flatpaks work things like drivers wouldn’t work without some serius workorounds.
pop os new de
Easy fractional scaling on sway
KDE Plasma 6 for the resolution of so many issues; COSMIC DE as a brand new choice in the future; Guix System to have KDE and more packages shipped because it’s literally the best designed distro as of now.
Personally, I’m looking forward to native Wayland support for Wine and KDE’s port to Qt 6.
Well, I think a lot of us are in the same boat.
Also, the flatpak development (Im not included in this but a lot of ppl is)
There is more big improvement development for flatpaks?
For me the console API is just horrible. Also idk if it is a packaging problem but a lot of things I tried in the past were a lot bugier than my distro package
