mechanicum

They haven’t cut a release since March. There have been updates almost every day.

I do think though that the long playing time is an important factor in the emotional devastation.

Considering other venerable classics with similar dynamics, I’ve seen far more people be far saltier about betrayal at the end of a game of Twilight Imperium (even though there can only be one winner) than they do in something like Cosmic Encounter (where they could have played for an almost guaranteed joint win).

Much easier to laugh off a 20-30 minute game and go again, than watching an entire day of scheming and planning go up in smoke at the hands of a supposed ally.

I don’t think utility or popularity had anything to do with the decision. It’s just that they no longer support casks with unsigned binaries.

You could create a third-party tap to install wine via homebrew.

> I switched back to main after noticing that the plugin branch adds about 1s to startup time

Very curious what’s happening there. With empty helix.scm/init.scm, there is essentially zero measurable impact on startup for me.

Bytecode caching isn’t yet enabled (it is in progress), so I can see that kind of delay if I’m giving it tens of thousands of lines of code to evaluate on startup, but it took a lot of effort to get there.

Talking to the person who gave it to you, in my experience.

In my own testing, Pangram is excellent at detecting the default output styles of LLMs.

If you tell the LLM to change its output style, so it’s not full of “load-bearing spaced em dashes that aren’t X, they aren’t Y. they’re Z.” constructions (which humans are pretty good at detecting on their own), the false negative rate soars.

I’ve seen the original repo, I mean Godier’s.

A name clash is the least damning evidence in my opinion. Last year my previous employer asked us for suggestions for naming an AI agent. Everyone produced pretty much the same list, because everyone just asked ChatGPT.

Except me. I had also asked ChatGPT, but I bothered to google the suggestions and found there were already like half a dozen AI agents for every suggestion.

(they ultimately launched what was by then the 7th or 8th AI-related product with essentially the same name)

Creativity in naming doesn’t seem to be their strongest suit.

I’d love to see the other repo, and the prompts that led to both.

Did Godier copy the other guy’s repo, name and all, and try to pass it off as his own work? That seems like the obvious conclusion, albeit brazen to the point of insanity.

Did Claude copy the repo, in response to a prompt? If Claude copies a Claude vibe-coded project, can any plagiarism really be said to have taken place?

Or is this just what Claude is statistically likely to spit out if you prompt it to build an astronomy app and leave it to it?

You almost can, with Jackson:

  jshell> new ObjectMapper().valueToTree(Map.of("providers", List.of("SUN", "SunRsaSign", "SunEC")));
  $4 ==> {"providers":["SUN","SunRsaSign","SunEC"]}

(or was that the joke?)

It looks like that was added in Java SE 6, and doesn’t materially change the underlying problem. Have there been more recent developments?

My understanding was the biggest issue has always been that javac is a poor foundation for any kind of live tooling like LSPs?

It’s less “make me a Java LSP” than “rewrite javac around incremental compilation and exposing a semantic DB”. Which sounds like a much harder problem.

> I've found LLMs to be bad at balancing parenthesis.

I think that was true last year. In my experience, it’s no longer the case with Claude Code or Codex.