1: But the tech community is obsessed with new "paradigms" that "change computing forever". The enthusiasm for specialized solutions in this
-
-
2: thread is inconsistent with the way the tech community insists that "new paradigms" and "de facto standards" justify herd adoption of
1 reply 0 retweets 1 like -
3: popular libraries. Obviously there is some value in sharing, but "X is the new jQuery, it's already won!" argues that we should be
1 reply 0 retweets 1 like -
4/4: all driving towards one solution, which leads to the problem this thread is complaining about.
2 replies 0 retweets 1 like -
Replying to @wycats @jlongster
I think you missed the subtle distinction I made elsewhere about "generalized" vs "generally applicable". I want latter, not former.
1 reply 0 retweets 1 like -
Perils: "If you have a procedure with ten parameters, you probably missed some"
2 replies 0 retweets 0 likes -
The problem is one of deseminating techniques. Each parameter is an affordance, but building blocks don't necessarily invite you to use them
1 reply 0 retweets 0 likes -
This is the fundamental problem with unix philosophy etc for popular projects: it requires users to have skill and taste to use them well
1 reply 0 retweets 0 likes -
And this isn't about trashing some particular programmers: even experts lack skill and taste in new areas, so gravitate towards affordences
1 reply 0 retweets 1 like -
Replying to @BrandonBloom @jlongster
Fair. I'm basically saying that the tech community objects to solutions for small domains ("frameworks"), instead pushing for paradigms
2 replies 0 retweets 0 likes
React isn't a front end web framework, it's a computing paradigm. This doesn't leave space for domain subtlety, aesthetic considerations etc
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.