Instead of answering algorithms challenges, the challenge is to own a device fast enough for scrolling to work 
-
Show this thread
-
Replying to @danluu
Years back, I remember thinking that "modern"/complex websites are so terrible to use on a phone, surely practices will change.
1 reply 0 retweets 1 like -
Yet apparently the trajectory is that 2020 websites will feel on a then-current desktop PC as 2012 websites did on a 2010 phone.
1 reply 0 retweets 2 likes -
TBF, the capabilities of browsers are rapidly expanding, and there's greater demand than ever for feature-rich Web apps.
2 replies 0 retweets 0 likes -
Replying to @firagabird @danluu
Features that are completely wasted if the app is effectively non-responsive on everything but a high-end desktop PC.
2 replies 0 retweets 3 likes -
I'm not against features, but first and foremost, the basic user experience has to work.
1 reply 0 retweets 1 like -
My primary browsing/email machine is a Skylake laptop I bought last year, and I'm a well-off software dev who can afford to buy new machines
1 reply 0 retweets 0 likes -
every 2-3 years no problem. If your website doesn't work without severe stutter on a <1-year old upper-midrange machine, *who is it for*?
1 reply 0 retweets 1 like -
That's a crazy high cut-off to set. (And probably not intentional.)
1 reply 0 retweets 0 likes -
Replying to @rygorous @firagabird
IME, being "feature rich" and "dog slow" are virtually uncorrelated. The page we're discussing is a great example of that.
2 replies 1 retweet 6 likes
See also asana and zulip, which are so slow that speed is one of the primary reasons I hear that people leave or can't stand the apps.
-
-
I recently paired with someone on a "slow" machine, only 10x faster than the minimum requirements to run Quake 3...
1 reply 0 retweets 0 likes -
The machine that can run 10 copies of Q3 can't handle any single app mentioned in this thread, a todo list a chat app, and a static site
0 replies 0 retweets 4 likes
End of conversation
New conversation -
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.