The US code is 22 million words. [1] is a good visualization of it. I'd wager there are tons of redundancies that could be refactored. That being said, I'd also wager that careful refactoring is not on DJT's mind. More slash-and-burn the parts he doesn't like.

[1] https://twitter.com/harlanyu/status/165184504527462400/photo...

The US Code is law, not regulation, and so is completely irrelevant here. What you want to cite is the Code of Federal Regulations, which is much larger than the U.S. Code.

Of course you provide no reason at all except an unsupported assumption to believe that the size of the completely wrong thing that you cite is an indicator of unnecessary complexity, and the fact that you cite the completely wrong thing is a pretty good sign that you have zero knowledge of the domain from which to form a judgement.

I spoke in generalities. You are absolutely correct. I have no claim to being an expert or even a layman. What I do know is that once a description of any thing exceeds a certain threshold, there are bound to be redundancies. Think of it in terms of codebases for large softwares. The Linux kernel is approaching 20 MLoCs. I'd wager heavily on there being a different architecture delivering the same functionality with less code to describe it. Proving it would be a tremendously hard task, far outweighing any gain from such a bet.

"If this rule needs to be broken, then bring me a proposal for why" is a good addition. The idea should be to swap the default to less-complexity rather than more-complexity. If more is less, then it should be possible to write a succinct justification for it.