Greentext

4379 readers

1381 users here now

This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.

Be warned:

Anon is often crazy.
Anon is often depressed.
Anon frequently shares thoughts that are immature, offensive, or incomprehensible.

If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.

founded 1 year ago

MODERATORS

[email protected]

763

Anon tries programming in Java (lemmy.world)

submitted 1 day ago by [email protected] to c/[email protected]

236 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 28 points 1 day ago (4 children)

C# masterrace and I'm tired of pretending it's not

[–] [email protected] 4 points 21 hours ago

After close to two decades of programming, C# is still the best language I've used. While some of the newer features seem a bit weird, I'd say it's one of the few languages that has never got in the way and has just let me write code that made sense. Even with all the improvements Java has made over the years it's still nowhere near as good as what C# was like maybe 15 years ago.

The same goes for everyone's other "fav" language, Python. Ruby has been a better beginner scripting language than Python for many years, and while Rails is definitely a ghetto, as a language Ruby is great at teaching great programming fundamentals.

[–] [email protected] 5 points 1 day ago (1 children)

C# is pretty good generally - I know it far better than any other and it pays my bills! - but it certainly has its weak points. Particularly around the newer features, a lot of them feel really rushed and just kind of shitty.

The one I hate the most is the whole “nullable” pattern. It’s a total mess. Having to mark up files as #nullable enable, having to mark methods with a bunch of attributes, and the way that it works differently if it’s a value type or a reference type, it’s just so half-baked.

If you spend some time with a more modern language like Rust or Swift then you’ll quickly start to notice C#’s weaknesses.

[–] [email protected] 1 points 19 hours ago (1 children)

I feel like you're doing something wrong with the nullables... I'm pretty sure you don't need to mark up files, you can just enable it on the whole project? I'm not sure about the attributes, you might have a point there, but it just makes sense for value vs reference types IMO, since value types are already implicitly different in terms of nullability.

But yeah, I can imagine it's half-baked, since nullable reference types (that's the name, previously reference types were just nullable by default with no extra features) are a more recent addition to the language, one that wasn't built with them in mind.

[–] [email protected] 1 points 14 hours ago

If you create a new project from scratch, yes, you can enable it project-wide. If you have a project which has a bunch of code predates nullable reference types, and you enable it project wide, you’ll have a billion warnings about it. Also, they’re warnings and not errors by default, which just encourages developers to either ignore or suppress them.

So the reality is that you need to remember when you’re making new classes to add the attribute, and then deal with external stuff - which isn’t always clearly marked whether it’s nullable or not unless it’s using attributes, by the way… just such a total mess.

They should have just gone with something more like Rust’s “Option” type. Would have been clearer for codebases that have to deal with a mix. They also could have clearly and decisively deprecated non-nullable reference types and just told people they were going to remove support in some future version so we could all migrate to them properly like we’ve done for .NET Core/.NET 5+.

[–] [email protected] 6 points 1 day ago

C# has had string interpolation for, what - nearly a decade, now? It arrived with C# v6, which was released in 2015.

Meanwhile Java just pulled their implementation out of the latest beta earlier this year because they couldn’t get it to work right.

Don’t know about you, but I think that Java is largely resting on its laurels as of late. That the only real reason to go for it is it’s third-party library system, and not much more.

[–] [email protected] -1 points 15 hours ago* (last edited 15 hours ago)

C# is nicer Java, but I think it's still fundamentally a poor language.

Rust master race:

fn main() {
    println!("Hello world!");
}

Unfortunately, the time you save typing you'll spend compiling, so there's that...