71–72 of 72 posts
Awesome work, but I am genuinely curios about the use cases where the 200ms init time being a problem?
Lambda is far more economic given the memory requirements, but we recently moved to Rust+Candle to shave off ~300ms on cold starts as the lag could be really jarring.
Earlier quoted context omitted.
> I haven't kept track of what Oliver's doing here lately Please do go and check up what the state of using types to inform the compiler is (I'm not incorrect) On the area allocator, I wasn't clear enough, as stated elsewhere this was in relation to having something similar to isolates - each having a memory space that's cleaned up on exit. Python has almost identical semantics to JS, and has threads - there is nothi…
It is absolutely true that it is unsafe to trust TypeScript types. I've chatted briefly with Oliver on socials before and he knows this. So I am a bit confused by this issue: https://github.com/CanadaHonk/porffor/issues/234 which says "presume the types are good and have been validated by the user before compiling". This is just not a thing that's possible. Types are often wrong in subtle ways. Casts throw everything…
Well... unsafe and impossible aren't quite the same thing. I guess this is possible if you throw out "safe" as a requirement?