Is this primarily for multi-user scenarios or complex setups?
Seeing them play Portal and other video games, I'm curious if they will eventually help solve that last N% of self-driving.
I enjoyed the content nonetheless.
I had been working on it for a couple years, using it myself. I finally released it recently. It heavily uses an embedded Lua VM to power its scripting engine.
https://github.com/mmcdole/lunar
I'm releasing Lunar, a new Lua 5.1 compiler and virtual machine written entirely in Go. It includes the standard libraries, coroutines as well as supporting Lua 5.2-style goto.The embedding API avoids the Lua C API’s stack-based interface in favor of typed Go values and callback frames. Libraries and script-file access are opt-in, so the host explicitly controls what Lua code can access.On my...
I had been working on it for a couple years, using it myself. I finally released it recently. A number of users are contributing feature requests, testing, etc on the discord as well.
But I don’t mind work expenses on my personal card? I get reward benefits for a sizable chunk of expenses that I’m directly reimbursed for?
I don't want this auto-detect agent request. The explicit toggle was perfect.
It had a simple UI with a clear button / key combo to toggle the “agent mode”. That, plus the fact it could “warpify” my SSH connections made this a useful utility.
Then a couple months ago they completely changed the UI. It doesn’t work as it once did. My saved prompt templates didn’t work as they did before, the agent toggle was gone (you can now start some ‘/agent’ command but it is much less intuitive) and they seem to be focusing on these cloud agents and code editing.
I want none of these things. I loved a simple terminal that let me still execute sudo, let me ssh into remote machines but still bring Claude and OpenAI models to interact with my session.
API driven, have "elastic resources", etc, etc. Rather than bolting together various solutions you get to have a "Cloud-like" stack in your own datacenter.
But I’m not sure we can say they the big US companies aren’t doing foundational research anymore. I suspect a lot of it is just kept unpublished as a result of the intense competitive pressure, which is disappointing.
I converted my resume to LaTeX with Claude Code recently. Being able to iterate on this code-form of my document is so much nicer than fighting the formatting with in Word/Google Docs.
I dropped my .tex file into Prism and it makes it nice to instantly render it.
It also perhaps tries to preserve some moat around their product/service.
There are a lot of anecdotal reports of quality differences following some Gemini 2.5 Pro releases earlier in the year.
> There was a Sears-Roebuck, a Gillet, young Sidney Kodak who would one day be Kodak of Kodak, a Houbigant, Buick of Buick, and R. H. Macy XVI, head of the powerful Saks-Gimbel clan.
- The Stars My Destination
His takes often remind me of Jim Cramer’s stock analysis — to the point I’d be willing to bet on the side of a “reverse Gary Marcus”.
(It auto-routed to its thinking model, took 25s)
> Short answer: you can’t. iOS doesn’t ship a public zstd encoder/decoder. The system Compression and AppleArchive frameworks only expose lzfse, lz4, zlib/deflate, and lzma. So with only Apple SDKs, there’s no way to produce zstd-compressed bytes.
> > Two practical paths:
> 1. If zstd isn’t mandatory, use a built-in codec (lzfse or lz4 are fastest) via Compression’s streaming API. Example (pure Swift, no deps) that compresses an arbitrary byte stream: >
> <code example>
> 2. If zstd is mandatory, you must embed zstd yourself. That can mean:
> - Vendoring the official C sources (libzstd) directly into your project and calling them via a tiny Swift wrapper/bridging header
> - Statically linking a prebuilt libzstd.a you compile for iOS