It's been a long time since I've used a linux live CD but my experience was that it was really slow, and did not persist storage. Maybe that's changed, but having a VM open while able to google errors in your "main/dailydriver" OS is a huge plus to me.
it will depend on hardware on how fast or slow it is. Since, iit's basically loading a filesystem in memory, and then you are running on that while using it. If you barely have enough memory to handle whatever you are using, you will probably see some lagging. For me, it tends to be pretty fast on a system with 16gb or more of memory. 4gb, depending on the distro, and desktop, might be starting to cut things a bit close since everything is getting moved there.
All that said. it not being persistent, and not being, and not dealing with vm's is the exact reason I think it's great for this use case. Since it's a new user wanting to just play around with linux. It's simple to set up, you don't have to worry about ruining anything. And for me it performs better than a vm. Which whatever I do, vm's have always felt laggy and wierd. Maybe if I do hardware passthrough. But that's a lot of set up to just play around with linux. When they can get that by design from just plugging in an iso.
Reproducible builds are not an 'innovation'. For example, F-Droid, which anyone who isn't insane already uses as much as possible instead of Google Play, does that shit.
This is the most Google-retarded shit possible. Here's my favorite part. It's written in Go because Google.. but none of the documentation mentions supporting whatever clusterfuck is Go packaging
Go has had a real problem over the last few years. With malicious packages getting added. It seems like it's happening constantly. And with the way go, and these other languages work, people could be pulling those in accidentally for normal non-malicious programs, that used those libraries before they were altered to contain the malicious code.
Hopefully that's what they are addressing when they are saying "supply chain attacks" because it's a big problem for anything using go, that uses outside libraries.
No matter how much I use Vim, I always confuse J and K when navigating. Then again, I only treat Vim as a CLI text editor for simpler jobs like config editing, I much more prefer GUI editors like Sublime Text for most work. I don't think I'd ever get used to using Vim as a full blown IDE, and that is without trying to turn it into one with those Neovim conversion packs. I want to keep my shit simple.
Where vim really gets good isn't the hjkl movements. Those are nice, and like someone else mentioned they become muscle memory on which way they move, rather than actually remembering. But where you really see the benefits of vim is when you start getting into text objects, and doing things like dap yap diw using the { and } to move around full paragraphs, using f to search forward for a character or F to go backwards then you can use ; to repeat that motion, and one of the biggest things is cntrl+v for visual block.
And the more you learn about it, the faster you get. It starts to really compound how much time you save doing editing work. And if people are spending time in editors for work that really adds up. Something I just learned recently. is when you do visual select more. after you highlight something, you can hit :s/foo/bar then do the normal sed style search and replace, for the instances of foo in the text you selected, and replace them with bar. like you might do for a full buffer using :%s/foo/bar. There are so many things you can do with vim to save time. It's crazy what it can do.
And for development work, if someone takes the time to set up an lsp, like they may be using in another ide. but also know, and can take advantage of all the other time saving things vim has. It's really hard to go back to any other editor, you just won't get the things you can from vim from almost any other editor out there
