4 ms·
slinging around "web trying to be native is bad" in the way the author does is such a thoughtless argument: just because something exists in native land (a land
by RubyPinch 11y ago
slinging around "web trying to be native is bad" in the way the author does is such a thoughtless argument: just because something exists in native land (a land of a lot of well paid researchers and designers, etc etc), doesn't make the idea bad for everywhere else. Maybe the idea is just a plainly good design decision?
(I mean, do you have fond thoughts of the entire page flashing white, then pieces of the page bouncing around the screen as they try to position themselves based on content that hasn't loaded yet?)
- JustSomeNobody 11y ago"(I mean, do you have fond thoughts of the entire page flashing white, then pieces of the page bouncing around the screen as they try to position themselves based on content that hasn't loaded yet?)" You mean like it does now?
- RubyPinch 11y agoyes, which is why "imitating native", aka not reloading the entire page, is seen a lot more on sites like facebook and twitter (the ui stays the same as the main page reloads), this is done to provide a more comfortable experience, sans screen flashing rave party navigation transitions (more of this horrible ugly "native" stuff) is standardizing a mechanism for this