Can’t comment on the Lemur Pro, but the Pulse has an excellent screen. Was wanting more pixels than a 1080p screen but 4K incurs ridiculous cost and tends to be available on “laptops that don’t fit on your lap”. 2880x1800 @ 120 Hz means your fonts look really crisp and updates are smooth.
When my Tuxedo Pulse arrived, I turned it on once to marvel at the fact that it started up straight into Linux. Then restarted it to install Arch btw and never looked back. Fantastic laptop, tho.
I’ve installed both Arch (systemd) and Void (runit) on the same laptop as an experiment to see whether you could have them both coexisting on the same filesystem. (Which you can - main difficulty is keeping their kernel names separate in /boot.) There was very little difference between them in time-to-desktop. Arch was faster, if anything. And I run more services on a desktop than I would on a server.
Choosing init scripts over systemd is fine for philosophical reasons or if you prefer it for maintenance, but speed isn’t an issue. Init scripts are simpler, but systemd goes to great efforts to start things in parallel. Critical servers should be load-balanced and redundant anyway so that you can restart them for updates; whether they take a second longer to start-up doesn’t matter.
HDMI -> DP might be viable, since DP is ‘simpler’.
Supporting HDMI means supporting a whole pile of bullshit, however - lots of handshakes. The ‘HDMI splitters’ that you can get on eg. Alibaba (which also defeat HDCP) are active, powered things, and tend to get a bit expensive for high resolution / refresh.
Steam Machine is already been closely inspected for price. Adding a fifty dollar dongle into the package is probably out of the question, especially a ‘spec non-compliant’ one.
I’m going to guess it would require kernel support, but certainly graphics card driver support. AMD and Intel not so difficult, just patch and recompile; NVIDIA’s binary blob ha ha fat chance. Stick it in a repo somewhere outside of the zone of copyright control, add it to your package manager, boom, done.
I bet it’s not even much code. A struct or two that map the contents of the 2.1 handshake, and an extension to a switch statement that says what to do if it comes down the wire.
Aww, man alive. Most perfect desktop environment I’ve seen in years, and then it’s a full OS rather than just a DE. Had been looking in the ArchWiki for how to install it and everything.
SNAAAAAAAAAAAAAAAAAAKE!!!
Allows the very important ‘overwrite files while they’re open’ functionality used during update. Write all the new files for a service then restart it. No need to reboot the whole machine for that.
Looking at you, Windows, and your bullshit scheduled reboots.
I actually find that starting a ‘raw disk partition’ virtual machine for Windows is one of the best ways to run it. Stops it from fucking up your BIOS and EFI when it does an update. You can restart into it when you want the ‘native GPU’ for games.
Of course, the even better way to stop Windows from fucking up your hardware is to not allow it anywhere near your hardware in the first place…
I have a Tuxedo Pulse 14 gen 3 as my personal laptop, was looking for something with a bit more display resolution than my old 1080p machine, but did not like the price of 4K laptops.
It has been superb for over a year now. Came with Tuxedo’s own Linux, which looked pretty but wasn’t for me. Installed Arch on it, has been rock solid. Is a great machine for coding on, makes a great job of running Dwarf Fortress and less stressful 3D games - Crusader Kings 3 and Disco Elysium run great, for instance. Battery life impressive too.
Been quite robust, too - heard complaints that the lid can get a bit loose but mine’s fine. All the rubber feet have come off the bottom, but that’s probably because I use mine on my lap. They prefer that you install their own fan control app rather than eg. just providing drivers so that you can set it up in CoolerControl, but it works fine.
All in all, good machine. Better than the ThinkBook that it replaced, and those are fine laptops.
I quite liked how the original Linux fix for the Spectre-style speculative execution bug on Intel processors was called “Forcefully Unmap Complete Kernel With Interrupt Trampolines”, but alas, in the interest of diplomacy it was renamed to “Kernel Page Table Isolation” (KPTI) rather than “FUCKWIT”.
Doesn’t feel like it was that long ago, but of course, all search results are dogshit in this new age: https://wccftech.com/intel-kernel-memory-leak-bug-speculative-execution-performance-hit/
Yeah, mine was similar. Had some old Win95 machines from work that were getting thrown away; scavenged as much RAM as possible into one case and left Red Hat Linux downloading overnight on the company modem. Needed two boxes of floppy disks for the installer, and I joined up a 60 MB and an 80MB hard drive using LVM to create the installation drive. It was a surprisingly functional machine - much better at networking than it was as a Win95 computer - but yeah, those days are long gone.
CMake, which is kind of the universal standard build system for C++ now, has “fetch content” since v3.11. Put the URL of a repository (which can be remote, but also local, which is handy) and optionally the branch / commit ID that you’d like, and it will pull it into your build directory automatically. So yeah, you can pull anything nefarious that you’d like. I don’t think most people would question pulling and building a library from Github as part of the build, especially if it had a sensible name for the task at hand.
Kind of. It’s the Linux kernel that manages all of the controller drivers and makes them available to userspace, mostly via the evdev interface. SDL is a library for managing graphics, sounds and events in a generic way on multiple platforms and devices. It’s overwhelmingly the most common library used for Linux games - Steam used it for all of their Linux-native ports of Source engine games, for instance. But it also presents all gamepad events in a consistent way regardless of their “true source”, so generic devices tend to work with every game.
SDL3 mostly clears out all the clutter from the previous versions of SDL. It’s a mature library and gamedev has come a long way in that time. Getting rid of all the weird stuff that the API accumulated makes it easier to use and maintain. Plus there were things like managing audio generally, and pen-and-touch gestures mobile phones and tablets, that were quite the head-scratchers before. That’s all a bit easier now.
Programming a robust global date-time system and having a transparent conversation between metric and *imperial/traditional" units is just a warm-up to show that you can work with the truly demented currency system. Make sure everything is rounded off to the nearest whole ha’penny.
You can only store rational numbers as a ratio of two numbers, and there’s infinitely times more irrational numbers than rational ones - as soon as you took (almost any) root or did (most) trigonometry, then your accurate ratio would count for nothing. Hardcore maths libraries get around this by keeping the “value in progress” as an expression for as long as possible, but working with expressions is exceptionally slow by computer standards - takes quite a long time to keep them in their simplest form whenever you manipulate them.
Assuming you had a pretty decent monitor and graphics output in the 90s, it may have been 800x600, but more likely 640x480, and you’d have been using the standard issue bitmap font with no anti-aliasing, blitted to screen using software rendering. Probably in a single colour, too.
Alas, the problem with that is that it doesn’t scale. On xterm a 4K monitor, I can watch Vim redrawing the screen, paging through logs is painful. Use Kitty for the same, it’s instant, I can flip through tabs and split screens too, and have niceties like anti-aliased fonts and transparency if I want them.
Some people spend a lot of time in the terminal, so I can’t fault them for taking the time to make a nice working environment and sharing that work with others.
I’d probably go with a “kitchen” metaphor here.
The executable for a program is a list of instructions for the CPU to execute. Windows and Linux gaming machines will usually use x64. Most of the instructions are logic eg. how to add numbers together, what comparisons to make, what to copy from one place to another; and they’re exactly the same on both Windows and Linux, you can run them as-is.
Some instructions ask the operating system to do things, like open a file to read. Windows and Linux do these quite differently, but you know how one works then you can change it to the equivalent ask for the other machine. Making the translation takes a moment, but some things are faster on Linux than Windows, so it’s not very easy to generalise as to whether it’ll be faster overall to do certain things. The really important operating system calls for games tend to be messages to pass to the GPU, and the Proton team have put a lot of work into making these as fast as possible.
If you think of it like following a food recipe, then given the ingredients you’d expect that most people would produce exactly the same meal by following it. Most of the steps will be exactly the same for everyone. However, if a step requires a piece of equipment that you don’t have, then it might take longer to follow the recipe if you’ve got to make do with different stuff. Similarly, you might be able to prepare things quicker if you’ve got a whole pile of restaurant-level gear and can do some of the steps differently.
It does just fine for claiming the free games and then otherwise ignoring the Epic store, which is perfection. Think I’ve installed about one out of fifty or so I have available, but the important thing is that Tim doesn’t receive a penny.