Dynamic typing is the source of very amazing errors, see JavaScript.
tux0r
Feel free, it’s still out there!
I still write more Perl than Python these days.
Still easier to refactor than Python. ;-)
For all of those, Lisp is the more logical choice. Plus, whitespace as syntax is the worst possible design decision.
There still is no documented way to migrate an existing WordPress to PostgreSQL. The PostgreSQL plugin assumes a fresh installation, everything else is not assumed to be there.
It still is, as that’s what the developers use.
nextCloud becomes notably faster when you migrate from MySQL to PostgreSQL.
I rewrote the last remaining MySQL-based software of mine this year because I didn’t want to have MariaDB just for this one tool. Everything else had already been migrated. PostgreSQL is much faster in my tests.
Some of our customers rely on Oracle’s database system, because history. Sadly, we can’t teach them.
MySQL refugees = those who ran to MariaDB when MySQL was bought by 'Orrible and now need another new home. Accidentally, PostgreSQL has grown support for some of MySQL on recent versions.
You can make embarrassing mistakes in virtually any programming language that's not too esoteric.
When I still used Python for prototyping (today, I usually use Go for that), it happened much too often that I did this:
In Lisp, however, both errors are much harder to make (not even considering GNU Emacs's superb auto-indentation - which is what most Lispers use these days, as far as I know):