I don't think the FCC is arguing that they don't want people's own distribution running along side a WiFi device, but rather, as WiFi chipsets become more "Software Defined" - rewriting the code in them is essentially the same as "modifying the radio".
The best analogy are the RTL HDTV over-the-air capture dongles for software defined radios. Guess what? They're generic radios which only do TV decoding via software - so people write NEW code and suddenly you can use them to do (and I dare say ANYTHING) that any sort of radio receiver could ever be made to do.
This is okay (and legal) with a receiver - they just don't want to to happen with transmitters. What would happen if anyone could do anything they want on the airwaves?
The counterargument is going to be "but they're not cracking down on MODIFYING the radio - just leaving the radio OPEN to being modified". This is expressly prohibited (and has been for a very long time) by the FCC - long before software-defined stuff. Lots of devices like Family-Band radios (and other licensed transmitters) are REQUIRED to be manufactured with things like "non-replaceable antennas" - which make user-modifications more difficult, because they are prohibited (unless done by a [ham] licensed operator).
The alternative would be nasty - let's break out a protracted set of functions, variables, loops, etc to process this piece of text in a more "readble" way? No thanks - let me bang-out the regexp and be done.
Also - At least Perl uses a normal open/close (braces) to begin and end a scope - unlike Python - which relies on the number of leading spaces. (I've been using Python for years - can handle that - but still think it's a very bad idea).
For me - Pearl's biggest downside has been that the world has simply gone to Python largely, and so have I.Whereas I used to love Perl, I find it hard to keep switching back-and-forth.
That being said - I miss the ease at which Perl can fork a subproces, then scrape and parse it's output. Yes you can do this with Python - but it does take more keystrokes. From a linguistics point of view - it comes down to Information Density. Thus, we can argue that Python looks cleaner, but Perl's code is denser.
Luck, that's when preparation and opportunity meet. -- P.E. Trudeau