Can you clarify what you consider "splitting"? I'm interested in knowing more.
I'm of the opinion that there's only so much that browsers can do, there's ways of serving the content like lazy loading that still get you the full content but help the browser do less work. I also think that it's responsible to use those techniques where required (low end network conditions on underpowered devices like phones, for example) as long as the experience is not broken (which needs careful implementation and consideration!). Whatever we need to reach as much people as we can! (and make google not redirect wikipedia to googleweblight on certain countries) On Wed, Jan 13, 2016 at 12:29 PM, Bernardo Sulzbach < [email protected]> wrote: > Thanks, Joaquin. I image how tiresome waiting 3 minutes of loading > (for a web page!) must be. > > I just hope that no one decides that this makes a good reason for > "splitting" the Obama article. I would expect more improvements from > the browser itself, more on-the-fly rendering of the page as you get > data. > > I've seen forum threads (think about GitHub issues) reach gargantuan > sizes (way more than a mebibyte). I think it is the browser's job to > handle these scenarios. > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
