Glad I’ve never used it.
Always eat your greens!
Glad I’ve never used it.
You must be a bot, you don’t understand the semantics. Ironic, and blocked.
The point is that it actually can be vetted.
Absolutely.
And yet, this AI expert stated that we don’t know why the AI designed the chip in specific ways. There’s a difference between understanding the rough mechanism for something, and understanding why something happened.
Imagine hiring an engineer to design something, they hand you a finished design; they cannot explain what it is, how they actually designed it, how it works, or why they made the specific choices they did.
I never made the false equivalency you claimed I did, and you also never addressed my second criticism, which is telling.
Nope, we actually have entire fields of study that focus on the brain and cognition with thousands of experts and decades of research and experimentation to effectively understand a ton about how our brains work and why we behave the way we do.
Plus, your brain is not created and owned entirely by trillion dollar megacorps with the primary incentive to use it to increase profitability.
“We are coming up with structures that are complex and look randomly shaped, and when connected with circuits, they create previously unachievable performance. Humans cannot really understand them, but they can work better.”
Great, so we will eventually have black box chips running black box algorithms for corporations where every aspect of the tech is proprietary and hidden from view with zero significant oversight by actual people…
The true cyber-dystopia.
history | grep command you’re searching for
That will return all commands you’ve typed that contain that keyword. Helps if you remember part of a command, but can’t remember the specific flags or the proper format.
If there are common commands that you use over and over, turn them into a Bash script and name the script something descriptive.
I do that for long commands that I don’t want to type out, like my whole system update workflow: sudo apt update -y && sudo apt upgrade -y && sudo flatpak update -y
I saved that as a Bash script and called it “update.sh” then I saved it in my home directory. Now whenever I want to do a full system update, I just type ./update.sh and it asks me for my password, then updates my whole system without me having to do anything else. I do this with several different tasks like my remote Ansible server updates.
Other than that, you can buy/make a linux command cheat sheet with the most common commands. Keep it with you or next to your computer. Look at it whenever you need a refresh.
I’ve really been enjoying Fish on my personal laptop.
Immutable distros are great for applications where you want uniformity for users and protections against users who are a little too curious for their own good.
SteamOS is a perfect use case. You don’t want users easily running scripts on their Steam Decks to install god knows what and potentially wreck their systems, then come to Valve looking for a fix.
Immutable distros solve that issue. Patches and updates for the OS roll out onto effectively identical systems, and if something does break, the update will fail instead of the system. So users will still have a fully functional Steam Deck.
If you’re not very technical, or you aren’t a power user and packaged apps like Flatpaks are available for all your software, then go for it. I prefer to tinker under the hood with my computers, but I also understand and except the risk that creates.
Immutable distros are a valuable part of a larger, vibrant Linux ecosystem IMO.