C# should actually be "What Java said, except it's ICrackable".
this post was submitted on 14 Mar 2024
3 points (100.0% liked)
Programmer Humor
18971 readers
1035 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
No, actually C#'s answer should be: "What Java said - hold on, what Python said sounds good too, and C++'s stuff is pretty cool too - let's go with all of the above."
C#, or as I like to call it "the Borg of programming languages".
I got my first software developer role last year and it was the first time I’d written C#, I was more TypeScript. Now we use both but I must say I really like C# now that I’m used to it.
I think most programmers would like C# if they spent time with it. It is getting a bit complex because the joke about it over borrowing from other languages is on the money. It is a nice language though and pretty damn fast these days all things considered.
C can STRUCTurise classes tho
Yeah, you can technically write object oriented code in C. Or any other language. Just that actual OOP languages provide a nicer syntax and compile time checks.
Rust is kind of a good example of this. It's technically not an object oriented language, but the trait system brings it close.
Time for Rust++
I want my vs code to look like this
But, why?
most C programs are just C++ programs with extra steps if you look at them close enough
Rust is more like: unless you can mathematically prove to me that this is equivalent to a nut there is no ducking way I'll ever let you compiled this.
And then still segfault
https://github.com/Speykious/cve-rs/blob/main/src/segfault.rs
If you can make safe Rust segfault you're doing something wrong.
IME Rust programs crash at about the same rate as other languages. "Rewrite everything in Rust" hasn't made much of a difference for me, so far.
Rust programmers vastly overestimate how many bugs are caused by memory problems
Yeah. The verdict is still out on whether having a deeply surly compiler will help me focus on iterating and understanding the client's needs.
I run Python CICD controls on main with at least the same level of prissiness (as Rust comes with), but at least Python knows how to shut up and let me prototype.
I'm currently not convinced that Rust's opinionated design hits a useable long term sweet spot.
But I think if Rust adds a debug flag --fuck-off-i-need-to-try-something, it could genuinely become the next Python, and the world would be better for it.
Edit: And if I just missed the --fuck-off-i-need-to-try-something Rust flag, someone point me at it, and I'll gladly give Rust another run.
Once you get the hang of rust you don't ever need to ask it to do unsafe things. It's not really any faster to do things unsafe
It's not really any faster to do things unsafe
Yeah. Which is how I roll with Python now, as a Python Zen master. But Python was a little charmer when I was learning it to replace my Perl scripts.
In contrast, Rust would not shut up the last time I was trying to do an unsafe local bubble sort, just to get to know it. What I got to know was that I was working with a language that was going to go out of it's way to get in my, each time way I wanted to do something it didn't like.
Rust was easily the worst first date with a programming language I have had in a long time, and I can code in both varieties of 'Pikachu'.
Again, it's just my first impression, not the last word on the language. But I have enough tools in my belt that I didn't need to add Rust.
I'll try that 'unsafe' flag next time, and we will see if it can sort my local music files by artist name without having a security fit.
Edit: Responses here have convinced me not to give Rust another shot. Reeks of the Java community. If that's what's happening here, the Java devs can have this one to themselves. They'll probably fill it with XML again. I didn't want to like Rust anyway. And everyone needs to get off my lawn.
You're missing the point. Tools are different. Trying to learn and use rust by writing unsafe bubble sort is pointless. Use it to actually accomplish something and you'll find out just how amazing it is.
Using the ecosystem that exists to be productive and not have to think at all about whether what you're doing is correct is the point. It catches the subtle errors for you and lets you use the powerful libraries like clap for command line parsing, tokio, etc.
StackOverflow: Question closed as duplicate. Someone else already asked whether or not something is a nut.
"Question closed as duplicate"
The question it's a duplicate of: "How to programmatically prove a hotdog is a sandwich?"
In Java, it's not called the Crackable interface.
It's the Nuttable interface.
Provided your method specifies a strongly bound type you can ensure that you get your nut.
void dischargeNut(T extends Nut) { ... }
strongly bound you say?
I just dabbled in javascript again, and that description is spot on!
console.log('javascript operators are b' + 'a' + + 'a' + 'a');
The only reason people use JS is because it's the defacto language of browsers. As a language it's dogshit filled with all kinds of unpleasant traps.
Here is a fun one I discovered the other day:
new Date('2022-10-9').toUTCString() === 'Sat, 08 Oct 2022 23:00:00 GMT'
new Date('2022-10-09').toUTCString() === 'Sun, 09 Oct 2022 00:00:00 GMT'
So padding a day of the month with a 0 or not changes the result by 1 hour. Every browser does the same so I assume this is a legacy thing. It's supposed to be padded but any sane language would throw an exception if it was malformed. Not JavaScript.
I can‘t believe you’ve done this