Absolutely incredible.
1,630 karma · joined October 13, 2013
Absolutely incredible.
One of those benefits brings to mind another analogy: Apple. The ai model and the tooling are kind of like the hardware and software. By co-developing them you can make a better product and certainly something hard to compete with.
More importantly: can this be used to run untrusted jobs? E.g. user-supplied or AI supplied code?
It would seem to me that durable execution implies long running jobs, but this kind of work suggests micro optimisation of a couple of ms. The applications inherently don't care about this stuff?
What am I missing. Or is it just that at a big enough scale anything matters.
I implemented something like this once but had to use the typescript compiler to identify all the variable names and also use the typescript compiler to find valid moments they could change and insert code to capture their value at that time. Guessing you didn't go to that length in multiple languages. Sou how did you manage this? I'd be very interested in a technical write up and I suspect hn would too
I'd be interested to read a blog post or technical write up. I think conceptually it's an interesting idea
Seems like a lot of effort to go to otherwise
One big reason: you can't name it interfaces.d.ts, or import as type, which has widespread implications:
Your types are now affecting your shipped bundles.
Sure that's a small bit of size - but it can actually lead to things like server side code getting shipped to the client.
Whereas if it's all .d.ts stuff you know there's no risk of chained dependencies.
I'd go so far as to say default eslint rules should disallow enums.
Works best at the extremes
GPT4, GPT4T, Gpt4o-Mini, GPT4o,