> maybe that's driven the idea that "scripting/untyped/loose typed languages can't have good Code Intelligence"? One idea I've had on this subject is that each

> maybe that's driven the idea that "scripting/untyped/loose typed languages can't have good Code Intelligence"? One idea I've had on this subject is that each layer of tooling multiplies or reshapes the capabilities of all the other layers. This sounds great, but there are good reasons to choose limited tools. Sometimes a powerful tool can grow so powerful that it does the work of other tools, and suddenly your other tools are dependent on this one layer. So we use vim to edit 10 KLOC files, but should your files be that big? Your editor can do braces and semicolons for you, but should you need those? If I have a fancy type system do I need tests? I'm not specifically advocating for a crappy editor, but the rule of least power suggests that we might get ultimate flexibility out of weaker tools.