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

Either take the biggest one or render in chunks.




Saddling some guy on an underpowered Chromebook with a crazy large static allocation, just because you want your programme to also support some crazy large screen that might come out in 2035, seems a bit silly?



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

Search: