Turing machinist for hire. Gremlin herder. πππππππππ ππππ ππππππ
Dude and Catastrophe.
- Tweets 3,920
- Following 95
- Followers 243
- Likes 119
The first (one-shot, no real feedback beyond "make sure to match the design as closely as possible", "please don't ignore features") ASP NET attempt is...similar to the original Elixir implementation (whose issues are well-documented).
Code (@dhh if this would be helpful):
github.com/crertel/once-campβ¦
Testing rig (best with nix):
github.com/crertel/once-campβ¦
Now, of course, I expect that my dotnet version is *at least* as flawed as the Elixir version--I've only used C# for some low-level binary shenanigans and gamedev. But, what's interesting is that it only took a few hours for stock @grok Build (not even Claude or Codex) to bodge this together.
2
1
1,123
But, the important thing here is that now *somebody else* can fork my attempt and golf it and run it through their own brain or clanker(s) and apply expertise.
I think a pass of "Okay, now make this idiomatic and look for common performance problems, let's add tracing and sampling and profile it" would be a great next step.
Or, in the fashion of the times, throw a stronger model at it.
249
Something that's very important to note about the automated ports of the Basecamp stuff from @dhh , which *I ALSO* have run into with the ASP NET port, is that you really have to sit on the models and nudge them to make sure they achieve parity with the original.
Lack of strong test suites and acceptance tests makes it really easy for models and harnesses to just go "oops, I totally forgot to lug over the entire file upload workflow" or whatever.
Similarly, lack of benchmarks, stress tests, and other things particularly backed by profiling means that if you're doing something weird (say, serializing DB access), **the AI will be much less likely to spot it**.
A simple instruction "hey, port this code to Elixir" or whatever will skip best practices that might get pulled in during the harness' reflection on most pessimum profiling.
We've run into this with our work on indie gamedev in Godot.
617
So, the work that @dhh has done with the campfire shootout is interesting in a few ways:
1. He's shown how very easy it is to port small-medium legacy webapps to a new language using AI with minimal involvement. (I'd done something similar this year handing Claude the source code for system shock 1 and porting the renderer to JS.)
2. He's shown that these ports will suffer in ways predictable to experienced users of those languages but hard to catch otherwise.
3. He's shown (really, reaffirmed) the easiest way to get information on the internet is to loudly say something wrong and bait domain experts into replying.
4. He's shown that even unpalatable languages (e.g., Rust) with nice performance benefits can now be attempted in places where nobody sane previously would've done so.
These are all useful results!
2
3
69
5,714
(in response to a friend asking if abandoned malls were backrooms and if not what they were originally)
originally, no, just some weird liminal space. but once described in those terms, any architectural space whose energy and purpose is ultimately meant for transitional and--while perhaps not antihuman, but ahuman; that is to say, meant to prevent the accumulation of the psychic energy of its tenants and passers-through--transactional experience becomes something that is backrooms-adjacent.
322
Great news everyone! You can just choose not to have certain problems.
minor.gripe/posts/2026-09-25β¦
1
142
Having seen the wildly successful fundraising of Omarchy, I exhort everyone in the #nixos community to reflect on what we could be learning from their approach.
Even ignoring the (evidently severe) rolodex of @dhh , there're obviously still millions in funding being sent their way--what can we learn from this?
4
257
The ability of nixpkgs to clear its backlog in the past five years also appears to have changed.
1
1
160
The implication of high Gini coefficients in open source projects both challenges the common notion of community-over-all-else as well as explains some degree of the animosity towards clankers, in my opinion.
In some ways, your average OSS contributor complaining about AI contributions is like your average American complaining about tax cuts: they're not the ones actually impacted.
1
1
63
Interesting finding from my Nix ecosystem research.
(remember: all data analysis is flawed; some of it nonetheless is useful!)
1
1
77
That Gini tho.
For anybody paying attention, there's an interesting implication here:
1. Nix often really is a good-old-boys club
2. If you want to replace the top 10% (around 400 developers) for nixpkgs with clankers you might well still get 80-90% of the output.
(check pmc.ncbi.nlm.nih.gov/article⦠for other work in this area)
49
I must admit to being darkly amused at the current live-action remix of "I'm just a bill" and "Weekend at Bernie's" playing out in our capitol.
2
57
Graphmath 3 is out.
github.com/crertel/graphmathβ¦
Lots of fixes, back to complete test coverage and alternative-implementation cross-checking.
2
78
Google and transformers is going to go down in the business case studies along with Kodak and digital cameras.
1
2
77
