Live data from Hacker News

Windows 11 will happily execute a binary compiled 30 years ago

twitter.com

251–260 of 424 posts

Re: Windows 11 will happily execute a binary compiled 30 years ago

#251
Ha, the version of ZIP that I use was built in 1996, and I was using a version of 'ls' that I wrote for NT 3.1 -- maybe 1993 or so -- until a couple of years ago.

These programs don't use DLLs, and frankly there's little reason they for them to stop working.

Re: Windows 11 will happily execute a binary compiled 30 years ago

#252

Earlier quoted context omitted.

Use the email no@thankyou.com with any password. It will let you install on Win 11 with a local account.

The developer who put that in needs a raise.

IIRC it's something to do with the account being permanently locked due to too many failed password attempts, so windows basically throws up its hands and lets you log in anyway.

(This is just a vague recollection from last time I installed Windows, might be wrong)

Re: Windows 11 will happily execute a binary compiled 30 years ago

#253

It's not insane, it's my expectation for a tool. My hammer still works perfectly well with nails I bought 30 years ago. It's impossible to build on shifting foundations that are constantly breaking backward compatibility. You eventually spend all your time maintaining instead of creating. Then you have to go reinvent your wheel, and in my experience as a user your shiny new one isn't necessarily better. Most of the s…

Milwaukee still manufactures NiCAD batteries for their tools that have long since been outclassed.

Re: Windows 11 will happily execute a binary compiled 30 years ago

#254
post #4

I wish there was a backwards compatibility option to give applications a “virtual display” which runs in a window, for old programs which only know how to run fullscreen at 1024x768.

This is why I ran a virtual machine for windows even when I was running windows. Virtual machines almost always support having a different virtual resolution vs actual.

Re: Windows 11 will happily execute a binary compiled 30 years ago

#255

Earlier quoted context omitted.

> Right click -> Remove. Done. 2 seconds. Surely you aren't making the argument that Microsoft is generous enough to let you remove their bloatware?

That's a nice strawman you got there, give him a spin so we can admire it in all its glory.

My dude I literally quoted what you said, at least before you edited your comment to remove it.

Re: Windows 11 will happily execute a binary compiled 30 years ago

#256

Does Linux have this backwards compatibility? What about macOS? I know instruction sets changed from PowerPC to Intel to ARM, so probably not macOS at least. But this is a CLI and I doubt old system calls changed

MacOS is actively hostile ( I still remember when they dropped cocoa or carbon or whatever it was, many apps died that day ).

Linux isn’t hostile and if you ONLY use the kernel ABI or statically compile everything, it will work quite a long time.

But if you use dynamic libraries, you gonna have a hard time unless you have source.

Re: Windows 11 will happily execute a binary compiled 30 years ago

#257

Earlier quoted context omitted.

I've only used MacOS for a year and only recently (maybe that matters), and I get all the same crappy inconsistent behaviour I do on Linux and did on Windows ~20 years ago when I last used it. Apple has the benefit of controlling both hw and sw and still manage to mess it up. Random crashes, slowdowns for long running sessions, crappy UI (eg those labels not checking their checkboxes in Settings), network weirdness (…

You haven't used Windows in quite a while have you ? Past Windows 7 it's been sliding downhill into bullshit UX, crapware, backend migration to Linux almost exclusively, etc. Random things on top of my head : MacOS doesn't come with candy crush, Instagram, TikTok, Spotify etc. prepopulating your start menu. Phone home telemetry and ads in OS ? Yummy Dealing with Windows dev environment is always a PITA eventually - u…

> Dealing with Windows dev environment is always a PITA eventually - unless you're doing stuff where Windows is first class citizen (like games). For backend stuff it's almost implicit that you're running on Linux in prod and macos is well supported because it's fairly similar. On Windows it's always some path issues, stuff randomly breaking between updates, missing/incompatible CLI, etc.

YMMV but my experience is the opposite. Windows is a perfectly usable dev environment. The only time I face issues is when developers don’t choose to use cross platform tools.

> Chocolatey is garbage.

I’ll give you this one, but that’s why anyone serious on Windows is using scoop.

Re: Windows 11 will happily execute a binary compiled 30 years ago

#258
post #244
post #148

Earlier quoted context omitted.

It works in Linux the same way it works on Windows: If you don't have the dynamic libraries and configuration you need, it won't work. Why this is a mark against Linux and not Windows is beyond me.

Microsoft keeps maintaining all those libraries, and keeps them in the OS by default. That may not be the case with Linux.

This is exactly it. If you call native windows things, they’re there (ignoring deprivation of win16, etc).

But if you call gnome libraries, they’re probably long gone.

Re: Windows 11 will happily execute a binary compiled 30 years ago

#259
post #220

Earlier quoted context omitted.

That's common in the mainframe world. Unisys (ex Univac) still has its Dorado mainframes binary compatible with the Univac 1100 released in 1962.

I think I remember reading a while back that System/360 binaries can still run on modern Z/architecture mainframes.

Yup, that’s the example I cited above.

Re: Windows 11 will happily execute a binary compiled 30 years ago

#260

Earlier quoted context omitted.

This seems like an interesting vector for a virus.

These older games will all work in 640kb so the fix would likely just have been to fence off 640kb completely from other apps while SimCity was running.

Sim City 2000 used DOS/4GW though: https://en.wikipedia.org/wiki/DOS/4G :

> It allows DOS programs to eliminate the 640 KB conventional memory limit by addressing up to 64 MB of extended memory on Intel 80386 and above machines.

Post reply on HN