Normally you don't want to format automatically generated code, you adjust the code generator instead.

The text on all pages looks very much LLM-generated, and I think all "user comments" there are fake too. (Edit: I mean "what people said" sections.)

I like the idea of the site, but not the execution.

It feels weird to read "nostalgic recollections" that pretend to be human, while in reality come from gen AI.

those are there for the placeholder purposes, I am currently removing and substuting them with real user feedbacks, thank you for the feedback, thank you for taking time to share it.

It is obviously AI-generated, lots of filler text that communicates nothing of substance. Disappointed to see this on the front page, what a waste of reader's time.

> the garbage collection disaster

Isn't it normal for the initial commit to be large?

A little larger, a lot of the time, though I like a small initial commit better. Though just a little larger. Not so large that it is too large to show on a GitHub page. That means not using version control properly.

Usually when someone decides to share code with the world, they don't want to publish the actual development history. They publish the first version that is ready to go public as the first commit. With enough functionality etc.

> Not so large that it is too large to show on a GitHub page.

Maybe not applicable in this case, but Github has a ridiculously low threshold for when it starts hiding diffs. Probably a limitation of their new React frontend.

I have a similar experience, I learned English much later than my first programming languages, and picking up some keywords and basic APIs was never an issue (it was BASIC and C/C++ at the time). Maybe I would occasionally look up in a dictionary what is 'needle' and 'haystack' in a code snippet, and I was puzzled by the ubiquitous "foo, bar, baz", which to my relief turned out to be equally cryptic for the native speakers. I still don't feel about code as a kind of English prose, it occupies a separate part of my brain, compared to the natural languages.

Scala and Kotlin have 'tailrec' annotation/modifier, though not as sophisticated as you describe.

You mention it was 8 years ago, at that point a typical Java dev would be already using Spring Boot for requests and deserializing JSON to POJOs (with Jackson under the hood).

I get your point, but the natural numbers do not form a ring or field.

Sorry you're right. I was tired commenting.

S/naturals/rationals/g for rings

and s/naturals/algebraic numbers/g for fields

It looks like a parody of LLM delusion, but the PR is oddly specific to be just trolling, and the author also submitted his work to HN: https://news.ycombinator.com/item?id=45982416

oof.

I am doing backend in Kotlin, but I must admit that Java has been catching up quickly, and it seems like Kotlin has been shifting its focus to Kotlin Multiplatform. Modern Java is a good, pleasant language and a safer bet.

Gradle with Kotlin DSL is nice, what's annoying is Gradle's constant API reshuffling for the sake of it that breaks plugins. Some plugins also introduce pointless breaking changes just to have a fancier DSL.

The IDE support is not an issue in practice, in my opinion, because IDEA is the best IDE for both Java and Kotlin. The official Kotlin LSP was released 6 months ago, but I haven't tried it.