Even though the kernel module is open-source (sort of, development still happens behind closed doors), it's still an out-of-tree module, rather than being built into the kernel, which would give you as smooth an experience as with AMD or Intel, who's GPUs literally do just work on any distro with no fuss.
It’s never gonna be a smooth experience with Linux on Macs, because of installation, but also firmware upgrades etc. there’s always some manual steps involved and nothing will change unless Apple itself starts supporting Linux natively
> Conversion of legacy nontrivial C++ code bases into Rust (or anything else for that matter) feels like it should be one of the "Millenium problems" for AGI.
Whilst I have no doubt that LLMs will be useful here, I still have reservations about validation. I think experience tells us that test coverage is generally insufficient to ensure functional equivalence, and not all components are well specified.
It was all the rage towards getting 4K 120 Hz VRR on Linux before AMD came along to contribute proper HDMI 2.1 support to the kernel. There is also mention in that thread of a CableMatters adapter that could be flashed with an alternate firmware but it wasn't as stable.
Is there a better way to get started with Emacs than the built in tutorial? I've tried a couple times (due to increasing annoyance with VS Code), but have struggled to get to a point where I feel productive enough.
I recommend the tutorial (Help -> Tutorial) from the menu bar inside Emacs to get you started. Don't listen to people telling you to disable this or that. Use your mouse and arrow keys to get started. Don't worry about what other people are doing with their Emacs too much. Pick one thing you want to do with Emacs and focus purely on that (writing Go, taking notes in Org, etc.) and avoid a wholesale move unless you have infinite time and patience.
It's no different from learning vim. Just stick with it until the shortcuts become cognitively automatic.
It also helps to learn upfront the idiosyncratic terms and concepts like buffers, windows, frames, yanking, killing, etc.
Most of these terms map one-to-one to more familiar nomenclature like copy, paste, etc.
Buffers is a concept a bit more unique and integral to emacs. It's easier to understand in practice than in reading.
Most importantly though, emacs is a lisp machine, and exposes the highest level of granularity, and enables the finest level of customization for the user.
I'm in the minority and think the tutorial is awful. "Here's this software everyone says is so great. Before you can actually use it, be sure to spend 20 minutes doing a bunch of stuff for which you don't have context/don't have motivation for"
No thanks.
Instead, literally just start using it and ask an LLM for help as you go.
An LLM is great at writing a first shot at key bindings to suit your taste, and recipes for Emacs' four syntactically different yet functionally overlapping configuration schemes.
The maybe complementary, or at least deterministic source of advice is old school 'M-x info'.
And that's the really fun part of all this, that weak substitutes will also become more expensive. But on the bright side, I've got dozens of sticks of DDR3 RAM that I'm hoarding like Pokémon cards. Any day now, we'll get desperate enough to start using them again!
reply