I think in principle you could clone your database in prod and at least test to see if your most difficult + common queries are indeed faster after running through the LLM optimizer?
Frankly, just a general extension to feed a query log to a batch job to do offline optimisation of common actual reoccurring query shapes based on a query log might well be worth it.
> I think in principle you could clone your database in prod and at least test to see if your most difficult + common queries are indeed faster after running through the LLM optimizer?
That is the responsibility of whoever thought it would be a good idea to write this article. It's their responsibility to show that their idea has merit, and that their results are significant. I mean, don't they have a vested interest in manipulating and cherry-picking their results to inflate their relevance?
Like when we claimed that the russians had sabotaged their own pipeline rather than just stop pumping gas, after Biden declared he'd blow that thing up in case of conflict, and we are still supposed to believe it was the russians?
You can very likely borrow check in languages that don't have it in the type system. Exactly the way you suggest, as an optional add-in. It's still WIP but in my side project I haven't found cases that can't be handled yet.
> Exactly the way you suggest, as an optional add-in
No, I don't suggest it, but criticize it. Rust performs its checking as a separate step after actual compilation, which sometimes leads to strange behavior (like borrow errors are shown only after actual compilation errors). I prefer an approach which is integrated with other language mechanisms.
> It's still WIP but in my side project I haven't found cases that can't be handled yet.
It's generally a good idea to write such an analyzer, but I doubt it can be useful without proper integration with the language itself (with huge semantics changes). If it's too strict, it will reject perfectly fine code, but otherwise it will catch only the most obvious errors and approve code having more complex memory bugs.
I think Pony’s reference capabilities are a better solution for linear types. It’s just part of the language so a violation is simply a type error, not something flagged later during static analysis.
Well.. that amount of bars you can see depending on the real signal level is just a SIM configuration. In the "newer" networks they aren't configured properly yet.
It has, but I only learned about it when the drama started hitting HN recently. But since I learned about the guy and the company in the same headline I put two and two together right then and there. I've learned some suspicion of founders who name companies after themselves.
There is no reason to believe that the transformers couldn't be doing something close to what copycat does (especially with thinking tokens), as an emergent phenomenon of the sheer size of the corpus. The architecture is certainly capable of encoding the actions in copycat anyways.
reply