• 2 Posts
  • 58 Comments
Joined 1 year ago
cake
Cake day: June 28th, 2023

help-circle





  • Maybe I’m just lazy, I’ve only invested 10-15 hours total into my config.

    Once I got it working, I’ve never bothered to really even touch it. (I probably should, it’s most likely months of out of date…just like my NixOS config…)

    Next time I make changes will probably be when I update to 0.10 for inlay hints and set that up along with attempting to fix that error message that randomly pops up every time I start Neovim.

    Also probably not the typical Neovim config experience, but I’ve configured it enough to get of my way, now I just want to write code.



  • AI’s not bad, it just doesn’t save me time. For quick, simple things, I can do it myself faster than the AI. For more big, complex tasks, I find myself rigorously checking the AI’s code to make sure no new bugs or vulnerabilities are introduced. Instead of reviewing that code, I’d rather just write it myself and have the confidence that there are no glaring issues. Beyond more intelligent autocomplete, I don’t really have much of a need for AI when I program.









  • Well, think microkernels as the bare minimum. They give you just enough to write your own OS on top of that: only the bare essentials run in kernel space, whilst everything else runs in user space and has to communicate with the kernel. Compare this to a monolithic kernel, like the Linux kernel: here, the whole operating system is run in kernel space, which means that data doesn’t need to be moved between user and kernel space: this makes the OS faster, but at the cost of modularity. Redox doesn’t use the Linux kernel, it uses its own microkernel written in Rust.

    Edit: A good example would be driver. In a microkernel, these run separately from the kernel and interact with it when needed. In a monolithic kernel, these drivers would be included in the kernel itself. They both have their pros and cons: if you’re interested, feel free to look it up.