There's an *awful lot* of JavaScript that exists solely because the developer didn't know CSS well enough.
-
-
This, I avoid a CSS in complex situations because it doesn't abstract/encapsulate well in my experiences.
-
That's a problem I'd like to address through better CSS tooling.
-
We have been using SASS for ages, but I don't see much progress on this. Do you have ideas on how to move forward on this?
-
I agree with every word you said, but with real deadlines people don't have days to figure out CSS way, when it can be done in JS in 5 min.
-
Some situations are quick in JS in 5m, some situations introduce tons of complexity in JS in 5m you pay off for years and years.
-
Agreed, but under pressure many cave in and forget big picture. We need better culture and better tooling. Help dev fall into pit of success
-
Cause of my career man :)
- 1 more reply
New conversation -
-
-
Given a sufficiently good type system, is the rule of least power still applicable?
-
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.