Compiling code converts it from human readable source code into optimized machine code which the processor understands how to execute. For a lot of software you can just unpack the source code, run ./configure, run 'make', and then 'make install'. This can vary a lot and is a simplified explanation, but it's a start...
For-profit prisons and hospitals.
Absolutely not. And they can fuck right off with that whole needing an account to use a terminal thing.
I like it. Everyone these days seems to want web pages that are 5MB of dynamically generated junk.
My little website is just static hugo-generated stuff.
Annnnd that ended any curiosity at all I may have had for it...
Mint is my go-to linux newbie distro suggestion.
Found in a time capsule in 2150: hey guys, we left you a little something over there by Vesuvius...you'll thank us later. And you better not have built a McDonald's on it...
Thumbs up for announcing it's creation so we can pre-emptively block it though.
"States have a right to decide on issues!"
"Not like that though!"
Command line is a lot more powerful for a lot of cases. Most CLI programs are written with the idea that the caller might be another program, so they tend to be easy to chain with pipes and redirection. So you have tons of simple tools that you can combine however you need.
A terminal that uses Electron? Hah, no...not a chance. I'll stick with wezterm.
Nah, I'm good. I'm fine with services being limited to what information they can convince my browser to give them, rather than what they can convince my phone to give them. Or try and convince me to give them permission to access.