this post was submitted on 07 Feb 2024
1591 points (99.3% liked)

Programmer Humor

19809 readers
173 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 195 points 10 months ago (52 children)

Sorry, what's .Net again?

The runtime? You mean .Net, or .Net Core, or .Net Framework? Oh, you mean a web framework in .Net. Was that Asp.Net or AspNetcore?

Remind me why we let the "Can't call it Windows 9" company design our enterprise language?

[–] [email protected] 59 points 10 months ago (28 children)

Can't call it Windows 9

But that actually made sense! They care about backwards compatibility.

For those not in the know: some legacy software checked if the OS name began with "Windows 9" to differentiate between 95 and future versions.

[–] activ8r 8 points 10 months ago (1 children)

It makes sense why they did it, but their messed up versioning was the cause to begin with. You should always assume Devs will cut corners in inappropriate ways.

[–] [email protected] 15 points 10 months ago (1 children)

They'll cut corners the more the shittier APIs and ABIs you provide

[–] [email protected] 3 points 10 months ago* (last edited 10 months ago)

The API is fine. It returns the internal version number (which is 4.0 for Windows 95), not a string. https://learn.microsoft.com/en-us/windows/win32/api/winnt/ns-winnt-osversioninfoexa. There's no built-in API that returns "Windows 95" as a string.

load more comments (26 replies)
load more comments (49 replies)