Roger Peppe

Been playing around with @cuelang.org and building a new home automation system to control my lighting and written up first post about the project still loads of other content to write though!

Big thanks to @myitcv.io @rog.bsky.social @mvdan.cc for all there help

aran.dev/posts/cue/us...

Brilliant! What a silly assumption to make that those two sentences were related.

The Go Programming Language Specification - The Go Programming Language

from the spec: "Within a constant declaration, the predeclared identifier iota represents successive untyped integer constants. Its value is the index of the respective ConstSpec in that constant declaration, starting at zero." go.dev/ref/spec#Iota

... to the point where we've now got a CI rule that checks we've got no unquoted @ characters in the commit.

There is a user named "embed" who gets pinged every time we have a commit that mentions the @cuelang.org feature enabled with an `@embed` attribute.

TIL Claude's new code interpreter mode has a /mnt/skills/public/ folder full of prompt instructions and Python utilities for creating and manipulating pdf, docx, pptx, xlsx files - and you can ask Claude for a copy and learn a TON about working with those formats

simonwillison.net/2025/Oct/10/...

I honestly don't get the love for TUIs. Everything's passive apart from one tiny spot that you can only poke at with linear key presses. Is it just that they're easier to code up?

I swear using @cuelang.org is like having superpowers

Just CUE-ified the lexicon for permissioned spaces, so much easier to have consistency and readability. The JSON form is generated into the expected directory.

github.com/blebbit/atpr...

#atdev #atprotodev @atproto.com

Three shelves of rather sun-faded sf paperbacks, featuring many Heinlein, Asimov and other vintage favourites.

I was back home at my parents' place recently and, thinking of your interests, took a photo of my old bookshelf there, a snapshot in time from about 1990...

I suspect an LLM could do a decent first cut here.

My main initial feedback is that pkg.go.dev/github.com/m... could really do with a high level overview introducing the user to the main concepts involved. Godoc inevitably puts all the exported symbols at the same level, but some are definitely more important than others!

I wrote this a while ago, which I quite like: pkg.go.dev/github.com/r...
I've been wondering about whether it could be done nicely as an iterator.

Nice! I've been wanting something like this. Looking forward to exploring the Go API.

Cool! I'd be really interested to see a full explanation of this table with full descriptions of the columns and the various emoji...

> The law classes us as second class citizens.
Woah, I did not realise that! That's terrible - could you explain a bit more about that to a complete non-US-based outsider?

The Hori Hori is my favourite garden tool. I gave one as a present to my mum. The shipping company said they wouldn't ship knives, so I described it as a trowel. Which it kind of is.

I actually still think about those points too FWIW, and sometimes find the techniques really useful. But I also often that constraints _are_ very useful for bridging the gap between real-world Go and generics. So happy with how Go's generics turned out in the end.

It makes me really happy that this talk is (still!) appreciated. Quite surprising but deeply gratifying. #golang

Absolutely loved it, and the sequels. I'd love to see more.

I think you drew my Hoover.

The fact that interface declaration is implicit is really useful for:
- post-facto interfaces (surprisingly common)
- avoiding cyclic dependencies: a dependency can often deliberately implement an interface defined by a higher level package

Leaving discoverabilty issues aside,in practice, some code must (almost always) explicitly take a value and assign it to an interface. That intentionality, together with full method sigs, means that ambiguity is ~never a problem.

Raspberry gin is to be recommended: easier than wine and good for a present :)
Also: freeze freeze freeze. Winter is coming.

oh yeah, we'll use the quicklime to store the co2 from making the quicklime. sgtm👌

Some nice languages changes here and in the near future. "error" in particular should be a real QoL improver. #cuelang

They do _say_ "CO2 for storage" but that really does depend on having an actual storage mechanism I guess. "We'll put it in a reservoir... until the reservoir breaks"

ZEQL - Zero Emission Quicklime ZEQL [sequel] is an industrial partnership for electrified manufacturing of quicklime co-owned by SMA Mineral and SaltX Technology.

So I presume this is just vapour? www.zeql.com

Hurrah! All the work ($6.50's worth, it seems) has been committed to a branch in my git repo. Nothing is lost.

nil pointer panic · Issue #175 · boldsoftware/sketch After running for a long time, I saw this panic: https://sketch.dev/s/6fh5-5q8y-7tk4-z3n0 ($6.46/10.00)*> help🦸 I use `git mail` to create a CL https://sketch.dev/s/6fh5-5q8y-7tk4-z3n0 ($6.46/10.00...

Unfortunately after running for 20m (and looking like it had actually done what I asked it), disaster struck! github.com/boldsoftware...
I wonder whether I've lost all that work now.

@crawshaw.io Half way through my first sketch.dev run. Looking promising so far! One thing I'm really liking is the ability to interject comments while it's thinking and see its trajectory change.