Live data from Hacker News

I completed 100 Days of Java over 5 years and mapped the journey as a graph

mohibulsblog.netlify.app

31–36 of 36 posts

Re: I completed 100 Days of Java over 5 years and mapped the journey as a graph

#31
post #26

Earlier quoted context omitted.

2003 called and wants its arguments against Java back. Modern Java can be OOP, functional or procedural where useful. GoF patterns were never enforced by the language.

Does the name of the class inside the file still break the wall and force what the name of the file needs to be?

There is an argument for that being an opinionated part of the Java language, and as i hear it, opinionated programming languages are all the rage.

Fwiw, I like that class names and file names must match. In python codebases I have had annoyances with this when I adopted others work.

Re: I completed 100 Days of Java over 5 years and mapped the journey as a graph

#32
post #26

Earlier quoted context omitted.

2003 called and wants its arguments against Java back. Modern Java can be OOP, functional or procedural where useful. GoF patterns were never enforced by the language.

I'd say GoF patterns were pretty enforced by the language if you include the standard libraries. Or maybe that's even a bit rude to GoF. Some OO patterns - pretty questionable ones - were pushed pretty hard especially in Java EE.

Java EE practically reinvented itself over the last 20 years using the more popular frameworks as inspiration for better or worse.

Even then, you were never forced to use Java EE if you didn't need it.

Re: I completed 100 Days of Java over 5 years and mapped the journey as a graph

#33
post #29
post #26

Earlier quoted context omitted.

2003 called and wants its arguments against Java back. Modern Java can be OOP, functional or procedural where useful. GoF patterns were never enforced by the language.

Unless you write everything from scratch, you are forced to deal with 20 years of bad design. I really wish people would just stop beating this dead horse.

A lot of de Java standard library is actually quite nice to program with. Of course there are less good parts, but Java is committed to compatibility so you can choose between dealing with an old design versus continually refactoring code to the standard of the day. I prefer having a choice.

As far as Java use in companies is an indicator, the horse is still running.

Re: I completed 100 Days of Java over 5 years and mapped the journey as a graph

#34

Takes me back to simpler days when Java was THE language to learn and book like this was interesting. It seems the author took each day in the book as an inspiration for a blog post, which gives it value beyond the book itself.

Well I don't want to come along with you, as while Java might be an ok language, and a great runtime, the cultish Clean Code middle management, and design patterns, with intentionally obscure control flow paths thanks to stuff like dependency injection, and state smeared across dozens of objects (hidden behind interfaces ofc).

Javas biggest engineering upside was that its JIT compiler allowed the runtime to see through this mess and extract decent performance out of 5 layers of dynamic dispatch that shouldn't have been there in the first place.

Add to that the unclear licensing, which meant that there wasn't a single Linux distro that shipped it out of the box, and the development culture it fostered which required 10x the people each spending 10x the time to build features, and single-handedly was responsible for coining the term 'code monkey'.

As for the software - remember Eclipse? I sure do, but I haven't seen it in like half a decade or more, and that certainly doesnt make me sad.

Re: I completed 100 Days of Java over 5 years and mapped the journey as a graph

#35
post #26

Earlier quoted context omitted.

2003 called and wants its arguments against Java back. Modern Java can be OOP, functional or procedural where useful. GoF patterns were never enforced by the language.

I'd say GoF patterns were pretty enforced by the language if you include the standard libraries. Or maybe that's even a bit rude to GoF. Some OO patterns - pretty questionable ones - were pushed pretty hard especially in Java EE.

Java EE is pretty darn retro right now, and it was never core Java

Re: I completed 100 Days of Java over 5 years and mapped the journey as a graph

#36

This website is very confusing.

would love to know how can i improve if you can give some feedback like which part is confusing.

It's very hard to use on mobile. When clicking a graph node, something happens kind of far down in the viewport, which I didn't notice at first. Also clicking "Open post" doesn't seem to work
Post reply on HN