@dan_abramov pretty sure @feross is trying to say (or at least i would argue) that wikipedia has nothing to gain from switching to react
-
-
Replying to @dan_abramov
@dan_abramov@feross i don't see how wikipedia could ever benefit from a SPA though?2 replies 0 retweets 2 likes -
Replying to @sebmck
@sebmck@dan_abramov@feross In it’s current state of UI / UX I see no benefit, but doing a SPA could open doors for visual persistence.1 reply 0 retweets 1 like -
Replying to @AndrewDelPrete
@andrewdelprete@dan_abramov@feross what does visual persistence mean?1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@dan_abramov@feross One of the benefits of SPA is having a frame like persistence where pieces reload without everything else.1 reply 0 retweets 1 like -
Replying to @AndrewDelPrete
@andrewdelprete@dan_abramov@feross wikipedia loads fast enough though, i have less than 1s latency when clicking a link. it feels instant.3 replies 0 retweets 1 like -
Replying to @sebmck
@sebmck@dan_abramov@feross So if Wikipedia has some neat UX in mind where comps persist when traversing their site, SPA could be useful.1 reply 0 retweets 0 likes -
Replying to @AndrewDelPrete
@andrewdelprete@dan_abramov@feross we've been able to do that with the web forever though, it's called frames or pjax1 reply 0 retweets 2 likes -
Replying to @sebmck
@sebmck@dan_abramov@feross Great point. I don’t think everything needs to be an SPA. I’ve ran into perf issues myself with larger apps.1 reply 0 retweets 0 likes
@andrewdelprete @dan_abramov @feross the problem is that not all websites need to be "web apps". wikipedia is fine as it is. no fanciness.
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.
he/him 