2 ms·
"a "write only" language" A cousin of that problem is it doesn't matter how many years ago "Modern Perl" was written, today MySQL still doesn't support transac
by VLM 10y ago
"a "write only" language"
A cousin of that problem is it doesn't matter how many years ago "Modern Perl" was written, today MySQL still doesn't support transactions.
Not a non-sequitur, in that to this day you'll still run into people swearing mysql doesn't support transactions because last time they looked into it in '94 it WAS true, mysql didn't add transaction support until the late 90s IIRC. Likewise its a law that all Perl discussions ignore everything that's happened in Perl development in the last 20 years. If no one has written code like that since '96 it just doesn't matter to the discussion.
- gotofritz 10y agoI actually started drifting away from Perl not that long after it became object oriented, it kind of felt like a bad fit, it lost its "perlness". I assumed that even if it had evolved it would be further along the same path so I wasn't interested. But more importantly, NOBODY I know and rate has come to me and told me "You know what? Perl has moved on, it's actually become a wicked language, you should give it a shot". Whereas that has happened to other languages that I had given up on (ActionScript, JS, PHP) and I had no problem going back to them. As for MySQL, seriously? Are there people who think that in 2016? I find it hard to believe. One thing is a programming language, but for a RDBMS it's just a matter of time before all the feature developer wants get added. With MySQL it's just a matter of "so what's version is it now, have they added them yet?"