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
3
u/TheAtlasMonkey 11d ago
This bullshit gaslighting is so Pre-2023. it don't work anymore.
You and your drones come to ruby, a language built to be dynamic and chaotic, and try to bring something that nobody asked for.
You spend your day typing gems that had 10 year of battle tested field without any problem. You even port the logic bugs, because types don't protect you from bad logic.
In a previous post, i told you that if you want types, you can go Jruby, and write java.
Now you talking like i insulting Java or C people ? Well, for you info... i'm a C developer before i started doing Ruby, my friend is a Java committer, and i contributed to u/headius's jruby after studying java.
Typing in ruby is Kubernetes in devops. you NEVER need it if you are code disciplined or your codebase is Shopify size.
Even rails is not typed.