> I'm not with him on making types more prominent in Ruby. They are also micromanagement and I don't plan to use those new features I agree with the general a

> I'm not with him on making types more prominent in Ruby. They are also micromanagement and I don't plan to use those new features I agree with the general argument, except this - keep in mind that typing in Ruby is optional (and will always be). So devs who choose not to use it, they won't suffer any downside. There are also middle grounds - typing can be added gradually or locally. Keep in mind though, that as projects grow large, handling dynamic languages becomes more and more challenging, and adding types is a good strategy to handle that.