Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lombok makes Java cool again

bytes.grubhub.com

Post reply on HN
Print view View original

191–200 of 239 posts

Re: Lombok makes Java cool again

#191

Post by pjmlp »

zestyping wrote: post #83

Reading this just reminds me of all the terrible things about Java. The lack of reasonable default string representations, comparison and hashing methods, etc. are all glaring mistakes in the language design that have wasted huge amounts of time for millions of programmers. It's as though Java programmers are so deep in the grips of Stockholm Syndrome that ordinary, sensible behaviour seems amazing and "cool". This i…

Java really felt refreshing versus what C++ world was doing before it came out.

Go dig out a book about Boochs, CORBA, DCOM/MTS,...

Re: Lombok makes Java cool again

#193

Post by cs02rm0 »

stickfigure wrote: post #146
philsnow wrote: post #27

Earlier quoted context omitted.

> The downside is that you'll need to install it into your IDE. And again when you upgrade it. I guess the version needs to loosely match the one your projects use too. If you work on a lot of different projects with different versions of Lombok, do you have to have multiple versions of the IDE plugin installed / is that even possible?

Lombok doesn't really change that much/often. I've been using it for a decade on projects of varying ages and never noticed a problem.

Yep, also never had an issue with it in practice.

Re: Lombok makes Java cool again

#194

Post by pjmlp »

int_19h wrote: post #137
hodgesrm wrote: post #100

Earlier quoted context omitted.

Which design patterns are you thinking of and which languages had them? The original gang of four Design Patterns book is filled with C++ examples, most likely because almost nobody was using Java in 1995 outside of a few people at Sun. More generally comparison and hashing methods seem like small potatoes compared to locking primitives, portability, and a large, well-documented class library that have made Java idea…

C++ circa 1995 was a lot more like Java with manual memory management, really. Templates were a rare sight, STL was not yet a thing, and it was still considered an impure OO language rather than multi-paradigm.

STL wasn't a thing, but MFC, OWL and ATL surely.

Re: Lombok makes Java cool again

#195

Post by pjmlp »

stewbrew wrote: post #144
jcrites wrote: post #109

Earlier quoted context omitted.

The remark about design patterns is not accurate. Design patterns did not originate with Java and aren't specific to that language. The classic book "Design Patterns: Elements of Reusable Object-Oriented Software", by the 'Gang of Four', was written in and about C++. It was published in 1994 and predates Java. "Design Patterns", both as a book and a concept, is about the recurring patterns found in object-oriented so…

"about the recurring patterns found in object-oriented software" ... in statically typed languages of that time (like C++ and to some extent Java). At least some patterns solve problems that are not (that kind of) a problem in, e.g., dynamically typed languages.

GoF was written for C++ and Smalltalk developers.

Re: Lombok makes Java cool again

#196

Post by pjmlp »

chooseaname wrote: post #14

Java the language is cool. What the enterprise has done with it is not cool. Writing apps with layer upon layer upon layer upon layer of abstraction is ... self defeating. Then they'll holler, we need to rewrite it! All in the name of finding that one true architecture that can handle any business CR. Blech.

> Java the language is cool. What the enterprise has done with it is not cool

This is a re-occuring pattern.

I have seen it happen with C, C++, TP, Clipper, Java, JavaScript, C#, VB, ...

The enterprise environment is quite "interesting", specially when politcs get intermixed with technology.

Re: Lombok makes Java cool again

#197

Post by pjmlp »

dajohnson89 wrote: post #30
chooseaname wrote: post #14

Java the language is cool. What the enterprise has done with it is not cool. Writing apps with layer upon layer upon layer upon layer of abstraction is ... self defeating. Then they'll holler, we need to rewrite it! All in the name of finding that one true architecture that can handle any business CR. Blech.

How do you feel about Spring? I'm a fan of Java itself as well, but find myself conflicted whenever I use Spring/Boot. It's very nice when it works. But when the magic formula isn't recited correctly....you get frustrated and wind up visiting HN to forget about how unpleasant it is. ahem

I think that it brought a good competition against JEE (back when it was still J2EE), however I would still just use JEE for Java Web projects.

Re: Lombok makes Java cool again

#199

Post by EmpirePhoenix »

jcheng wrote: post #97
Rapzid wrote: post #76

Earlier quoted context omitted.

I would be nice for any language that supported annotations(TypeScript, C#, python, etc) if we could somehow annotate the same code in different files while maintaining a single source of property truth.. A combination of interfaces and class annotations for combining them could work..

I don't know if this is what you mean, but Aspect Oriented Programming was a hot topic for a very short period in the early 2000's, especially in the enterprise Java community. Ultimately it didn't seem to find many use cases and the buzz died down pretty quick. https://en.wikipedia.org/wiki/AspectJ

The hype wave is gone, but if you ever saw @Secured or @Transactional, those are aspects after all.

Re: Lombok makes Java cool again

#200

Post by EmpirePhoenix »

mattnewport wrote: post #102
barrkel wrote: post #94

Earlier quoted context omitted.

Java popularised GC. GC wasn't taken seriously as an option for high performance code before Java, and it altered the mindset of the majority of programmers globally. Java's biggest mistake IMO is checked exceptions. Java is more notable for the things it left out than what it added. It was designed for success and achieved more than most of the languages you list. I don't love Java. However there are many cases in w…

I'd argue that GC still isn't taken seriously as an option for high performance code by people who actually write high performance code and Java is not the language of choice when performance is a primary goal. The lack of value types hurts it there even compared to other similar GC languages like C#.

Tell that to the high-frequency-trader crowd, they almost use java exclusivly, because even 1ms equals a few thousands to them, correctness is apparently worth it for them.
Post reply on HN