I don't think any frameworks force you in this sense. Calling this a React advantage is strange. This whole thing is strange.
-
-
Replying to @wycats @jaffathecake and
Frameworks (“toolkits” in old days) can take over whole app & its runtime, make it big, slow, non-progressive. True fact!
#Notallframeworks3 replies 1 retweet 7 likes -
Replying to @BrendanEich @jaffathecake and
My app,
@skylight, using "heavy framework" Ember, has used a static login page from the beginning. "Not being punished" feels like spin.1 reply 0 retweets 12 likes -
Replying to @wycats @jaffathecake and
Must everything be politicized? I'm describing known problem, Jake too. I've seen it back to the '80s. Good of Ember to avoid but it's real.
3 replies 0 retweets 10 likes -
Replying to @BrendanEich @wycats and
I don't see anything being politicized. Why is it political to respond that frameworks don't punish users, with examples.
2 replies 0 retweets 0 likes -
Replying to @petermbenjamin @wycats and
I was replying to Yehuda, who first said "spin". This is really simple: not all frameworks or libraries have the flaw we're discussing.
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @petermbenjamin and
Because "you can use a static login page" has nothing to do with "punishment" and the idea that it's specific to React is spin ;)
2 replies 0 retweets 1 like -
Replying to @wycats @petermbenjamin and
Jake wrote "React doesn't punish you for doing some stuff without React". I didn't see an attack on Ember. Was it a strawman? Not in '80s!
1 reply 0 retweets 1 like -
Replying to @BrendanEich @petermbenjamin and
He said it "reflects well on React", which implies relative to something else.
2 replies 0 retweets 1 like -
Replying to @wycats @BrendanEich and
That was in response to the React fans that were angry. I was saying "no, this should be celebrated"
3 replies 0 retweets 6 likes
"React doesn't punish you for doing stuff w/o React" is just such weird framing for "you can make your login page w/o React" but nuff said
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.