Look cmon, this is pure cope. The problems it has solved in TCS are far from trivial, with plenty of smart people making their careers in trying to solve them. The techniques these LLMs are using are non-trivial, and not just brute force.
I'm more interested in the techniques used to generate these proofs, and how they can be improved to be as reliable at solving a broader class of problem than already formalized mathematical conjectures.
These are pretty nice examples, as both SQL and Prolog can only be used well for anything non-trivial when you're aware of how the result you're asking for is going to be figured out.
It's not apt not being smart that can cause troubles when mixing packages from various suites. There's no reason to mix in cases where you can just use backports instead.
I've been using touchscreen laptops for more than a decade now. It's been really useful when working on mobile stuff and occasionally handy in some games or when sketching something, but other than that - it just stays unused.
Yeah, but what's more likely to happen is that when you look inside the code you see thousands of lines of code of a handrolled parser and when you ask "why would you write your own rather than use some existing one here?" you only get silence in return.
I don't really generate big chunks of code, but in general I found AI outputs to be quite sensible. It knows what the main modules are and uses them, I've not seen any as egregious as making a JSON parser from scratch without a need.
Maybe not a JSON parser in particular, but I've already seen a fair share of MRs that contained many thousands of lines that no human would have ever written without stopping to ask "do I really need to do it?". LLMs aren't bothered.
reply