LLMs are already a powerful tool for serious math researchers, just not at the level of "fire and forget", where they would completely replace mathematicians.
I've used Sorbet a lot but don't really count it. I understand why others would but I find the type system is extremely shallow and limited and the overhead it adds to development (and even performance) is substantial.
Also Ruby has RBS now which is not inline and... much maligned to say the least. I think the entire ecosystem is at a crossroads rn wrt typed Ruby
No worries, I also think it deserves a bit more highlight, especially to those who are against having rbs as separate file and to those who despise the Sorbet DSL in Ruby. The plan with Rbs-inline is to merge with rbs-gem so it will come included in Rbs!
> Debugging a program running on a $100M piece of hardware that is 100 million miles away is an interesting experience. Having a read-eval-print loop running on the spacecraft proved invaluable in finding and fixing the problem. The story of the Remote Agent bug is an interesting one in and of itself.
Some context from the blog post:
> I turned to service apps this winter: doordash, instacart, uber eats. Their signup systems were incompatible with my full, legal, one-letter last name, and it took about 50 hours on the phone with doordash support in Malaysia and the background check provider in India to eventually get cleared to drive them. I was not able to get through on the other apps.
For sure the impact is not just limited to service apps.
> Of course, Figma‑ or Gmail‑class apps still benefit from heavy client logic, so the emerging pattern is “HTML by default, JS only where it buys you something.” Think islands, not full SPAs.
reply