[josefresco]

So let me get this straight. Some developer/guy spends 5 minutes trying to theme a WordPress website for himself and decides to write an article bitching about it instead of actually reading some documentation or the thousands of Google results from countless other developers who have done the same and much more? The first commenter pretty much sums up how much this guy knows about WP themeing (hint: nothing).

This almost happens to me all the time but I know better. I spend 10 minutes with a new program, decide it's batshit crazy but instead of posting a lame article I have the wisdom and experience to stop and tell myself "I'm just a noob" and will probably embarrass myself.

[CyrilMazur]

And what are this so-called thousands of Google results from countless other developers who have done the same and much more? Dirty workarounds that shouldn't be necessary if WordPress had been made properly in the first place. That's only what the author says: although WordPress rocks to propel blogs, it's far from being made of good code.

[slouch]

you can rewrite a lot of the WP functionality by writing a plugin. if your plugin is popular, it's modifications may be absorbed into the core software that is distributed at wordpress.org. you're calling open source development dirty workarounds.

[CyrilMazur]

If it worked like that, WordPress would already be OOPed and MVCed isn't it?

[CyrilMazur]

Nope, I don't follow up the WordPress development at all so I can't judge

However, I can't believe none of the WordPress developers has never suggested to rewrite it using nowadays technologies?

[slouch]

i'm not sure i follow. are you suggesting that the wordpress development team discourages participation?