The thing I would have liked to know is why they don't use an existing fast SQL parser. Was being slightly incompatible with all existing SQL dialects a product requirement?
I tried a few PPTX files from consulting firms that are available online. The rendering does not seem to be truly pixel-perfect, but all of them were quite readable and had a good layout, which is already an impressive feat.
I use the latest codex with gpt5.4 and Claude opus every day. they hallucinate every day. If you think they don't, you are probably being gaslighted by the models.
I use linux at home (with a HiDPI screen) and MacOS for work. The screen works well with both computers. I mostly just use a text editor, a browser, and a terminal though.
Linux has bugs, bug MacOS does too. I feel like for a dev like me, the linux setup is more comfortable.
I use a fork of sqlx in SQLPage [1]. I think my main complaint about it is runtime errors (or worse, values decoded as garbage) when decoding SQL values to the wrong rust type.
In the second handpicked example they give, GPT-4.5 says that "The Trojan Women Setting Fire to Their Fleet" by the French painter Claude Lorrain is renowned for its luminous depiction of fire. That is a hallucination.
There is no fire at all in the painting, only some smoke.
If the electricity were generated by thousands of volunteers pedalling in their basement, then yes, I would expect the utility company not to be too greedy.
ChatGPT (4o): Noticed "a pattern"
Le Chat (Mistral): Noticed a "cartoonish figure"
DeepSeek (R1): Completely missed it
Claude: Completely missed it
Gemini 2.0 Flash: Completely missed it
Gemini 2.0 Flash Thinking: Noticed "a monkey"
This resonates with me. I used to love tinkering with "underdog" tech. I did frontends in svelte before it was cool. But for new projects, I now always default to react+tailwind, because that's what Claude knows best.
And for the backend, I'm working on a SQL-only framework, because LLMs are now at almost 100% accuracy on text-to-sql.