Same, just gonna stick with node. On the other hand, the trial by fire will be interesting to see... long term I can only imagine the kinks will surely work themselves out
spec isn't code. There's a C language specification and many implementations. There are a handful of browsers each implementing HTML, JS, and CSS specs in their own way.
And given a C description of a program, a C runtime can implement that program in various different ways — interpreted vs compiled, explicit memory management vs garbage collection, different pointer sizes and memory layouts, parallelism at various points or not. It's turtles all the way down :) It just becomes ‘code’ at the point where a computer can execute it (in one way or another) without further human intervention.
I moved over back when GitHub was planning to charge per minute to use my own runner. It was easy with Claude, the gh API, and forgejo web API. I even set up daily backups to my S3 clone of choice.
The only repos I left on GitHub are forks and one with a bit of public engagement.
> Most of us, when we want to ship a product, we start at the beginning and with the most obvious ingredient: the product. Because when you can create, the act of creating feels most natural and straightforward. But it makes it so easy to end up with a product that nobody wants to buy. And isn't that every new entrepreneur's worst nightmare? All that work, and nobody cares.
reply