Decades ago, a collegue of mine (who once worked in hard drive design) said, “Oh, hard drives stopped reading 1’s and 0’s years ago. Now they compute the probability that the data just read was a 1 or a 0.”
Decades ago, a collegue of mine (who once worked in hard drive design) said, “Oh, hard drives stopped reading 1’s and 0’s years ago. Now they compute the probability that the data just read was a 1 or a 0.”
Yeah, for a short time there the word ‘java’ was very ‘in’. Marketing hipsters at the time wanted to use it in everything, just like the word ‘AI’ now.
Big endiant is great for intellisense to quickly browse possibilities, since it groups it all in the same place.
If only someone would train a program… we could call it a Large Language Model… to knowingly group the names together so we wouldn’t have to choose between human-readable format or dB format.
Guess that will never happen because instead we’re stuck using “AI’s” to inflate stock prices instead. /s
I remember seeing a proposed language that would allow each programmer to choose what name to use for each item. Don’t like ‘open_file’? Choose to see it as ‘file_open’ every time you review the file in the future.
While we battle with each other endlessly, we keep forgetting that the computer doesn’t care.
One day, someone’s going to have to debug machine-generated Bash. <shivver>
This was pre-PnP (also pre-JPEG!), so you had to know all the addresses, IRQs, DMA info, etc, of your hardware
Thanks for that flashback. <shiver>
QQ: What’s the difference between a “class-based language” and an “object -based language”?
A: “We really need this super-important and highly-technical job done.”
B: “We could just hire a bunch of highly-technical people to do it.”
A: “No, we would have to hire people and that would cost us millions.”
B: “We could spend billions on untested technology and hope for the best.”
A: “Excellent work B! Charge the government $100M for our excellent idea.”