Why is Java so slow to upgrade and innovate compared to C#? Is it worth it to learn Java when C# just seems tidier? Why is Java years behind and why are they so slow to catch up?
>>106695596Java is older, Java has more stakeholders and it also has a lot of extremely bad design decisions baked in that can't be fixed.
>>106695596Ok, but hear me out, make Name public and you won't need either.
you only seethe because your IDE blows
>>106695609What would it take to fix it?
They're owned by Oracle, notoriously shit rent seeking fuckface corpo that immediately halts innovation the moment they buy a new thing. The one good thing Microsoft did in the 2010's was unleash the C#/.NET team and let them innovate to their heart's content. They also attempted to open source and de-license a lot of things to get more developers on board with it.
>>106695596With this image as my only C# experience, it's an improvement that you can specify getters and setters so easily but it's still pretty stupid that they're something you use.
>>106696479They make more sense once you use them often and find cases where you can make use of the get/set functions beyond blindly returning the underlying object
>>106696425copy Cshart, but they can't. other JVM languages pay some costs to work around the JVM and just spawn a bunch of boxed objects.
>>106696459too bad M$ is still pussyfooting it cuz god forbid they lose out on VS subs.
>>106696421What IDE is that?
>>106695596>so slow to upgrade and innovate compared to C#Laughs in project loom you stupid nigger. This thread is filled with moronic javalets who havent written a single line of code
>>106696421>EclipseI'd rather Jeetbrains
>>106695596Pot calling the Kettle black
>>106695596I don't use any JVM languages but kotlin/scala/groovy probably has a solution
>>106696509But that's all the auto-generated getters and setters do is it not? Why not just make the member variable public at that point?
>>106698105>Laughs in project loomda fuck are you talking about? that shit was over sold, it just works for niche cases, what developers need right now is structured concurrency and is still in beta and has been for years.
>>106698105What is project loom?
>>106698781No, sometimes you want something else to happen when get/set are called, that are uniquely attached to that property. Either modify the value or spin off another method/workflow. As I said once you get deep into it and are writing a lot of code you find out why these fields are useful, it's a convenience thing.
>>106699007You're not understanding what I'm saying. The C# auto-generated getter and setter functions do nothing except getting and setting right? If you want to do something else you need to write the functions yourself. So why even have them?
>>106699404>The C# auto-generated getter and setter functions do nothing except getting and setting right?you can refactor auto properties to have side effects without fucking the ABI compatibility, and if you don't need that... well, your code is just less verbose
>>106695596>empty complaintnocoders should be hanged
>>106699404get and set is for newbiesget and init is for real hackers
>>106695658If you're going to make your getters/setters public then sure, but no one ever does that in practice
>>106695658>>106698781>Why not just make the member variable public at that point?can't have fields in interfaces
>>106695596It's just a bad language full of horrible paradigms and awful standard libraries. It's simply easier to move on to another language than to try and fix this mess.
>>106695596>Why is Java so slow to upgrade and innovate compared to C#?Because they actually give a fuck about compatibility.Why is C# so slow to execute?
>>106699404yes
>>106695596Java was designed for small apps so people could have tools built for their business quickly, but jeety people are using Java to build large games, pseudo operating systems and large scale projects that should really be written in C/C++
