From reading the GitHub privacy statement, I'm interpreting that private repositories won't be used for AI (https://docs.github.com/en/site-policy/privacy-policies/gith...). I'd be interested to hear any different though.

To add a complicating factor, from this blogpost [1] GitHub say's "...if you provide private repository content as input to an AI Feature, we may use that input to improve AI features".

So I assume that if you were to supply a significant chunk of code to AI and ask for a code review, then your code could end up in the training data even though it wasn't written by AI (unless you know there's a manual opt-out option [2]).

[1] https://github.blog/changelog/2026-03-25-updates-to-our-priv... [2] https://github.com/settings/copilot/features

Eric answered a similar question on the Discord channel saying Slug is suitable for generic vector graphics. He recommends checking out the demo at https://sluglibrary.com/ (you can cycle through the examples with the space bar).

Awesome, thanks.

Scott Geffert did a talk about The Met scanning process on Weds at the OpenUSD working group meeting. Here's the link he shared which explains more (along with a bit of history) https://www.metmuseum.org/perspectives/color-photography-sta...

A near neighbour described being interviewed by Tony Hoare for his first job after graduating (he got the job!). Sounds like the interview process in those days was a chat over lunch rather than coding exercises. https://news.ycombinator.com/item?id=43592201

42

The bytecode interpreter in the second half of the book doesn't use the visitor pattern.

No, but his first "Tree-walk Interpreter" does - he builds an AST then uses the visitor pattern to interpret it.

https://craftinginterpreters.com/representing-code.html#work...

To quote the very first paragraph of the bytecode interpreter section[1]:

> The style of interpretation it uses—walking the AST directly—is good enough for some real-world uses, but leaves a lot to be desired for a general-purpose scripting language.

Sometimes it's useful to teach progressively, using techniques that were used more often and aren't as much anymore, rather than firehosing a low-level bytecode at people.

[1] https://craftinginterpreters.com/a-bytecode-virtual-machine....

Sure, I'm not criticizing it.

He's doesn't actually build on this though, but rather goes back to a single pass compiler (no AST, no visitor) for his bytecode compiler.

the parser does

The parsers in crafting interpreters do not use the visitor pattern. The visitor pattern is used when you already have a tree structure or similar. The parser is what gives you such tree structure, the AST. When you have this structure, you typically use the visitor pattern to process it for semantic analysis, code generation, etc.

I’ve only glanced at the second part but I don’t remember that being the case.

Probably this one (not launched yet) https://www.kickstarter.com/projects/argonforty/upton-one-th...

Yep that's the one, I have to say it's kinda tempting on one hand, but on the other the Pi 5 is still about 4x slower than this already slow Framework 12 with a GPU that barely qualifies being called that so using it would be pretty painful I imagine.

The Metaverse Standards Forum has had some activity around gaussian splats recently, for example debating whether it's too early to standardise.

There's a town hall on 5th March with speakers from Niantic and Cesium: https://metaverse-standards.org/event/gaussian-splats-town-h....

The previous splats town hall, and other related talks, are on the videos page (there was another gaussian splat talk a couple of days ago from Adobe). https://metaverse-standards.org/presentations-videos/

Nice list. USD (Universal Scene Description) has been renamed to OpenUSD. Part of the motivation was to make it easier to search for. Not all the official docs have been updated yet though.

Given USD is in the list, I am a little bit surprised that alembic (.abc) isn't.

A strategic move

Another example of 'control flow' is the new behavior graph from Khronos (glTF Interactivity Specification). They did a survey of existing visual programming langauges and are trying to making a standard. It's just been released for public comment: https://www.khronos.org/blog/gltf-interactivity-specificatio...