Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Usable has many meanings and to me personally, a website that isn't very responsive and lags when you scroll doesn't seem very usable.


Did you read the article and the comment I was replying to? Both basically rendered 40k element HTML <table>s. Difference is, the Google UI lags because it is hampered by browser painting/layout computations taking forever, despite the <table>s in discussion having near-identical complexity, so one can conclude the Google UI bug is more-or-less a bad interaction between the UI's CSS and the browser rendering engine.

So, pray tell, how does parent comment decrying UI developers for supposedly not just rendering HTML tables make any sense in light of this context? It is just sass from someone who likes to rail against UI development, there is no insight




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: