- Drew Belloc ( @drew_belloc@programming.dev ) 73•1 year ago
It’s time to show off my java hello world with 7 errors on line 34
- elvith ( @elvith@feddit.de ) 13•1 year ago
I don’t know what I did wrong, but the bug must be somewhere in
HelloWorldExampleClassForTutorialBuilderFactory.HelloWorldExampleClassForTutorialBuilderFactory(StringBuilderFactory myHelloWorldExampleClassForTutorialStringBuilder, int numberOfTimesToDisplayHelloWorld)
- pwndave ( @deadly4u@lemmy.ca ) 9•1 year ago
That’s really interesting. Maybe it’s like @nxtsuda@lemmy.world said. For a lot of folks, OOP was the way we learned and operated for years
Could they have just asked it differently? Or do they just have Java hate.
- Nechesh ( @Nechesh@beehaw.org ) 1•1 year ago
If all I knew about java was some of the garbage projects I’ve inherited over the years I might hate it too.
- flashgnash ( @flashgnash@lemm.ee ) 8•1 year ago
Man if I were in the US I’d apply for that job in a heartbeat, looks like that was written by a head dev who actually knows what he’s talking about rather than some recruiter
- Sanchokan ( @Sanchokan@kbin.social ) 4•1 year ago
Ool about it. Where does the java hate come from?
- serinus ( @serinus@midwest.social ) 27•1 year ago
OOP is fine. It’s particularly Java culture that’s terrible.
I never want to see the word Factory in a class name ever again.
When a Java dev writes in any other language, you can tell. Too many layers of abstraction is a key indicator. They make simple problems complex.
I once inherited a C# website project from a Java dev. I couldn’t even figure out how to modify the CSS. And I’m a C# dev.
- magic_lobster_party ( @magic_lobster_party@kbin.social ) 16•1 year ago
Factories can be good in moderation. If you make factories for every class, maybe you need to rethink your practices.
- kboy101222 ( @kboy101222@lemm.ee ) 3•1 year ago
I was part of a fun era at my university where they switched from C++, which is what I took in intro to programming, to java. So by the time I was doing some group projects senior year, I was working in C# with people who had only done Java.
They wanted to abstract everything. Everything had to be a class. Any time they repeated 2 lines of code it got put into a helper class.
We ran into an issue where the code just would not run no matter how hard we tried and of course no one on the project but me bothered to use git (they would literally send me the zipped up project on discord and I had to copy and paste everything into the actual code). I ended up rewriting the entire project overnight. It actually wasn’t that bad once I got into the flow of things. Turns out none of them knew how to program without being explicitly told how.
Still not the worst college group project though. Maybe top 5.
- lasagna ( @lasagna@programming.dev ) 3•1 year ago
In most programming I have done, we treat the users as the dumb mofos. In Java, the programmers are treated as the dumb mofos. As a dumb mofo, I have a great dislike toward Java’s standard development ecosystems.
- nayhel89 ( @nayhel89@lemmy.sdf.org ) English2•1 year ago
The horror of the single inheritance that forces you to use composition instead.
The boredom of knowledge which exception every method throws.
The narrowness of generics that don’t allow duck typing.
The oppression of monads and pattern matching.
The poverty of a central package repository and only 2 package managers.
The pressure of choice between dozens of garbage collectors for different workloads.
The promiscuity of the single platform that interconnects various programming languages and allows all of them to use features like state-of-the-art profile-guided optimizations.The horrible world of Java.
What about the Cortex M processor? For homeoffice?