@mjgardner
There were warnings about using this even when I was an active Perl programmer (2009-2016). Not sure why you’d choose to put such code in production, at the time? Kinda like hooking your business to Google or Microsoft: nope — none for me, thanks. 🤷🏻♂️
@chessert Apparently not everyone was as tuned in as you were. At #Perl v5.10’s introduction I agreed with https://mastodon.social/@gruber/112125241870511100 that given and when sure looked nice and readable, and the smartmatch ~~ magic was inspired by what was then optimistically called #Perl6, so it had to be okay, right?
I never got around to doing enough git blame code archaeology to determine Patient Zero while I was at that doomed company that went all-in.
@mjgardner
Yes. I had a couple unpleasant encounters with the ~~ operator when we were forced to upgrade our production Perl libraries, due to Debian releases.
The company's entire online (web app) codebase was in Perl, well after it should have been retired. It probably still is??? I tried to push them toward Python, or even PHP, but the "head shed" had been there since the 1990s, and any significant change was viewed as a loss of control. 🙄
@chessert It’s all ultimately about culture and politics, relationships and people, and how they do or don’t change over time. #Programming languages are just the fashions those relationships wear when we instruct our machines about them.
Add comment