3 ms·
They're claiming that the runtime will figure it out for you. It wouldn't be too surprising if this is the sort of thing that an optimizing compiler or query p
by fizx 3y ago
They're claiming that the runtime will figure it out for you.
It wouldn't be too surprising if this is the sort of thing that an optimizing compiler or query planner could do better than a human.
If not, you're probably at the scale where performance regressions are caught and rolled back at early phases of rollout.
Like most magic, it's either going to make things 100x better or 100x worse, depending on how leaky the abstraction is at its current state of maturity.
- dilyevsky 3y agoI'm going to (at least I should) design my application logic very differently if I know in advance the call might take a while or timeout completely. If I'm not offered that info during development time it's just going to turn into terrible mess in production. Ain't nothing any framework can do about it if the language itself lacks the semantics to express developer's constraints.