Jens Greifenhagen
nixCraft 🐧Terminal forever <3 https://www.commitstrip.com/en/2016/12/22/terminal-forever/? #unix #linux #macos #freebsd
garrytansucks.55 on Signal@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.
Karl Pettersson@hucksternoise @nixCraft 32 KB and 128 MB RAM was probably also more typical for a new computer in 1980 and 2001?
StarkRG@nixCraft
2038: 1901 is gonna be a good year.
2038: 1901 is gonna be a good year.
Ian Chard@flup 1970 would be 0, the 2038 bug is a signed 32-bit integer rollover so it'll become maximally negative.
2106 would be the unsigned 32-bit integer limit, but I'm not sure how much that's used.
@StarkRG of course, silly me. Is this actually what happens on a system with 32-bit time_t?
@flup Without mitigations, I think so, yeah. Most consumer facing stuff is 64-bit these days (laptops, desktops, phones, tablets), but I think embedded systems are dominated by 32-bit processors (actually, I think it's probably still dominated by 16-bit, with 32-bit a close second, the 16-bit systems probably don't handle time, though). You *can* use 64-bit time on a 32-bit system, but it's an added complication that I doubt many will have bothered with.
@StarkRG Yeah, it’s the legacy stuff that’s worrying. The dusty embedded widget that sits in a cupboard running the national grid. And I’ll bet there’s 64-bit hardware out there still running kernels with 32-bit time representation.
@flup And 32-bit programs running on 64-bit systems. Like some manager was told they need to upgrade to 64-bit so they just replace the hardware and OS, but continue running their proprietary 32-bit software. It probably won't be as impactful as Crowdstrike's f-up, but it'll be a lot harder to get what is impacted up and running again.
Oh crap, and what about 32-bit protocols? Like the system that lets airlines rebook passengers on another airline. Sorry, you're 135 years late for your flight.
ElectroFetish
Virginicus@ElectroFetish @nixCraft I recently needed to use an awk script that I wrote 20 years ago. I used to start it up and go to lunch. Now it comes back immediately. If you’re not running a modern GUI, modern hardware is amazing!
The Gym Nerd@nixCraft I see me speaking in shell commands to a all powerful AI in a dystopian future...
S.T. Veje@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.
0x10f/kalle/qalle
Benjamin E.@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 ...
thorsummonerif 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
RejZoR@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.
Ash_Crow
Trit’@TritTriton @nixCraft Why when GUI could have all that crap plainly visible. It's why I hate terminals.
josejuan@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.
markymarrow@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
Claude Lavoie@markymarrow @nixCraft In 1980, I had a 1 KB computer. There was no personal computers with 1 MB at the time. The IBM PC appeared in 1981, offered with 16KB. The Commodore 64 was lunched in 1982, with 64 KB.
Tim Ward ⭐🇪🇺🔶 #FBPE@markymarrow @nixCraft ... and the processor speed was 4.77MHz not 5 MHz, wasn't it?
Martin Uecker@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.
Raphael@uecker @nixCraft To be fair, many CLI programs have _horrible_ UX, especially the ones that have been around for decades.
But, as you say, they never change so copy-pasting from ten-year-old posts usually works out fine.
Shell completion on options/flags is an absolute must, as it adds discoverability to otherwise arcane commands.
Ciencia Al Poder
oceaniceternity@nixCraft typing "dnf update" vs paging through a gui...
h0nza 🌄 🏊🚴the word hell is inside shell 😁. but seriously, there‘s no hacking without a shell
Stuart Longland (VK4MSL)@nixCraft Years a little off methinks…
1980: 1MB would have been loads of RAM. IBM PC XT had 128~640kB in 1983. Maybe closer to 1990 (286+).
2001: you would have been laughed at with 24MB RAM… budget PCs with 256MB were common by then. 16~32MB would have been common circa 1996 or so.
Still… the point is valid… I pretty much live in the CLI. Always have.
SirWumpus 👾🍁@nixCraft Only 1980 was 2.106 MHz and 64 KB of RAM and 8.3 filenames.
AzureArmageddon@nixCraft lol It'll still take longer to launch your AR terminal emulator window than booting into a shell because it's gotta compute the shadows, room anchors, smooth (foveated) fonts, etc.
@nixCraft It just hit me none of these guys full-screen the windows of their terminal emulators...
Bonkers@nixCraft 1MB RAM in 1980? What are you talking about? A few dozen kilobytes was the norm.
Blue Ridge Black Hat
Dan Neuman 🇨🇦@nixCraft I mean, you spent so much time learning all those commands 40 years ago. Why let them go to waste?
Leif SamuelssonOne of the first great inventions was curses, which allowed simple windowing on terminals. I didn't hashtag that, because there are too many witches around. :)
lemgandi@nixCraft Oof. Story of my life.
Killab33z@nixCraft CLI is king ^_^
Dave Wilburn 
Look at Mr. Moneybags here with 1MB of RAM in 1980.
Juankz@nixCraft 1TB of RAM. 999GB used by Chrome.
Rene 🄲🄰🅅🄰🄲 Schickbauer
"Terminal Velocity", a graphics demo running in the Linux Terminal
@nixCraft Yeah, IF you have a good memory, which many users do not. GUIs are great for people with poor to average memories (also for people with little to no typing skills) but for some reason some geeky types think it is okay to make fun of GUI users, just because they presumably have great memories and can remember all those obscure terminal commands and their options (or don't mind spending hours reading and re-reading documentation). #unix #linux #macos #freebsd
Linky~@SeanWelsby @nixCraft I have poor memory, I don't see this as a issue for me. Maybe write yourself a guide or something. Improvise is all am saying
@linkachus17 @nixCraft If it is not a problem for you then you do NOT have a poor memory!
http@SeanWelsby @nixCraft Your argument is weakened by the existence of the apropos command, and that most commands have -h/--help arguments.
Eg. More important than being an expert in writing pcap filters for tshark is knowing that that tools exist to analyze network traffic, and they can be looked for.
Wintermute_BBS@nixCraft full ack!
Jabberwock@nixCraft nothing will beat the Terminal.
Capywarist@nixCraft I don't have a terminal. I have a stream of text represented in the form of `window` over here in Plan9. There's nothing quite like it, not a terminal emulator because it doesn't emulate nothing. Not a terminal because it runs in `rio`, it is the bare command line represented in a window.
Chloé Raccoon@nixCraft @TundraWolf remember when we went from smart people In front of dumb terminals, to dumb people In front of smart terminals...