austin

joined 1 year ago
MODERATOR OF
 

If you've played around with version catalogs enough, you will inevitably come to a point when you when you want to also use a BOM in your version catalog. Doing that just feels so...clunky? You need to declare the BOM in the libraries section, and then you have to declare each individual dependency from the BOM as a library (without a version). Alternatively, you can just skip using the BOM entirely and declare each dependency without the BOM. In either case it's not a great experience and definitely could use some improvement.

I wrote a Gradle plugin (in Kotlin) to automatically generate a version catalog from a BOM so you only have to specify it once, let me know what you guys think!

[–] austin@programming.dev 1 points 11 months ago (1 children)

If you already know Java, Kotlin for Java Developers is free and created by the Kotlin team.

[–] austin@programming.dev 3 points 1 year ago

I do think there’s a gap between hibernate and jooq that needs filling. I love the ease of querying for relational data with hibernate, along with support for validation annotations. On the flip side I love the jooq dsl, code gen, typed queries, and the flexibility you get from it, but there’s really no easy way to plug in validation annotations and querying for nested relational data requires a lot of effort. Based on a brief look of the docs, it seems like this library intends to fill that exact niche. Interested in checking it out when I get some time

[–] austin@programming.dev 4 points 1 year ago

Much needed change, I wish they made it apply for all go versions though

[–] austin@programming.dev 2 points 1 year ago

The backwards compatibility promises of Go definitely makes upgrading a breeze. Java is pretty much in the same boat (except it maintains bytecode compatibility instead of source). When working with languages that don’t offer these promises it’s always a nightmare to upgrade to newer versions.

[–] austin@programming.dev 1 points 1 year ago

the developers don't have to of left the team to make it legacy code

view more: next ›