lemming

...Unity made a blog post saying they were happy about you moving to Unreal, publishing they think it'd be a win-win, then outlining why they think so

I mean, that makes it all sound very polite and dispassionate, but Andrew's piece was anything but. I have no dog in this fight, I don't use Zig, Rust, Bun or Claude, and initially I thought the bun rewrite sounded like a terrible idea. I changed my mind after reading the piece about the migration - it was very interesting and the process was obviously quite thoughtful. Andrew's piece made me want to take a shower afterwards.

This is amazing! Very refreshing in the age of AI to see so much manual building going on. Sadly I don’t have much time myself but I have several friends who would love this, I’ll pass it on to them.

The always excellent Oatmeal:

We need to have a conversation about wombats

https://theoatmeal.com/comics/wombats

Possibly NSFW, depending on your W.

...parents are also responsible to lock their alcohol, drugs or guns...

No they're not - all those things are illegal for children nearly everywhere.

One thing that would be useful in the readme is instructions on how to install the built app on a phone, for those of us who don’t do iOS development.

I agree, some of the examples look very nice, but some have small-scale vortices that really don't look realistic.

That said though, lovely site and project!

Or if the code is really important, sometimes even “please make no mistakes” is necessary.

Perhaps not in that one, but in plenty more: https://www.972mag.com/lavender-ai-israeli-army-gaza/

Because just firing up Claude and let it rip

Based on Tridge’s post, this seems an unfair characterisation of how he used Claude.

Did Claude increase bugs in rsync?

TFA answered this, the answer is “no”.

Tridge in his blog post describes people as "foaming at the mouth"?!

Did you see the picture in the article where the user posted a picture of them strangling the maintainer? I think “foaming at the mouth” is probably gentler than how I would characterise that.

I always remember when, as a young geek writing games for my C64, I was thrilled when I saw the Terminator and a lot of the code scrolling past in its HUD was 6502 assembly code!

That is really interesting, and very clever - thanks for the details! What you describe is indeed what I meant by whole world, I'm not sure if there's a better term of art for it.

I can't speak for the core team, but from memory invokedynamic took a long time to become performant. So if you still want to support older JVM versions, the performance will be pretty terrible on those older systems if invokedynamic is used for something as integral as var lookups.

That is very cool indeed. Are there limitations that this imposes? Is Julia a whole world compiler or does it support partial compilation?

Clojure (AFAIK) does not use invokedynamic, except perhaps in the latest version for some of the new interop stuff. It still officially supports JVM 1.8 bytecode. It’s a language which greatly values stability and backwards compatibility, so it’s been very slow to adopt newer JVM features.

No, it doesn't. In JVM Clojure's case, the vars are usually compiled to the moral equivalent of a global variable holding a pointer to a function. This allows you to update the function if the developer redefines it in the REPL, but it comes at a performance cost (the JVM can't inline it or otherwise optimise it). Clojure also allows you to compile with "direct linking", e.g. for production deployments, where you know you're unlikely to be wanting to dynamically update the code. In those cases defns are compiled down to static methods which call each other - much faster since the JVM can perform its magic with them, but you can't update them at the REPL.

I'm unsure exactly how jank works WRT this tradeoff, but the article makes it sound like it's closer to the direct linking version, but with the inlining etc being done by jank rather than the JVM. I don't know if this is only for AOT or also in JIT cases.

Great article, as always.

There is one thing that I think is important to bear in mind when discussing inlining, especially in the context of Clojure. This is that once a function has been inlined, you can no longer update the definition of that function in the REPL and have that update the behaviour of functions which use it, unless you recompile those as well. This is not a criticism of course, it’s just part of the natural tension between dynamism and performance.

When I was in NYC a while back, I met a woman at a friend's dinner party. She sounded totally American, but was in fact Brazilian. She worked as a lawyer, and said that she'd had to get extensive voice training in order to sound American so that people would take her more seriously professionally. I have no idea if the professional part worked, but the accent, mannerisms etc was amazing - I would never have guessed.

Sure, but the article talks about flourishing populations of deer, elk, and bison. I assume that means we’re talking about herds of each, all in the same space. And they have to survive over winter, which sounds pretty cold there - presumably they don’t migrate, which I guess they usually would? It’s definitely not ideal conditions.

Obviously it’s possible, but I was surprised.

What's amazing to me is how little space is required to have a completely self-sustaining ecosystem. A 60km diameter circle just doesn't seem like a very big space to have enough plants to support "flourishing" numbers of multiple types of large herbivores, without migration, as well as all the different prey species required to keep things in balance.

Regardless of the arguments about radiation, it seems pretty clear that lack of humans is really the most important thing for animals to flourish.

Thanks! Yes, I get on really well with everyone in the community - the community in general is perhaps my favourite thing about Clojure!

Hehe, Lisp Emacs Myopia is indeed a real thing. Cursive users have been not starting REPLs for over a decade now!

j/k of course, and no offence taken :-)

Things have been different for well over five years...

In fact, I first presented Cursive at the conj 2014, and I'd been working on it in open beta for perhaps a year before that, so well over 10 years!

...all this fantastic "static analysis style" developer tooling by borkdude and eric dallo.

ahem

I still don’t understand why they’re referred to as persistent vectors rather than immutable vectors, but I digress.

I believe that immutable just means, well, immutable, but persistent means that updates are achieved via structural sharing, so they’re efficient.

So soon our agents will need spaced repetition flash cards for the things we want them to remember! I eagerly await Anki for Agents.

Related question: how are people handling adding family members of varying technical abilities to your tailnets? Does each family member get a separate user so you can manage their access? For my immediate family I was just logging tailscale in as me on their devices, but that becomes a pain when they get logged out and need me to log in again before things go back to working.

I'm very familiar with Clojure, but even I can't make a good argument that:

    (tc/select-rows ds #(> (% "year") 2008))

    filter(ds, year > 2008)

But if it doesn’t have access to the network, then it’s just not very useful. And if it does, then it’s just a prompt injection away from exfiltrating your data, or doing something you didn’t expect (eg deleting all your emails).

This argument is predicated on Anthropic losing money on the subs, but I'm not sure that's a cut and dried argument. OpenAI have said publicly that they're (very) profitable on inference, and they're much cheaper than Anthropic. I suspect this is just artificially trying to create a moat. The problem is their moat is not as sticky as they think it is - I completely ditched Claude for Codex a while ago, my money now goes to OpenAI, and I'm very happy with it. For a while Claude was noticeably better, but that's not the case any more - in my case I prefer Codex.

This actually produces more impressive results than I expected. My understanding was that models are quite poor at spatial reasoning/understanding, so I'm surprised it can generate such good assets. Do you use different models for the 3d generation?