Comment by wyager
12 hours ago
> You can do this in basically any language.
You can do it in Assembly. That doesn't mean it's cost effective.
12 hours ago
> You can do this in basically any language.
You can do it in Assembly. That doesn't mean it's cost effective.
And categorically: the issue isn’t what “I’d” do, my habits often match my habits, it’s what other project members will be doing (including future degenerate versions of myself assumed to be some combination of busy, tired, stressed and drunk).
The Confucian philosophy that people act like water coming down a mountain, seeking the path of least resistance comes to play.
Haskell, OCaml, F#, and their ilk can yield beautiful natural domain languages where using the types wrong is cost prohibitive. In languages without those guarantees every developer needs discipline to avoid shortcuts, and review needs increase, and time-pressure discussions rehashed.
Costs are a skill issue ;-)
You demonstrate well the problem: yes anything that is computable can be than in any computation system. That's not what discussions about tooling are about.
If a tool can help enforce some ways of doing things, or if it doesn't constrain people much, that has consequences for the type of work that gets done with them and the systems you encounter running out there that you might be invited or find the need to work with.
"I can do it" is exactly the wrong answer. "How can I guarantee that others will do it" is the point being made.