"Your homework for tonight is to tidy up this SQL query"

An incredible achievement and a joy to visit!

That said, code can still do: `Composite([a,b,c])` to emulate an ordered tuple like key instead of naming each property explicitly. So not completely impossible.

The performance of creating each object will be, at best, linear with the number of properties. So a risk with tuples is that code might treat them like a cons-list with fast prepend and end up being accidentally quadratic.

I'm really excited with the amount of things we now have agreement on! Still some open design points to resolve before Stage 2.7 but have already had great input on these 🚀

Yeah, that's really impressive. Really well explained.

This is why I don't love the hype around download numbers. Downloads are cache misses 😀

Thanks!!

Would it be possible to update the diagram in the post to make it easier to know which logo is which framework?

I treat myself to printed magazines when travelling. Had a work trip last week so have MIT tech review and the Economist in my bad right now.

I do find conditionals helpful in certain situations, when the negative case would trigger so much logging it would slow the system. But that isn't super common. When performance is ok: unconditionally logging and then grepping the output seems to work fine.

Welcome welcome!!

Plus One

What unbelievable luck! I found ASSIH while working my way through the library. When do we compare notes?

Running /clear feeling like I'm Agent K in MiB

I presume there is a, albeit surprising, good reason?

I think enabling coverage tracking disables JS optimizations, at least in v8. I think that's why the data is only collected when devtools is open.

This is wonderful