I don't think the fact that React was used on the server is particularly relevant, although it can help reduce some angst perhaps.
-
-
Replying to @wycats @jaffathecake and
it is extremely relevant! I use angular (you could use any f/w) even for static-ish SSRed pages/sites because I can use the same
2 replies 0 retweets 0 likes -
Replying to @jayonlines @wycats and
mental model to build any web app - classic or SPA. The point is that I'm using a framework for what it's supposed to do -
1 reply 0 retweets 0 likes -
Replying to @jayonlines @wycats and
make development fun & fast. And today's frameworks (all of them) actually allow you to get the best of both worlds.
1 reply 0 retweets 0 likes -
Replying to @jayonlines @wycats and
That's why I think that the clickbaity title actually does a disservice to the underlying principle that should come out from that article
1 reply 0 retweets 1 like -
Replying to @jayonlines @wycats and
aww, I tried to avoid being clickbaity. It could have been "Netflix removes React, gets faster. Where now for React??"
3 replies 0 retweets 1 like -
Replying to @jaffathecake @wycats and
lol - I have nothing against clickbaity titles. I just pointed out that it could potentially have been the trigger for the outrage.
2 replies 0 retweets 0 likes -
Replying to @jayonlines @jaffathecake and
A better (also clickbaity) title, imo - "Netflix discovers a better way to make React apps more performant"
1 reply 0 retweets 0 likes -
Replying to @jayonlines @wycats and
That kinda buries the intent of the article – addressing the outrage at Netflix's announcement.
1 reply 0 retweets 0 likes -
Replying to @jaffathecake @wycats and
aah .. I see. All my comments were with respect to the Netflix tweet actually. I see how I didn't make that clear. Sorry about that
1 reply 0 retweets 2 likes
Makes more sense!
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.