Yeah! And integers do way too many things as well. Counters, indexes, number of orange slices in an orange, there's just no end to the wacky things people try to make integers do, and it's impossible to keep track of it all when looking at code. And floats? Don't get me started on floats. Angles, probabilities, weights, heights, degrees of separation from Kevin Bacon ... I'm getting dizzy just listing all these different things that floats do.
It's a big problem, because there isn't an easy way to fix it in every programming language known to man, and someone needs to write more articles about this to get more hits for their sites.
I think the article makes a good point, but perhaps I'm over-interpreting. It's not that we should stop using strings. It's that we should use the type system to separate different kinds of strings and enlist the compiler's help to detect incorrect mingling of them. So for example a symbol type would only permit strings that contain ASCII letters, underscore and digits, and concatenation with / conversion to plain strings would be limited.
It's definitely a rule that can be taken so far that it is counterproductive, but I think it's good practice to thbk about how I could use something other than a raw string ( even if it's just a constant defined somewhere )
The analytic continuation of KB(x) to the complex plane subject to a superconvexivity constraint is unique but doesn't necessarily have a straightforward geometric interpretation
You joke, but Rails actually does make Integer do too many things lol. I’d argue they’re useful things, but it does so by patching the core Ruby Integer class :p