Fedora 42 Beta
redhat.com
redhat.com
Notably with FEX support for running x86 binaries. https://fedoraproject.org/wiki/Changes/FEX
Both MacBook Pros and Airs are nice machines, but macOS, for me, it's a huge step back.
Unfortunately the Asahi project is underfunded (likely one of the reasons the project founder/lead jumped ship recently), and as a result M4 support is likely a year+ away.
Oh wells, let's see what Dell and Lenovo have on offer this spring/summer. Should be able to get a pretty decent PC laptop for less than the $4k+ an MBP 16" with 2TB/64GB will cost.
Going to dive into the details now, thanks...
It's only been a week but thus far it has worked very nicely and I think ended up running me around $1,500.
We see what the future brings, but for now, seems a very solid purchase.
(Edit: as someone mentioned below, the speakers are not very good at all. This was not super important to me. If it is super important to you, you'll be let down)
I bought one. It lasted less than a year. One day I pulled it out to use it and it just stopped booting. It had been barely used up to that point. No drops or anything like that.
Support was giving me the runaround, too -- by not using info I provided them, not answering direct questions, and asking me to provide info I had already provided.
Do some research on Framework support. You'll find it is atrocious.
The idea is absolutely amazing and I hope it succeeds. The expansion cards are an AMAZING feature. The problem is that the quality bar just isn't being met, yet.
[1]: https://arstechnica.com/gadgets/2023/05/review-framework-lap...
It's just a bad laptop: has "hot bag" syndrome, speakers are terrible even with the upgraded kit, the hinge that turns the screen off is very temperamental.
Still no open BIOS, they've hired a “Linux guy” who is super condescending in their official forums and locks topics when he feels the heat.
Stay far away.
https://www.lenovo.com/us/en/p/laptops/thinkpad/thinkpadp/le...
Great keyboard and touchpad and nice display.
In fact, it's even better than Linux as a VM desktop host - finally a reliable suspend on lid close, smooth graphics in VMs, easy context switching between VMs, no silly fiddling with virgl and GPU passthrough etc. It Just Works. I can even play almost all the Windows games I care about - and at totally acceptable frame rates despite x86/ARM translation layers and lack of discrete GPU.
The only issue with that is that the boot chain is not verified, and you are not protected against evil maid attack.
https://docs.fedoraproject.org/en-US/workstation-working-gro...
Most of my dev work is in a Ubuntu distrobox and I use mostly Flatpaks for everything else.
If I had to use Ubuntu I would fight to use Debian instead.
It's rock solid AND comes with relatively new packages, AND they are close to stock. I also appreciate their willingness to put themselves forward and show leadership when it comes to adopting (or creating) new technologies that can make the platform better. I think most professionals can agree at this point that despite little qualms and some early hiccups here and there, technologies like systemd and wayland (and others) were probably good ideas in the long run, and Fedora was consistently way out ahead in promoting and adopting them.
I also tend to trust Red Hat (and yes even IBM) more than I do Canonical for a number of reasons.
You're probably trying to write fairly and without throwing shade, but the result is this gives off vibes of FUD. Can you be a bit more specific about your issues with Canonical?
All I'll say is that the recruitment process alone, if it's still as bad as it used to be, is a major red flag and deal breaker w.r.t what it says about the overall culture.
Maybe things have changed and so people should really take my opinions about them with a grain of salt.
Example application: https://canonical.com/careers/4676649/application
> How did you perform in mathematics at high school?
Predefined answers are "Top 0.01% in the region", "Top 5% at school", "Top 10% at school", etc.
> Please share your rationale or evidence for the high school performance selections above. Make reference to provincial, state or nation-wide scoring systems, rankings, or recognition awards, or to competitive or selective college entrance results such as SAT or ACT scores, JAMB, matriculation results, IB results etc. We recognise every system is different but we will ask you to justify your selections above.
These are required questions. Even if I were literally in high school, I'm not sure how I would be able to answer these. "Make reference to provincial, state or nation-wide scoring systems, rankings" - do these exist in the US? If they do I've never heard of them.
They name a couple, SAT and ACT are still the main ones. Some states like New York have the Regents Exam which would be a statewide score. Demanding those scores is still just about the dumbest fucking thing I've seen a tech company do.
I cannot possibly tell you how my UK school ranked in the 90s, how I ranked in any subject at the school, and especially how I would have ranked regionally.
This seems like such an insane thing to even know, let alone ask.
I applied for an EM role in May 2020, crickets for NINE months, then they invited me to begin the process in Feb 2021. Of course I had signed up elsewhere long before that.
Yep, hiring is hard, but how you treat applicants says everything about your culture.
Also few years ago a kernel update made a laptop that was 7 years old non-functional. Eventually I had to install Debian as lack of security updates for the kernel was very problematic.
It's not really a separate distro, more like a different configuration. The regular atomic release is the "base image" with the universal blue stuff overlayed on top. You can rebase to or from a universal blue image and a stock atomic one.
It's much easier than having to try and gather packages from RPMFusion.
- A strong focus on security, one of the few distributions to use SELinux. They were very active in pushing verified boot. Early adoption of Flatpak, which has seen better and better sandboxing over time.
- Very fresh. So you get the latest & greatest GNOME, etc. and even after a release a lot of packages are actively maintained and updated. I have generally found that this leads to a more stable system, since bugs get fixed more quickly.
- Since Fedora is very up-to-date, hardware support is also very good.
- Their immutable/atomic distributions (e.g. Silverblue) are awesome. Immutable boot, atomic upgrades/rollbacks, etc.
I formatted ext4 with LUKS because it's what I'm used to, but honestly Fedora has been great. Add flathub, a few gnome extensions (same ones I'd use in Ubuntu) and it's basically the same experience.
Without knowing what you're migrating I can't really speak to that. I use a pretty light toolset and heavily lean on remote dev (VS Code SSH extension).
Other than that, you'll just be using dnf instead of apt. Articles/answers for RHEL usually work on Fedora. You should really feel right at home.
It's also worth having a look at Fedora Silverblue or Kinoite (or universal blue, which is newer than what I've used). Installing packages at a system level is more involved (they really want you to use Flatpak and containers), but it is possible. I had a CI server spitting out my system image weekly at one point. If NixOS didn't exist I would be using this.
I don't have much respect for Ubuntu. They did a lot for bringing Linux on the desktop from zero, but I feel as though it's being held back by Ubuntu these days (especially with snaps). At least consider Debian instead.
Ubuntu became a huge clusterfuck
I keep my home directory organized and backed up on my NAS, so for me reinstalling is straightforward. Also I use Flatpaks whenever possible, so reinstall them is just looking at ~/.var/app and reinstalling what is there.
Other files to back up might be custom /etc confs, and maybe lists of packages you need (dpkg -l or rpm -qa are your friends).
I also use Linux brew for some more up to date software (e.g. golang) and just brew list is your command to get what you have installed.
In general, keep a backup of your home folder (I suggest skipping backing up ~/.cache to save some time and space) and you are mostly good to go.
- Many apps store their config and user data outside of the home dir. I always find it dishonest when people say backing up home is enough on Linux. You did say "mostly ready to go", but that's exactly the tricky and important part that most people pretend doesn't exist
E.g. Docker volumes are in /var/lib/docker
So /etc/... and /var/lib are generally worth checking as well, but that probably still doesn't cover everything, as not all apps behave as maybe XDG specifies.
Also I have included backing up /etc confs in my original post.
I agree on the brew list being incomplete, totally forgot about casks. Not even sure if they work correctly under Linux to be honest. I literally just use brew for golang and awscli :P
`docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main`
Then "open-webui" will be in `/var/lib/docker/volumes/open-webui/`.
Sure you can change it, but what I mean is that a lot of software by itself, or by you following documentation, puts data that you usually want to back up outside of your home.
FYI they now build WSL tarballs!
https://dl.fedoraproject.org/pub/alt/stage/42_Beta-1.4/Conta...
Really excited that the KDE version is ascended from spin to Edition! That's what I use for my desktop at home.
I've been running Fedora for 20 years and I still can't navigate that part of the install process. The combination of partitions and LLVM - which I don't need - and that part of the install setup... ooof. And try to reuse anything already on disk? I never can get it.
Thank God upgrades are seamless now so I don't have to use the installer.
BTW it's just the disk layout part I have a problem with. Everything else is great.
I tried COSMIC and was disappointed that it didn't work well on a touchscreen (a common refrain for Linux environments, and a motivator for me trying it out). Then again, it's still an alpha. Would be nice to see improvements there, but since it's from a laptop vendor, I don't have high expectations.
Definitely still in alpha.
I like the idea that it will be a bit more secure, automatically. Security needs to be taken much more seriously. Fedora Atomic means most userspace apps will be sandboxed via Flatpak, and the base system itself will be immutable.
Flatpak needs a lot more love, though. Portals aren't as good as Android or iOS or Windows capability-based permissions yet. Many important apps just request full permissions, needlessly.
Slack screen share is kind of hit and miss as well. Not to mention screen capture being less than ideal.
https://taoofmac.com/space/notes/2025/01/05/1730#h-264-strea... (these packages have already been mainlined, I think)
Still, after one nasty experience in 2023, we always wait six to eight weeks after a new Fedora version is released before starring to attempt one of those upgrades. This has worked spectaculary well for us. We get all the benefits of newer mainline kernel drivers for recent server motherboard chipsets and CPUs while maintaining a very solid OS. CVEs seldom even get close to us, since they are often based on much older versions of system packages.
Our scale isn't ginormous. Fewer than two dozen microservices and we sometimes fudge the 'microservice' definition somewhat to allow some of those services (such as pure lookups) to host their isolated tables in the same database schemas/instances. We always mock external web service calls in the test env since a Fedora update either will or will not screw up the ability to hit an endpoint via HTTP (has never happened) -- in other words, hitting a real, live service would add nothing to the results of the dev test outcomes.
Edit: we use Makefiles, not because we are writing code in C (we are not) but because our tech culture is very familiar with using 'make' to orchestrate polyglot language builds and deployments.
> CentOS Stream defines Enterprise Linux.
> CentOS Stream is derived from Fedora Linux. It has a new major version release every three years, and each release is maintained for five years, matching the full support phase of RHEL. CentOS Stream development is open to all, but because CentOS Stream only has updates intended for RHEL, it is maintained by the RHEL team.
I'm Debian user for 15+ years. But stable version is too old and testing for some reasons breaking quite often (last year I wasted more time on fixing Debian Testing after updates than my friend which uses Arch -_-). Now I'm looking for good alternatives and I think I will stick with containers rabbit hole. :)
Thanks @jcastro [3] and contributers for fantastic work! <3
[1]: https://projectbluefin.io/ [2]: https://fedoraproject.org/atomic-desktops/silverblue/ [3]: https://news.ycombinator.com/item?id=38992292
One of the very few things I remember from that year, and yet I remember it in such detail. I'm really not sure how to feel about that.
(but yeah, I've been rocking fedora full time since fc16 or so and haven't looked back, it's amazing)
(and have been running fedora ever since...)
How times have changed, even OS installers.
Why not in XFS?
Happy there's been no signs enshittification of Fedora from Redhat, it's a just a clean polished well maintain modern distro, great option if you're a dev switching from Windows.
That's like naming your programming language "JIT", or "Compiler" or..."Hack".
UPDATE: as others have pointed out, I've got it backwards. RedHat had the name first. So, criticism retracted and redirected at the other Anaconda.
https://github.com/rhinstaller/anaconda/commit/785d44bf73ccc...
This kinda implies that Anaconda was in existence for some time back then & what was tracked in the newflangled change tracking software was the fancy new graphical UI. :)
I have not really looked further if perhaps the backend was imported later on or just grew from the GUI - but the same codebase, with continous 27 years of history is what installs the Fedora 42 Beta today. :-)
> So the Anaconda code base that we all started with began in 1999 or so
which implies that the pre-vcs history is pretty short.
But you're totally right, they obviously should have been more prescient and named it something else.
https://en.wikipedia.org/wiki/CMU_Common_Lisp#History
Certainly the Python trademark is sketchy.