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.

A nice bit of textbook groovy

Originally published .

Groovy is just so groovy. I’ve been working in Groovy since August of 2007 but I still take such pleasure from little things like this… take some tokens


def tokens = "abc,def foo+bar bar foo"

now break them apart


def parts = tokens.split("[+,\\s]")

now make the array a list…


def list = parts.toList()

now get groovy with the list…


def words = list.unique()

… and check it against test case list …


assert words == ["abc", "def", "foo", "bar"]

… and that just beats the socks off of stuffing the words in a hash then pulling out the keys. Putting it back together I have a single method now:


    static parseTags(String tagTokens) {

     return tagTokens.split("[+,\\s]").toList().unique()

    }

this method will pull apart a string with tagTokens and return a unique list of tags. Inspired by Graeme Rocher’s book “The Definitive Guide to Grails” Listing 9-8. Literally a text book example of why Groovy is so groovy.

Back to our one-liner. I developed the return statement to the method parseTags using a groovy shell script. First, I put groovy in my path by editing my .profile or from the command line…


 $ export PATH=$PATH:/path/to/groovy/bin

Once you have that you can run the script from the command line. The whole script reads… (file name: test.groovy)

#!/usr/bin/env groovy

assert "abc,def foo+bar bar foo".split("[+,\\s]").toList().unique() == ["abc", "def", "foo", "bar"]

println "If this prints then it worked." // otherwise the script will bomb out on the previous line

Notice the #! it works because groovy is in our path. Now from the command line I run…


 $ groovy test.groovy

… if I chmod the test.groovy file executable it will run as a shell script. And that’s just groovy. I can play with code now changing bits and re-running it over and over finding just the line I need. That little shell script is a test. In a Linux system it’s the lightest test environment imaginable.

And this is a big deal because now I can script Java. I can call Java code from OS commands as easily as I call a shell script. It could mean I could write Java-esque scripting admin files to fire-up Java services like GlassFish or JBoss. That could be very groovy.

These little tweaks can make a huge difference.

Explore the map · Browse by topic and date