I’m playing with typeful language stuff. Having only done a pinch of Haskell, Scala, and Go tinkering amidst Ruby work over the past ten years, it’s jarring. But, things are much better than they were before I started with Ruby.
Elm in particular is like working with a teammate who is helpful but far more detail oriented than myself. It lets me know when I missed something. It points out cases I overlooked. It’s good software.
I’m also tinkering with Elixir, which is not really a typed thing. Erlang’s dialyzer is similar in concept to Flow, but different in implementation. Both allow gradually introducing types to systems.
I’m more interested in types stuff for frontends than backends. I want some assurance, in the wild world of browsers and devices, that my systems are soundly structured. Types buy me that. Backends, I feel, benefit from a little more leeway, and are often faster to deploy quick fixes to, such that I can get away without the full rigor of types.
Either way, I’m jazzed about today’s tools that help me think better as I build software.
2 thoughts on “Type tinkering”
ooh good, please tell me what the point is (other than security and efficiency.)
i know there are times when fast and efficient count for so much– i get that, types are good then. and i also know they can save your butt sometimes, and are critical for things that nasa works on.
but other than that, what do they really do for you?
when i started coding, types were explicit. the idea of dynamic typing for example, was the sort of thing where you wondered if it would be possible.
Comments are closed.