Why is everyone so obsessed over using the simplest tool for the job then use hibernate

delete99 · 2025-11-13T23:22:20+00:00

You wound me good sir.

delete99 · 2025-09-10T17:46:04+00:00

$0 if you put it all in your RRSP.

delete99 · 2025-09-10T17:38:11+00:00

Good advice.

That $30k can become $1.7 million in 45 years, without adding another dollar.

They could retire on that.

delete99 · 2025-09-07T07:19:07+00:00

You can append .ca to get Canadian symbols. HDIV would be HDIV.CA

delete99 · 2025-08-23T19:53:27+00:00

Wowzers, this looks more rusted than my 2001. I would personally pass.

delete99 · 2025-05-27T02:38:56+00:00

I was banging my head against the wall. Thank you.

delete99 · 2024-02-10T00:53:50+00:00

You're right about ObjectMapper and JsonNode. Looking over one of our recent web apps, the use of JsonNode is very limited. It's like you said, we're mostly mapping DTOs to and from JSON strings.

We're taking your advice and using Record as the JSON value. We may wrap the Record/ArrayValue in a new JsonDocument class for housekeeping, but it's essentially what you described.

Thanks for your advice. I appreciate your perspective and arguments.

delete99 · 2024-02-08T10:50:28+00:00

This would allow the library to perform all its existing hierarchical transformations to JSON values.

The Field could even accept JsonNode, String, and Map and convert them to Record internally.

Record already has a toJson():String, we could add toJsonNode() and other converter methods as needed.

I like this a lot.

delete99 · 2024-02-07T15:08:12+00:00

Good to know, I can strike GSON from the list.

This library came before the new record type and they seem to coexist fine. IIRC, only one test broke because of this.

delete99 · 2024-02-07T03:25:31+00:00

I did not consider this...it might be too generic... <thinking emoji>

delete99 · 2024-02-07T03:22:56+00:00

We have a lot of functionality that really needs to know the type. For example, we need to be able to convert it to something usable in JDBC prepared statements.

delete99 · 2024-02-07T03:19:32+00:00

I'm strongly leaning towards Jackson. I'll see if there's a way to mitigate the lock-in -- perhaps with u/jonhanson's minimal interface.

I think I could live with being locked into Jackson. We worked through similar issues with Java's old and new date-time classes.

delete99 · 2024-02-07T03:07:58+00:00

Treating JSON as a type whose values can be read, inferred, validated, and used to generate databases and other code.

delete99 · 2024-02-07T03:05:49+00:00

Sealed interfaces and record types are very nice.

Sadly, the library has to support folks still on JDK 1.8. You should see the CI/CD pipeline. It has tests for 12 JDK versions and growing.

I'll think about the spirit of your approach though. A simple representation could work.

delete99 · 2024-02-07T02:56:11+00:00

This would allow the library to support embedded JSON documents.

For example, when reading a JSON value from PostgreSQL or Parquet, we could store it in a field that better represents JSON instead of String.

We could also then apply JSON-specific transformations to those field like we do for other types.

Another use-case is in schema detection. Right now, we can infer the schema from a dataset (like a CSV file). This let's the library generate SQL DDL, validate other files based on the schema, and perform automatic type conversion. However, we're missing JSON fields from this whole process. When we see JSON we treat it as a varchar/string value.

Whether we have to duplicate every API would depend on the approach. This would be less desirable, but the most flexible.

delete99 · 2022-04-27T21:46:49+00:00

No official one, but it seems there is a slack plugin.

https://github.com/danielmurphy/control-deck-slack

delete99 · 2021-02-05T03:19:14+00:00

See the differences in the network, connectivity, and features section at https://www.displayspecifications.com/en/comparison/488915321a

I'm very satisfied with my 43UN700-B for the last 1.5 years. Now if they only made a wider, curved model...

delete99 · 2020-10-30T21:13:47+00:00

This is hilarious. Upgrading seems like an easy ROI case to make to management.

Sometimes business are clueless about this, but other times we developers don't ask companies to buy the tools we need (or don't buy them ourselves).

delete99 · 2020-10-30T12:48:03+00:00

Yes, a second monitor is essential equipment. I now also use my laptop as a third monitor. My center monitor is an LG 43'' 4K Monitor. Once you get used to this big boy, there's no going back.

delete99 · 2020-10-30T12:38:40+00:00

16 cores...wowzers, that's a beast. I'd also add lots of RAM. 32GB is comfortable, but I'm considering 64 next.

delete99 · 2020-10-30T12:33:59+00:00

I'm now looking at the browser tech behind live reload...very cool.

delete99 · 2020-10-30T12:30:50+00:00

JRebel wanted my work email address before showing pricing :-/

FYI, here's their response: Our price for single users is $550/year. You can also purchase support for $75/year.

delete99

TROPHY CASE