Hacker News new | past | comments | ask | show | jobs | submit login

One can't always introduce a multitude of shitlists into different places in the code. This can impact performance and readability; and perhaps even more importantly - if the language used is not high-level with reflection capabilities, you will be counting on callers' participation in calling the semi-deprecated API with truthful "usage key" for looking up on the shitlist. Who's to say nobody reuses authroized keys for expediency?



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

Search: