Why does having. GC mean not thinking about memory? I think about memory constantly in GC languages because I still want it to perform well.
The biggest difference is the failure modes. If I'm not thinking about memory, my RSS is higher or a bit of extra CPU time goes to GC. Both of those are radically better than UAF or buffer overruns. Good trade IMO.
Having that natively available as plain Common Lisp code is a very different thing from your "just read a text block and compile it as rust code!" concept. Or at least, the tool chain gymnastics required to make a C program emit its own source in another language... Why?
Can anyone explain this "quietly quantized" model idea to me from a business perspective?
Coca-Cola doesn't "quietly water down" its product to save a few bucks. They know people will take a sip, say "oh that's not what i wanted", and go buy a Pepsi.
If they serve me a quantized Fable, I'm just going to think Fable sucks and go get my tokens elsewhere. What's the point?
There's a bit of a mental model flip to make maybe.
> they're code that's generated at compile time
They're code that generates code at compile time. Macros can actively walk the AST of the parameters they process and rewrite them completely into new shapes. That transformed AST is what then actually gets compiled.
check out tsnet if you are building on tailscale anyways. your app can then be a tailnet node that can read tailnet WhoIs data and have access controlled via tailnet ACL
Really depends what you're working on. GLM 5.2 is doing excellent webdev work for me but really faffed up when working on a custom garbage collector that Opus has no problems with.
I'm actually very happy about this. Babysitting the agent just in case it needs me to do something is a terrible use of my time. I've always had to be very explicit about the various ways that it can get an automated feedback loop going to check its work, and now Fable doesn't even need that hand holding. Really great improvement all around.
Generally you don't even need to do the sub-routing in the handler. You can just render the entire page and have `hx-select` attributes pluck out the part that you want.
Your Go server can have endpoints that render XML instead of HTML and basically get the same server-driven experience of your HTMX site. Fully skips the need for the app review process since you're not updating the actual client app code to make UI changes.
I've spent an obscene number of hours learning how to get reliably good quality code out of these things. I'm actually very happy with where the tech is right now and can't imagine ever going back to typing code by hand.
But I absolutely hate how companies and society at large are acting because of this stuff. It feels like all rationality has flown out the window. So I'm just staying in my sandbox with my little toys and hoping the mass psychosis blows over at some point.
The biggest difference is the failure modes. If I'm not thinking about memory, my RSS is higher or a bit of extra CPU time goes to GC. Both of those are radically better than UAF or buffer overruns. Good trade IMO.