//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
Profile
Loading...
CUE, Go, fiddler, climber, gardener, curry maker.
Roger Peppe
Loading...
I'm here! Come by for a chat.
5/ Note: there's more to come — in particular some way to automatically include injected values without building a Go binary, but these should provide a foundation for that.
5 authors I've read at least 5 books by: E J Swift Adam Roberts Alasdair Reynolds Christopher Priest Adrian Tchaikovsky
A great example of how the Google #golang team put thousands of lines of ultra-technical code in service of an incredibly easy-to-use and useful tool. If you ever deprecate code, you really should know about the go:inline directive!
1/ I've just published three orthogonal but related CUE proposals. #cuelang 🧵
2/ Proposal: User-Provided Functions and Validators github.com/cue-lang/cue... A simple Go API for wrapping Go functions as CUE-callable functions and validators — extending CUE's evaluation with custom logic. #cuelang