Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead

Smallest-to-largest weight downloads. Qwen3.5 0.8B is our starting choice for page Q&A. GPU estimates are not total RAM: leave room for the browser, context and temporary buffers. Hardware changes speed and capacity; answers still need checking.

Session-only loading avoids saving model weights, uses extra RAM and downloads again after unloading. Turn it off to save downloads. Delete-data-on-exit or private browsing may impose a much smaller storage limit than the displayed estimate.

You sign in on OpenRouter; it gives this page a key for your account.

A free account does not make every model free. Choose a model with a listed :free variant; merely adding that suffix does not create one. Check free-model availability and pricing.

Chat

AI assistant, not Shawn Hartsock. It does not speak for him.

Inspect the page excerpt

Up to 4,800 characters, not the whole site. Recent conversation turns are retained within the model’s context limit.

Ask about this page, or just say hello.

Ready when you are.

Not saved or uploaded automatically. Closing keeps this conversation in this tab; changing pages starts a new one. Model replies can be wrong.

Grails in a J2EE world Part "zero" in GroovyMag

Originally published .

I’ve been very busy this year. I’ve been working with J2EE a lot lately. Normally you wouldn’t necessarily be proud of working in J2EE but I’m also learning about a unique and thriving industry in my region. Namely the biotech and pharmaceutical industry which was very successfully colonized by J2EE earlier in this decade.

The result is that I’ve been working with ways to integrate Grails applications with J2EE applications. The techniques I’ve come up with aren’t limited to just the integration of Grails and J2EE but I felt the title Grails in a J2EE world would probably help address the concerns that I’ve heard from developers working at large institutions such as banks, hospitals, and pharmaceutical companies like myself.

These companies who live in worlds dominated by J2EE can’t just walk away from their investment. For people who live in worlds like that but want to add powerful new features found in Grails I’ve decided to write up a series of articles for publication in GroovyMag.

The techniques I’ll discuss are applicable to far more than just J2EE and Grails integration, check it out.

Explore the map · Browse by topic and date