Convert the whole site to use Pelican instead of Jekyll
This commit is contained in:
23
content/blog/2012-06-14-wordpress-madness.rst
Normal file
23
content/blog/2012-06-14-wordpress-madness.rst
Normal file
@@ -0,0 +1,23 @@
|
||||
Wordpress madness
|
||||
#################
|
||||
|
||||
:date: 2012-06-14T06:40:12Z
|
||||
:category: blog
|
||||
:tags: wordpress,ranting
|
||||
:url: blog/2012/6/14/wordpress-madness.html
|
||||
:save_as: blog/2012/6/14/wordpress-madness.html
|
||||
:status: published
|
||||
:author: Gergely Polonkai
|
||||
|
||||
I’m a bit fed up that I had to install `MySQL <http://www.mysql.com/>`_ on my server to have
|
||||
`Wordpress <http://wordpress.org/>`_ working, so I’ve Googled a bit to find a solution for my
|
||||
pain. I found `this <http://codex.wordpress.org/Using_Alternative_Databases>`_. I don’t know
|
||||
when this post was written, but I think it’s a bit out of date. I mean come on, PDO is the part
|
||||
of PHP for ages now, and they say adding a DBAL to the dependencies would be a project as large as
|
||||
(or larger than) WP itself. Well, yes, but PHP is already a dependency, isn’t it? Remove it
|
||||
guys, it’s too large!
|
||||
|
||||
Okay, to be serious… Having a heavily MySQL dependent codebase is a bad thing in my opinion, and
|
||||
changing it is no easy task. But once it is done, it would be a child’s play to keep it up to
|
||||
date, and to port WP to other database backends. And it would be more than enough to call it 4.0,
|
||||
and raising version numbers fast is a must nowadays (right, Firefox and Linux Kernel guys?)
|
Reference in New Issue
Block a user