This keeps the new caching layer simple and take advantage of the existing caching. If they went any bigger they'd likely need to rearchitect parts of the keymap or underlying storage layer to accommodate, or else face unpredictable TCO.

Unclear what kind of quality you'll get out of it, but since the tokens are all local, kinda doesn't matter if it burns through 10x more for the same outcome.

[0]:https://www.docker.com/blog/clawdbot-docker-model-runner-pri...

Very much the LLM equivalent of “to bake an apple pie you must first invent the universe”.

To its credit, it did a great job.

1) It chews through tokens. If you're on a metered API plan I would avoid it. I've spent $300+ on this just in the last 2 days, doing what I perceived to be fairly basic tasks.

2) It's terrifying. No directory sandboxing, etc. On one hand, it's cool that this thing can modify anything on my machine that I can. On the other, it's terrifying that it can modify anything on my machine that I can.

That said, some really nice things that make this "click":

1) Dynamic skill creation is awesome.

2) Having the ability to schedule recurring and one-time tasks makes it terribly convenient.

3) Persistent agents with remote messaging makes it really feel like an assistant.

Two desktops, two AI workstations, two laptops, and a handheld. Even my wife is running Linux.

My personal phone and work laptop are the last holdouts.

(IMO it's not for many use cases, and to the extent it is I'm happy to see things like AtomVM start to address it.)

I'm just happy I can use Elixir + Zig for NIFs.

trust me.

I suppose it depends on which battle you’re choosing to fight.

When I enter such orgs, I join to fix the org. And I want every tool at my disposal to do it.

I love turnarounds. But they require careful management of energy. So if I have an opportunity to convince someone to change a name now, it saves me a bunch of energy later.

FWIW, I learned this while getting both React and Clojure approved for internal use at a Fortune 100 co. Took me weeks. Both had problematic licensing issues, both of which could have been avoided if the authors had spent 10 extra minutes clarifying a few small things a few years before.

While not a yet an ROI-positive takeover, on an incredible valuation growth trajectory from the post-acquisition low. Likely to be positive the minute xAI meaningfully monetizes Grok. [1]

Gains strategic access to global training data, and real-time human sentiment. [2]

Incredible built-in distribution for new AI-powered products. [3]

Literally tipped the scales in an election, a role typically reserved for traditional media companies. [4]

Yes, a total failure of a business. /s

[0]:https://x.com/Austen/status/1887363437518270757

[1]:https://techcrunch.com/2025/04/12/the-xai-x-merger-is-a-good...

[2]:https://www.reuters.com/technology/elon-musk-says-xai-will-u...

[3]:https://digiday.com/marketing/with-600-million-users-xs-lind...

[4]:https://techcrunch.com/2024/02/07/x-formerly-twitter-becomes...

Names have incredible power, positive or negative, when something is in its infancy.

At the start, when it's just you, and maybe one other person, and maybe one more than that... and your entire effort is just a wisp of what it could one day be, all it takes is some random fly-by-night architect (or even project manager) walking by, hearing the name, and saying, "No way am I letting something called jank touch this project," and shutting it down. The ol' swoop-and-poop, but for incredibly understandable reasons: corporate drones are superstitious.

Now... if, as a matter of culture building, you're intentionally leaning into the "jank" name, that's different. Because names have incredible power. So if you're cobbling together a cadre of crack hackers, "jank" might be exactly what you need to telegraph exactly the ethos you want to manifest.

But if you're just looking for a memorable name to slap on something you hope will actually get traction in any production capacity, I'd just ask that Jeaye consider if the potential benefits outweigh the risks.

[0]: https://www.linkedin.com/pulse/building-cloud-choosing-lisp-...

But for the love of... please pick a different name.

Whatever reasons companies/teams will have for not letting someone use Jank at work, don't let the name be one of them.