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

Well, unreasonable now was probably perfectly reasonable at the time of implementation. Perhaps they even have or had a plan to improve upon it, but given other tasks (ES6, etc.) it hasn't been given much priority.

I mean, why would they fix it with high priority if the engine already has reasonable performance and the benchmarks are happy as well?



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

Search: