Gregory's Server
 22 comments
 If you rate a processor's speed as max clock × core count, then AMD is selling 509GHz Threadripper CPUs. 🤷♂️ @argv_minus_one @nixCraft Recently I heard Sequent used to sell computers with gobs of 386's in the '90s. Amazing!   @nixCraft 'haha writing text to get resuts is lame' ... And also 'look at this prompt I used for midjourney to draw a cat' CLI has always been the future of computing :p @nixCraft Both command line and GUIs are great, as well as keyboard commands. Everything has it's purpose and use what you can to do things better. @LanguageMan1 @nixCraft Yes. On macOS I‘m constantly switching between Finder and Terminal depending on what fits the task better. @LanguageMan1 @nixCraft Also, you can drag-and-drop a Finder window’s title icon into a Terminal session to paste its path there or one or more files’ Finder entries to paste their full location with path, readily escaped for the shell if necessary. I’d like to know if these features are still coming from the NeXT / OpenStep roots of the operating system.   @nixCraft I see me speaking in shell commands to a all powerful AI in a dystopian future... @nixCraft Didn't we hit 1GHz around 2001? I remember it being a big party. Everyone* were completely blown away by it. * Me and my one friend. @nixCraft je me souviens que nous avions des prototypes de processeur à 70 GHz vers 2005, mais c'était trop dangereux de les commercialiser, le craquage de mot de passe tout ça ... if rhel would have cost 4 Trillion USD to build, how much would it cost to make every function have a GUI. Make it make sense  @nixCraft I'm the opposite of this and a fiery critic of terminal everything. If you're system admin, fine, but for users, fuck that shit. It has been over 30 years and I've gone through BASIC, MS-DOS, Windows CMD, Windows Terminal and Linux Terminal and I just hate it more and more every time I have to use it because you can't memorize all the shit and you need to look online for every command. So stupid. @nixCraft For a lambda user, witch just want doing things directly, of course, GUI is probably the best choice. The learning curve is not the same. @nixCraft, it may be soon, but by around 2040, we'll probably use voice (or subvocal speech, some kind of Neuralink, etc.) to issue commands through a large language model (LLM) agent. Essentially, it will still be the same command line interface, but with a much faster 'typing' interface, and our commands will be at a higher level of abstraction. Teaching the agent to perform specific tasks will be done by experts, much like how they currently write commands or snippets. @nixCraft 1980 for me was a lot closer to 1Mhz/1Kb where did they get all that ram from? Even Bill Gates didn’t need more than 640K  For me it greatly depends on how much I care about what I'm doing. If I don't care too much, I prefer GUI. If I care, I prefer CLI. @nixCraft It is because the command line is stable and does not change all the time. GUIs also generally lack consistency and modularity. It could be different in theory. i don't know why GUIs arre so bad and need to be change all time. |
@nixCraft akshually 🤓 clock speed has hit a wall, and if you want 1TB of RAM, just get a decommissioned supercomputer node's rack! They are quite commodity-like nowadays.