There's an *awful lot* of JavaScript that exists solely because the developer didn't know CSS well enough.
It is, but Rule of Least Power becomes an API design guideline rather than a PL guideline.
-
-
Haskellers would say don't pass the state or io Monad around gratuitously. RoLP is saying if a PL makes that hard, don't always use it.
-
the problem of ROLP is that you can't do anything in that nice little edge case where you do need more power to save you days of work

-
But if you model it using types, you'll see that the Io Monad has now leaked into the rest of your program ;)
-
Which will take days to refactor.
-
I feel like it's a pipe dream to have an ergonomic general purpose PL that satisfies the spectrum of PoLP but won't dismiss it out of hand.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.