>Certainly, and I can also type my JavaScript. Running a linter that catches just unused imports is a one line command (30 seconds), whereas statically typing

>Certainly, and I can also type my JavaScript. Running a linter that catches just unused imports is a one line command (30 seconds), whereas statically typing your javascript essentially requires a full rewrite (weeks or months of work). >This is why Go's simple but strict rules are so key to keeping it clean. There's value in being able to "dial up" the cleanliness as and when its needed. It's often a waste of time to focus on cleanliness of code that you're not sure is going to last. I wouldn't want unused imports to cause a compiler failure even though I run the linter and use that rule regularly.