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.

Careful, Spring will eat your lunch...

Originally published .

One of the best NFJS talks that I did not attend but should have was the talk by Venkat Subramaniam titled “OSGI: A Well Kept Secret.” I discovered this talk on my CD a few days ago and started researching OSGi.

OSGi is indeed a well kept secret and appears to be worth looking at. Based on Venkat’s presentation and research I’ve done on my own it looks like OSGi could very well be an answer to creating web enabled appliances. These could be hardware that through JNI and OSGi could expose themselves as services… and it appears that this could be the answer to the class loader woe I had a few months back. Not to mention sounding like it’s a JINI/JMX killer… which seems to me to be the lion’s share of what an Applications server is to most applicaitons.

The big deal here isn’t so much OSGi and how good it is… but that Spring is (from what I see in Venkat’s notes) poised to leverage OSGi in its 2.1 release. And if Spring can offer Hibernate3 and JINI/JMX replacements… and can offer SOA… and can offer all of this in an industry standard way…

… why are we using those big heavy application servers again? Clustering? It seems to me that Spring is getting ready to eat someone’s lunch. Make sure it isn’t yours. Red Hat, I’m looking in JBoss’ direction… do you really think embeddable ejb3 will save you? Is that rye bread?

Explore the map · Browse by topic and date