Live data from Hacker News

Wordless: stop writing Wordpress themes like it's 1998.

github.com

81–87 of 87 posts

Re: Wordless: stop writing Wordpress themes like it's 1998.

#81
post #74
post #62

Earlier quoted context omitted.

Yeah, but if a client wants something custom you're stuck either modifying an existing plugin, or creating a new one, and creating Wordpress plugins is a godawful mess.

Care to expand on 'godawful mess'? It's pretty straightforward and easy imo.

Wordpress provides little structure of framework for your plugin. There are plenty of hooks and functions to use, to integrate with each step of the rendering process, but other than that, you're on your own. Each plugin tends to provide it's own miniframework... or lack of one. A plugin tends to look like it's own self contained PHP web site from 2005.

Trying to integrate several different WordPres plugins is a challenge, as they each tend to be written in their own style.

Re: Wordless: stop writing Wordpress themes like it's 1998.

#83
post #74

Earlier quoted context omitted.

Care to expand on 'godawful mess'? It's pretty straightforward and easy imo.

Wordpress provides little structure of framework for your plugin. There are plenty of hooks and functions to use, to integrate with each step of the rendering process, but other than that, you're on your own. Each plugin tends to provide it's own miniframework... or lack of one. A plugin tends to look like it's own self contained PHP web site from 2005. Trying to integrate several different WordPres plugins is a chal…

It's php, there are a lot ways to write code that result in desired functionality - that's a plus in my book. There are thousands of differents types of programmers writing plugins for WordPress - more than any other open source project, so it's darn obvious there are going to be lots of different ways plugin writers approach their plugins.

Having said that, there are guidelines and best practices found in the codex (for one, all the hooks and filters that are available which are generally well documented) and there is some quality control when submitting plugins to the WP directory. In addition to that there is a fantastic handbook (professional WordPress plugin development) that gives both beginners as well as veterans a healthy education in the best ways to write plugins. And there's a big blogging community writing detailed tutorials.

I'm not sure what you mean with integrating plugins - what does that accomplish? Most plugins run fine when running concurrently on an install.

A lot of these criticisms toward WordPress in this thread are a bit ridiculous if you ask me. Yes it's written in PHP, big deal. Yes there's a lot of code that if written afresh today would look different. Yes there's variable quality in code written by various plugin/theme developers. At the end of the day WordPress is plain accessible for people - and that is a big reason for its success.

I started out years ago knowing zero about code to where I am today. My first plugin was shit and know I'm getting pretty good at it. Because developing on WordPress has been so much fun I taught myself Php, html, css, javascript (including ajax and jquery). Clearly, I'm not the only one as it is the most active community of all the CMS choices out there - and a lot of people are making a living thanks to it.

Re: Wordless: stop writing Wordpress themes like it's 1998.

#84
post #62
post #60

Earlier quoted context omitted.

Just as an example, it is better to make an app like BaseCamp or Campfire with Ruby on Rails than WordPress. But I can learn enough in a matter of weeks to make something like the P2 Theme ( http://www.p2theme.com ) with WordPress; god knows how long it'd take me to go from completely zero programming knowledge to the level required to build the same thing in RoR

Yeah, but if a client wants something custom you're stuck either modifying an existing plugin, or creating a new one, and creating Wordpress plugins is a godawful mess.

See, I still disagree. Working with WordPress has been nothing but (relatively) easy for me, even when making relatively complex plugins.

No one is arguing that WordPress is better, necessarily, than a custom build. But reality trumps theory. Theoretically a perfect diet may be out there, but if you can't afford it and won't adhere to it, for example, a less-theoretically-perfect diet that you can afford and can actually follow is better.

A lot of times I or my client can't afford a developer for a custom app. WordPress solves that problem, and I think it's only getting better, simpler, and more stable with time (as all open-source projects kinda do).

Re: Wordless: stop writing Wordpress themes like it's 1998.

#85
Jesus Christ. Can we stop all this "PHP Sucks" nonsense? We get it, a language like ruby is better for you. And hell, there's not much of an argument against how PHP looks; Ruby and Python, to me, look much much nicer.

But complaints about its technological capability are completely false. It's super easy and simple to learn, and even a HTMl/CSS guy like me is able to build pretty powerful, dynamic websites and simple apps with WordPress and (gasp!) PHP.

Before you start shitting on PHP, realize that a) you're arguing over a programming language lol b) it's been around for a long time and thus has a huge community, good documentation, lots of books and resources, and comes preinstalled on a lot of servers, etc, c) great applications like MailChimp, Wikipedia, Digg, and FaceBook use PHP extensively d) the learning curve is low e) yeah, it is ugly. But its easiness to learn got me into quasi-programming with WordPress, and since seeing .rb files I've begun to get curious about ruby. But the basic programming knowledge is there from PHP experience and facilitates learning other languages.

Sorry, it's just frustrating to see people making fun of a language and criticizing the people who work with it.

Re: Wordless: stop writing Wordpress themes like it's 1998.

#86
post #46

"1. Your development machine needs a ruby environment" C'mon. All this work and no PHP/Wordpress developer that will ever use this. What a shame.

I'm a PHP developer and use HAML and SASS in PHP projects. Why? Because to build a website with these tools speeds up my development time. You cannot forget anymore a closure. You can forget all the 'echo' calls. You can forget all that horrible "nested" css rules with tons of repetition. You can forget all that tags everywhere around the HTML code. Yes the cost to pay for this is ruby. Well, it took me about 20/30 m…

I'm not referring to HAML and SASS, I'm referring to Ruby.

HAML and SASS are good thing and to integrate it with Wordpress is great. However, if you want Wordpress developers to make use of your efforts, cut the dependency on Ruby since no Wordpress developer will be willing to get up and running (or even installing) Ruby.

Re: Wordless: stop writing Wordpress themes like it's 1998.

#87
post #83

Earlier quoted context omitted.

Wordpress provides little structure of framework for your plugin. There are plenty of hooks and functions to use, to integrate with each step of the rendering process, but other than that, you're on your own. Each plugin tends to provide it's own miniframework... or lack of one. A plugin tends to look like it's own self contained PHP web site from 2005. Trying to integrate several different WordPres plugins is a chal…

It's php, there are a lot ways to write code that result in desired functionality - that's a plus in my book. There are thousands of differents types of programmers writing plugins for WordPress - more than any other open source project, so it's darn obvious there are going to be lots of different ways plugin writers approach their plugins. Having said that, there are guidelines and best practices found in the codex…

My point was that raw PHP is a little too unstructured and powerful for the tasks that many plugins are made to accomplish.

By integration, I mean adopting plugins from various authors and making them work as part of your theme. There are all sorts of issues involved... random visual design, clashing HTML doctypes, possible poor coding, adding functionality, fixing security issues... creating a coherent, secure and functional site by piecing together various WordPress plugins is not as easy as installing some plugins and whistling off into the glorious sunset. Simply finding a plugin for a certain purposes which actually works can be a challenge.

I wasn't attempting criticize WordPress or PHP in general, just the quality of the average plugin and the lack of consistency and order.

Post reply on HN