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

This seems similar to attempts to rewrite a complex code base to be simpler, more consistent, and easier to understand.

In practice, a lot of the quirky, wonky code is there to fix an actual bug that was encountered, and taking it out re-introduces the bug.

How do we know eliminating some of the complexities of current laws won't re-introduce some of the problems those complexities were trying to solve?



> How do we know eliminating some of the complexities of current laws won't re-introduce some of the problems those complexities were trying to solve?

The other side of that coin is: are the bad outcomes produced by the current codebase bad enough that we will replace them and accept the risk of re-introducing the other bugs?

Alternatively, the entire codebase is in English (+/-) so one could document the bugs that changes are attempting to address.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: