The ultimate couch laptop will be an M1 MacBook Air as it has no fans and a suped up phone chip so it doesn’t heat. It also has amazing battery life… But it’s still pretty expensive and it cannot be repaired. Otherwise old MacBooks should be pretty good because most of the Intel models used relatively low end chips because their thermal design was so limited
I bought a refurbished dall latitude 7490 for like 270$. For the price it’s a powerful machine, 16gb ram and i7 processor. Installed fedora on it and I’m in love with it. For the price it puts out the power I need for software development.
I have that, never had problems, Bluetooth works as well! At least with the devices that play well with Linux.
You should check out linux-hardware.org too, it has a huge database of hardware probes that can help you know what works exactly from each device, the search page is what you want: linux-hardware.org/?view=search
I bet you money that you statistically use the touch screen keyboard on your phone significantly more than you ever are to your hardware keyboard for your PC.
You would be very very wrong, since I hardly use my phone.
But to your point, a soft keyboard is very different for conversational input that autocorrect and predictive typing excels at, and command entry and scripting where syntax is critical and you aren’t really typing in English or some other language.
What price bracket are you looking at? The two laptops that I normally use in that situation is a used Thinkpad X1 Carbon I got on eBay, and a HP Dev One that works pretty well for that.
The Thinkpad link that was shared below looks pretty nice, they tend to be fairly cheap and easy to get replacement batteries and parts. There’s a lot available in that $150 to $200 bracket on eBay. Edit: I just saw it’s 14", so a bit bigger than what you wanted. You can filter by screen size and price on eBay to give you an idea of what you can get. You may need a new battery depending on the age, so keep that in mind.
Any chance there’s a Debian repo for bcachefs? I’d want to see how it does on an extra drive in my server. Or will I have to compile it the old fashioned way?
For bcache, it is available in apt, I think. You just need to set the ppa. For bcachefs, I think you need to wait for 6.7 to land on Debian or compile it yourself.
Fedora Sericea is my current daily driver. Loving it so far. I’ve used Sway, River, and Hyprland on Arch, Fedora, and NixOS. The combination of an immutable system augmented by flatpaks and distrobox are supporting my goal to never wipe the drive again.
Sway is more stable and lightweight for me than Hyprland. I don’t use Nvidia hardware at all. The lead Dev on Hyprland is a treasure though. 10/10 for that human being.
Yes (kinda), that is a screenshot of one of the example compositors I included called “louvre-views” which implements server side decorations for apps that support the XDG Decoration protocol.
Have you installed a custom ROM on it? If not, you definitely don’t have the skills for this. If so, have you built your own ROM for it? If not, do that so you learn how it works in a predictable environment. Then port something existing to it, like UBPorts. Only after you do all of that and probably a lot more should you attempt to effectively develop your own distro on hostile hardware.
Some of those arguments are legit but like half is complaining about wayland being fundamentally different to xorg and obviously you cannot use straight xorg apps on it.
“Linux is inferior because it breaks all my powershell scripts and all my windows only apps. Don’t use linux.”
I mean, to play devil’s advocate here - if functionality that you need is all of a sudden swept out from under you then it doesn’t matter from an end user perspective if it’s not the intended design for Wayland - to the user, Wayland is broken in that regard.
A better equivalent would be if an application you used every day for the last 10 years all of a sudden has an update that kills features you used because that’s no longer part of the dev(s) vision. Or headphone jacks on phones. Or whatever that weird thing with Teslas where they disabled a sensor in an OTA update and replaced it with some other solution(?).
Or to modify the example you put, if Windows killed the cmd shell and only left powershell in a Windows Update.
I have an application that I need to use at work which will never fit Wayland’s design, short of me either finding a new job, keeping a Windows install around, or using a really old version of Linux around in a VM when X11 has completely disappeared from all distros (which won’t really work) - there will be nothing that I can do about it on the Wayland side because it’s highly unlikely the devs will update it to be compatible (since it’s a shock that they actually even had Linux support in the first place).
As it is, I currently just pop into an X11 session whenever I’m on working hours, it will suck that I can’t do that with Fedora come next release when they completely drop X from the repos.
Most points are just complaining that tools specifically designed for X don’t work on Wayland. That’s like hanging onto your childhood pants and complaining they don’t fit anymore.
But many of those are actively used by people. I use screen recording, screen sharing, global menus, key automation and window automation every day. Even if I wanted to use Wayland I couldn’t. What exactly is it that you want me to do?
And one of the first points is how Wayland crash will bring down all running applications - yep, just like on X11! But it’s somehow Wayland’s fault.
Besides the fact that on Wayland running apps can survive a compositor crash (I think new KDE will have that feature), which I doubt can be done on X11.
A WM crash does not bring down all the other applications… but an X11 server crash definitely does!
In wayland they are the same program (a.k.a. the compositor). User applications can be designed to survive a compositor crash, though many are not able yet
An X session depends on the main user process. Unless a DE picks the compositor as the main process then no, a compositor crash won’t affect the session. But they don’t do that, for obvious reasons, since the compositor is just a feature among others. They typically have a special program that takes that role, for example xfce4-session.
And one of the first points is how Wayland crash will bring down all running applications - yep, just like on X11! But it’s somehow Wayland’s fault.
They said that a Wayland window manager will bring down all apps, not a Wayland crash. Which, again, is not like it works on X, as I explained above. The window manager on X, like the compositor, is just another feature. If it crashes it just gets replaced and the session continues.
That’s a feature, stop buying hardware from vendors that treat GNU/Linux and *BSD users as second-class citizens and locks them into proprietary drivers.
Games are developed for X11. And if you run a game on Wayland, performance is subpar due to things like forced vsync. Only recently, some Wayland implementations (like KDE KWin) let you disable that.
That’s a feature, stop buying hardware from vendors that treat GNU/Linux and *BSD users as second-class citizens and locks them into proprietary drivers.
Nowadays I buy a new graphics card maybe twice a decade. I’m not changing the card for software.
Also, we’re all using proprietary hardware. Be serious. If you tried to never use anything proprietary you’d never use anything. You’re using like a dozen of them right now.
Sure, I have proprietary bits on my kernel and my AMD GPU needs proprietary firmware loaded to work, but that’s a hell lot different than the situation NVIDIA shoves users into. It’s one thing to have small proprietary components that don’t bother me or break my workflow, it’s another to have black box drivers that can bork my setup if I dare to update my packages.
I suppose it explains why people have a bad attitude about Wayland when tools providing useful functionality are described as trojans.
X11 can (…mostly…) have great security by just providing a suitable X Security module to it. It just seems it wasn’t considered that big of an issue that anyone bothered. Nokia Maemo/Meego used to rock such a module.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.