Failure
Posted by Jacques Chester on Friday, December 14, 2007
Something went horribly, terribly wrong last night. The server is all kinds of weird and frankly I am amazed it is working at all. It will let me log in but fails to reboot when told to.
Over the fold is a diagrammatic explanation of my feelings on the matter.
Update: “Epic” is only world left to describe all the things that went wrong today, both in the first place and during the attempt to fix things. Today it was a mix of “why the **** did they do THAT?” and “GOD I HATE WORDPRESS episode 579,294″.
From icanhascheezburger.com.
ShareThis
This entry was posted on Friday, December 14th, 2007 at 9:06 AM and filed under Site News.
Follow comments here with the RSS 2.0 feed.
Post a comment or leave a trackback.
Thanks Jacques - you know we love you for it, if that is any consolation
Posted on 14-Dec-07 at 11:55 pm | PermalinkPerhaps you should take Harry Clarke’s advice.
http://kalimna.blogspot.com/2007/12/keeping-it-simple-computers-blogging.html
Posted on 15-Dec-07 at 12:21 am | PermalinkYou are left no choice but to write your own blog software in lisp. I suggest you run it as emacs on the server with a clubtroppo blog plugin.
Only smelly hippies from MIT can be trusted now.
Posted on 15-Dec-07 at 5:48 am | PermalinkI have installed and maintained many WP blogs and do not agree with what you say about WordPress. I have also been an IT professional since 1969.
Problems with WP are mostly the fault of users fiddling with it, using plugins which have not been adequately tested or installed, badly designed themes which are not fully IE/Firefox compatible, or additional layers such as K2.
The real problem with blogs such as Troppo, LP etc. lies in the poor choice of web hosts (usually chosen on price alone) and other hardware ’solutions’. This is exacerbated by well-meaning amateurs administering the hardware and/or software.
Notice that LP is running without problems in exile at Wordpress.com because no one can fiddle with the software and it is running on professional hardware selected to take the load.
Posted on 15-Dec-07 at 7:28 am | PermalinkYour experiences have differed from mine. I have come across genuine boneheaded bugs. The worst part is when they are in the bug tracker marked closed with worksforme. I have come across two such bugs in just the last few days, including the aforementioned forkbomb yesterday.
Essentially you are saying that if we’re prepared to give up plugins everything will be hunky-dorey. You’d be right, though that just avoids the issue by trading away the major selling point of Wordpress.
Let me say that again: the major selling point for Wordpress is not Wordpress. It is the ecosystem around Wordpress. The program itself is not that good, and the project that runs it pay lip service only to fixing bugs. And yes, I do read the mailing list and use the bugtracker. It still doesn’t help.
Posted on 15-Dec-07 at 3:17 pm | Permalinkcam;
I actually have tooled around some erlang code, in a vain attempt to avoid scaling problems a bit. The problem is that a lot of my problems with Wordpress are institutional — part of how the project operates. There’s more that should be done than I can do.
Posted on 15-Dec-07 at 3:24 pm | Permalink