Idea: let’s ask Copilot to rewrite that in Rust
Curious, is any mainstream OS running all modern code?
TempleOS?
CTO: why fix something that ain’t broken That’s what interpreted
Hell, it might be the last reliable piece they have left, I’m fine with them not vibe coding that out of the codebase.
the only thing that isnt AI.
Oh boy, wait until you hear about an ancient little sweetheart named COBOL.
And? Maybe there’s a reason that code is still around? Maybe it’s because it’s good code that is solid as a rock?
I have less of a problem with this than the “constant update” model all software companies seem to subscribe to these days. We don’t need new features, we need bug fixes.
Isstill can’t figure out why discord has a new update every other day. I’ve never seen software this needy before.
Well it’s just s different approach in how you deliver updates. Update as you go or save up updates and publish once a month like ms
It’s the forced online login that wercks it. I now suggest linux.
We’d use a lot more windows if it wasnt so locked up in marketing
TCP/IP is from the 80’
That’s a protocol, not a software library
TCP does what it does pretty well, no need for replacing that which works fine
Ehh, TCP has issues with mobile connectivity and is designed around the idea that 1 logical application stream should map to 1 TCP connection, which causes issues.
But that’s why we’ve got QUIC now.
Other than that though, TCP is fine. If all you need is simple in-order delivery of a stream of bytes it’s hard to beat.
And tell me again exactly what the difference is between a protocol and an api, when both are using software that has not been changed for decades? Just curious.
Besides that, TCP/IP is the worst thing ever for a large network and it only gets worse by the day.
thatsbait.meme
Besides that, TCP/IP is the worst thing ever for a large network and it only gets worse by the day.
yet you use it every fucking moment, including to post this message.
wow. damn bro. go back to NetBEUI if you’re so fucking l33t.
If I’m going back I’m choosing OSI kthx
OSI
my brother in layer 3
jfc look in a mirror dumbass. Who gets this angry over internet protocols and then calls the other party fucking l33t?
lol you’re the genius who decided to talk shit about things they obviously do not understand.
Yes I refered to myself as the other party and have a different username. Doublely dumbass.
oh whoops, I got my assholes confused!
Seems like good code then? Old code is stable and bug free and we should keep using the boring stuff as long as possible.
It seems more likely to me that any bugs present in that code just became features that old software relied upon over time, so they can’t change anything without breaking backward compatibility.
So I guess, in a sense, it’s bug-free.
Most mobile devices use ARM processors, a tech developed by Acorn in the early 1980s.
Old doesnt mean bad. If it ain’t broke, don’t fix it
Found the person never having to use Win32.
RISC is the Alpha of the CPU field.
Had a friend in college who was redoing nuclear decay calculations written in Fortran so they’d work as C++/C# libraries. The calculations had been a historical standby for decades, and people were coming up with increasingly elaborate daisy-chains of dependencies to get them to work properly in modern environments.
There’s definitely a point at which the physical hardware and modern network/interfaces need you to catch up your code with the current technology. But there’s also this terror around trying to touch code that’s got an archaic datestamp on it, particularly if you’re working in a language or dealing with a particularly baroque procedure where the guy who wrote it retired 20 years ago.
Old doesnt mean bad.
Unreviewed Code is bad code unless proven otherwise. Maybe that latest iteration really is time tested and bulletproof. Or maybe Microsoft Execs simply won’t allocate time/money to the kind of routine review and maintenance a codebase needs from time to time.
Except it broke
Later additions have broken it, the foundation is still solid.
“I converted my studio into a 3 story mansion and the foundation sunk into the ground. The foundation is still solid, it’s just the 3 story mansion that’s the problem.”
A foundation that can no longer support what it needs to support is not a good foundation and should be replaced
A better analogy would be that the mansion fell down but the foundation is still standing. Because the foundation is the solid part.
ARM was based on 1975’s MOS 6502, star of the NES, Apple ][ and Atari 2600.
It kind of annoys me that ARM is a second order abbreviation. IDK why.
Surely there’s an acronym where the A stands for ARM, which would be sure to annoy you even more.
And c64 :')
…and PET…
30 year old legacy code bolted to vomited out ai slop, what a great combination
Maybe that’s why it’s more critical today. The only part that’s even remotely trustworthy.
What os doesn’t?
Reminds me of the flicker.
Quake, HL, HL2, Portal:
And here’s Half Life 1 and HL: Alyx for good measure:
What does that have to do with anything?
Ancient code being reused in new software is nothing new or specific to Microsoft.
This was very interesting, thank you.
With the way Microslop has been putting out code lately, I don’t think I’d actually want them to try replacing Win32 either.
It works stably and soundly, and I can only imagine any replacement would be riddled with bugs.
I do. More problems with Windows = less market share for Windows.
Well, it does work.
My prediction is Win32 will live on as THE “standard gaming/graphics API” in… linux. Through Wine/Proton.
Really?? Colour me shocked that a company known for its bloated OS still needs stuff from the 90s to work…
At least there is no FORTRAN in Windows or we will all be screwed.
About that…
jk
