https://www.swiftlatex.com/editor.html for the wysiwyg editor says "We are working hard to fix the editor." It has said this for many years. I think I tried it once when it was live and it was pretty cool. My guess is people observed it could corrupt documents, so it was taken down.
I strongly disagree with "Claim 1: Every goal of code review can be served by agents at lower cost and higher throughput." They define the goals and include this one:
> "Knowledge transfer. Agents can actively generate on-demand explanations, architectural summaries, and updated documentation at merge time, which is a more reliable and scalable mechanism for propagating knowledge than the incidental commentary of a busy colleague.
Knowledge transfer is much more than what they claim. An critical goal of code review is making sure humans do deeply understand overall what software actually does. Code is far more precise and detailed than any "on-demand explanations, architectural summaries, and updated documentation."
This interview https://youtu.be/oWOz2htozfI?si=qdQ0uZRoZOYeThOn
from 2 days ago with a top researcher from OpenAI directly addresses the bitter lesson argument and the importance of scaling for the history of their models.
> Some of the numbers that you saw from the number of students who receive failing grades were because we caught them (cheating) and prosecuted them and are sending their cases to the center for student conduct,” Garcia said. According to Garcia, nearly 30 students in CS 10 were caught cheating on take-home exams in spring 2026.
SEA with node.js "works" for nearly arbitrarily general node code -- pretty much anything you can run with node. However you may have to put in substantial extra effort, e.g., using [1], and possibly more work (e.g., copying assets out or using a virtual file system).
The current OpenClaw GitHub repo [1] contains 2.1 million lines of code, according to cloc, with 1.6M being typescript. It also has almost 26K commits.
This exact thing solves a huge problem with SEA binaries as he points out in his post. You can include complicated assets easily and skip an ugly unpack step entirely. This is very useful.
He is trying to use a different phrase “write-only code” to define exactly the same thing Karpathy defined last year as “vibe coding”.
For what it is worth, in my experience one of the most important skills one should strive to get much better at to be good at using coding agents is reading and understanding code.