Skip to main content

Seriously uncool Java?

A couple of podcasts I have listened to recently have flamed Java. It is a good "kusitolppa", a seriously uncool technology.  I'm pleased about not having to write Java anymore. Yet, I'll risk career suicide and take a stance to defend it against some of the low blows. After all, it was my bread and butter for quite many years.

I get it; writing Java is not in fashion. It is likely a wrong choice for a modern startup. The language is full of mysterious cargo-cultish traditions, is verbose, has annotations on top of annotations and you have to use an editor which eats half of your memory (the other half is used by the Java process you are working on). Traditional Java and JDKs are ill-fitted for short-running processes like lambdas; it needs time to warm to get up to speed and needs more than one core to work efficiently. It has horrible dependency management tools by today's standards. Running a JVM process requires all kinds of weird flags, its defaults are unlikely suitable for any given project.

An often pointed out defect in the old-school Java frameworks is their excessive use of threads. Granted, the traditional, solid but inefficient, thread-per-request model has been pervasive for too long. It's funny why, since the standard library has had the fork-join work-stealing type thread pool in for a decade. You are supposed to use that, preferably through a library or a framework, and never create threads yourself.

Speaking of frameworks, It's not trivial to figure out what is a good JVM framework. The de facto choice is Spring Boot or something expensive from RedHat. I would steer clear of those enterprisey frameworks and pick something like Micronaut or Quarkus. They have a fast startup speed,  don't need massive thread pools (non-blocking IO), and use code generation rather than runtime reflection. I won't even try to do or link any study on their performance compared to other frameworks from other languages since it is notoriously tricky, but I'm sure they are in the triple-A class.

GraalVM's ahead-of-time compilation can speed up startup and reduce the docker image sizes. The new CG's, ZGC and Shenandoah, have finally enabled massive heaps with low latency stop-the-world pauses. Since JDK 8, tiered JIT allows complex, heterogenous codebases to run fast after a warmup period. If a warmup time is not an option, Quarkus with Graal AOT compiled native image should do the trick.

I could go on about how slow and somehow uncomfortable Jest feels compared to plain old JUnit, and what a mess I see when I want to check the TypeScript definitions from the editor compared to the dull but very readable JavaDoc. I love writing TypeScript in VSCode, but I do spend a lot of time resolving all kinds of weird double import errors. IDEA was laggy and slow to start, but it did a lot of coding for me.

My conclusion here is that I would not personally start a new Java project and certainly would not build a startup with Java, but at the same time, I should not discard the JVM ecosystem so blatantly. If I were to choose the JVM, It's a no-brainer to use something like Kotlin or Clojure to get the best of both worlds, a solid runtime, and an expressive programming language.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...
Post a Comment
Read more

Canyon Precede:ON 7

I bought or technically leased a Canyon Precede:ON 7 (2022) electric bike last fall. This post is about my experiences with it after riding for about 2000 km this winter. The season was a bit colder than usual, and we had more snow than in years, so I properly put the bike through its paces. I've been cycling for almost 20 years. I've never owned a car nor used public transport regularly. I pedal all distances below 30km in all seasons. Besides commuting, I've mountain biked and raced BMX, and I still actively ride my road bike during the spring and summer months. I've owned a handful of bikes and kept them until their frames failed. Buying new bikes or gear has not been a major part of my hobby, and frankly, I'm quite sceptical about the benefits of updating bikes or gear frequently. I've never owned an E-bike before, but I've rented one a couple of times. The bike arrived in a hilariously large box. I suppose there's no need to worry about damage durin...
Post a Comment
Read more

Emit structured Postgres data change events with wal2json

A common thing I see in an enterprise system is that when an end-user does some action, say add a user, the underlying web of subsystems adds the user to multiple databases in separate transactions. Each of these transactions may happen in varying order and, even worse, can fail, leaving the system in an inconsistent state. A better way could be to write the user data to some main database and then other subsystems like search indexes, pull/push the data to other interested parties, thus eliminating the need for multiple end-user originating boundary transactions. That's the theory part; how about a technical solution. The idea of this post came from the koodia pinnan alla podcast about event-driven systems and CDC . One of the discussion topics in the show is emitting events from Postgres transaction logs.  I built an utterly simple change emitter and reader using Postgres with the wal2json transaction decoding plugin and a custom go event parser. I'll stick to the boring ...
Post a Comment
Read more