Been thinking about this. "Generalized" is usually the wrong thing anyway. Every inessential option is a failure to make a design decision.https://twitter.com/jlongster/status/879332102931722241 …
-
-
I think you missed the subtle distinction I made elsewhere about "generalized" vs "generally applicable". I want latter, not former.
-
Perils: "If you have a procedure with ten parameters, you probably missed some"
-
The problem is one of deseminating techniques. Each parameter is an affordance, but building blocks don't necessarily invite you to use them
-
This is the fundamental problem with unix philosophy etc for popular projects: it requires users to have skill and taste to use them well
-
And this isn't about trashing some particular programmers: even experts lack skill and taste in new areas, so gravitate towards affordences
-
Fair. I'm basically saying that the tech community objects to solutions for small domains ("frameworks"), instead pushing for paradigms
-
I'm confused by this tweet. Framework vs Library and size of domain or solution space are orthogonal as far as I can tell.
End of conversation
New conversation -
-
-
I like to think about abstract ideas this way (one way data flow), but for implementations, let many flowers bloom!
-
Even ideas are extremely subject to domain considerations. Frankly I think the react community is far too comfortable with One True Paradigm
-
For me, react shines as a way of boiling down constraints of UI design, especially on the web. Different constraints yield diff solutions.
-
React Native, sure maybe. React VR:
. It's certainly POSSIBLE that the constraints yield the same results, but we should check.
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.