3 ms·
I'd rather use a static language like Go which still keeps much of the dynamic feel, and helps catch my mistakes at compile time. Right on. It's the "dynamic f
by stcredzero 11y ago
I'd rather use a static language like Go which still keeps much of the dynamic feel, and helps catch my mistakes at compile time.
Right on. It's the "dynamic feel" which is really the key. It's the ability to iterate quickly, the access to anything in the runtime, and the ease of building software tools. It's an environment that makes you powerful by enabling everything and staying out of the way. Whether that's provided by "dynamic" typing is just an implementation detail.
- pcwalton 11y agoUnused imports and variables being errors is pretty squarely counter to that philosophy. I don't think Go represents the "static typing, but lenient" philosophy particularly better than C#, for example, does. Go seems to focus on simple typing, not lenient typing. There's a big difference between the two.
- stcredzero 11y agoI never said Go was perfect. Go needs to have much better debugging for my tastes.
- earthboundkid 11y agoI am never bothered by unused variables when I'm doing exploratory programming in Go because if the variable is still unused, I haven't written enough code to get to the point of running it for testing. I used to be bothered by the import thing, but then I installed goimports, and now Go is actually better than other languages for imports. Just write "foo.Bar" in your code and goimports will automatically add "baz.io/foo/" to the imports section on save.
- StreamBright 11y agoHow about optional type systems? I feel like in Go I have to use something (like an interface) to achieve the feel of dynamic typing but it feels much worse than having optional types or no types at all.