huginn

I'm not sure there's much that is better or worse than Jackson. When I worked exclusively in Java I was always using GSON and did not remember having so many hoops to jump through. Could just be my bad memory though.

I just feel like when I'm doing Java work I spend 90% of my time on useless boilerplate.

Corporate standards.

I'm pushing for no half measures: it's Kotlin or bust.

140k is the stat used in the article this post linked

I'm normally working in Kotlin when coding because I do Android development. I've had the misfortune of taking up some slack in a greenfield backend project and holy God is it miserable.

Everything is harder to read, every basic data model is 200 lines of getters and setters, multithreading is painful, basic transformers require separate class declarations. And that doesn't even touch on the horrific experience of using Jackson to handle json serialization.

140k/yr USD is still well within the class of people who care. Basically every doctor in America falls into that category.

Not really.

Android apps can declare which urls they accept as deep links. Once that is registered with the system (ie after install) then links of that type can be opened by the app. It doesn't have to match the package name.

Counterintuitive but very interesting. Thanks for the explanation!

Compression and encodings are not my forte at all: why is 10bit color more efficient to encode than 8?

Niche communities don't deal with spam.

But the moment it's big enough Lemmy will be rife with spammers and you'll need full time moderation tools.

It's a distinction only legally.

At 49% ownership and being 100x the value of Open AI that is effectively the same as full control. Open AI cannot blink without Microsoft getting right of first refusal.

49% ownership means they dictate what Open AI does. Don't kid yourself.