877
Source: so old it's lost
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Oct 2023
877 points (90.7% liked)
Programmer Humor
32380 readers
1361 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
You can definitely tell how old it is because both Rust and 3D printed guns have gotten way better.
And TypeScript is just the JavaScript sword, but with a cheap leather hilt.
And C# now can be taken off the donkey and mounted on a penguin and works rather well.
Now i can't get that picture out of my head. Its amphibious too!
It's a heavy duty hilt that's easily detachable by a small recessed switch labeled “any”.
(It does its job very well as long as you don't opt out of using it)
Except the tool you use to build the hilt in the first place has 100 permutations of settings, and most of them kill you on the spot.
I'll take .tsconfig and .webpackrc over C#
.configfiles every day of the week.because it makes it (type)safe to use..!
Also C# (or should I say the .net framework) is now cross platform, which wasn't really the case when I first saw this meme.
This joke made sense when instead of .net you could only use Mono with C# on other platforms, which wasn't very good at the time.
Yes, especially when you're running linux, and the project you started on windows that uses serial ports suddenly doesn't work any more and you wonder why.
Hint: The events for serial data received didn't fire under mono, for reasons.
I hosted my personal site using Mono over 10 years ago now and it mostly worked well. I contributed some code to Mono to fix a few edge cases where their behaviour deviated slightly from Microsoft's.
Of course, I couldn't actually look at Microsoft's shared source code when doing that, so I had to just observe its outputs. At the time, Mono code had to all be clean-room implementations, since Microsoft's shared source program, where they released parts of the .NET Framework 4.x source code publicly, had a very restrictive license that didn't permit reuse (it wasn't open-source). Even just looking at the code meant you couldn't contribute to Mono.
I was very happy when .NET Core was announced and switched to a beta of 1.0 as soon as I could.
Mostly right. Microsoft showed off how .NET 1.0 worked on FreeBSD but it was absolutely pointless since they didn't provide commercial licenses to run it on anything else but Windows until .NET Core.
And Python's migration to 3.x is more or less complete. Took a while (15 years since 3.0), but it's to the point where migration is not a common topic of conversation.
Perhaps a paper hilt. It'll trick some people into thinking it's safer but as soon as you begin using it you realise it still has all the same problems as before.
I don't know, man. I migrated one of my libraries and found 3 bugs just from that. It's prevented a number of other bugs and issues too.