[kamaal]

Have literally seen a 'architect astronaut' crap on Perl in some 2 hour long call, and eventually had his way with getting the management to approve Java. This was mid-2000s

When our team initially budgeted it, 4 guys over 6 months were enough to get this over the finishing line. The java team took over took more than 3 years, and close to 30 people. It was a AbstractClassFactoryFactorySingletonDispatcher mess with spring decorators all over. Which quite honestly was quite ironic because the original case against Perl was it was hard to read.

The java code was easily 30x more verbose, no body at the end knew how to maintain it. It was all about the guy getting to own his own team, promotions, bonuses, raises etc.

Have seen the same story repeat over and over again, everyone knew they wanted Python because they could get to inflate their headcounts.

Its one of things about tech, its not the good tech that wins, its the tech that helps with office politics wins at the end of they day.

After golang came along a lot of these java things too went out of fashion. Curiously enough golang does feel a lot perly to use. And Python has long moved away from its minimalism activism days. To that Python has transformed into the same feature bloat it once accused Perl of.