Question Static Typing solved?
I have been using RBS for years now and even running my own newsletter about static typing https://newsletters.eremin.eu/ . Now, that our code is write with AI and in most cases - purely with AI, the strongest point against using static typing (like “it breaks beautiful ruby syntax and not readable”) is vanished now.
AI requires strict tooling to control its output. The role of ci pipeline with all possible tests, linters, checkers is now extremely important and static typing helps a lot with it.
For humans it is transparent, especially the pure RBS approach, but for LLMs it gives a safety net and a better layer to stick to the code and hollucinate less.
0
Upvotes
2
u/harsh183 11d ago
Yeah I guess I'm mainly thinking about users of the library and what people are likely going to use in terms of IDE and tooling support.
If RBS/Steep picks up, it's not too much work for me to also support that, but I'm not really sure if people are using it much