Live data from Hacker News

Dear WordPress

ma.tt

41–50 of 80 posts

Re: Dear WordPress

#41
post #6

I can appreciate what wordpress has achieved over the years, and what it has helped to create. But the current wordpress code base is a nightmare to work with, and doesn't scale well. Having said that, it is an excellent blogging platform and CMS, but this is something that is usually forgotten, resulting in it finding itself shoehorned into the most inappropriate places.

I've been managing a series of wordpress sites for about 9 years now. Since 1.2 or 1.3, I think.

In terms of keeping the thing running, it has not been a pleasant experience.

Re: Dear WordPress

#42
post #20
post #6

I can appreciate what wordpress has achieved over the years, and what it has helped to create. But the current wordpress code base is a nightmare to work with, and doesn't scale well. Having said that, it is an excellent blogging platform and CMS, but this is something that is usually forgotten, resulting in it finding itself shoehorned into the most inappropriate places.

I get the feeling that those who "like" wordpress are either heavily invested in the platform or can't read code. Simpler, more specialised blogging engines are so beautifully designed, I don't see myself ever wanting to work with Wordpress again.

I'm not fan of the codebase, but until something else comes along that's as easy for my clients to learn/use - I'm going to keep on recommending and installing WordPress for them.

Anybody who's used a word processor can pick up most of what they need to know to work as an author or editor in WordPress in a afternoon. I'm not about to recreate all the widely available documentation and tutorials WordPress has available - or explain to my clients "all you need to do is write all your website content in MarkDown, then run this Ruby script from the command line to publish it to S3/CloudFront!"

Re: Dear WordPress

#43
post #34

Earlier quoted context omitted.

I don't like the Svbtle style but I don't think you should suggest using something that stole the design and is not condoned by the original author. It's so funny how outraged hacker news becomes when a startups design is stolen but when dcurtis made svbtle a private platform they were all to happy to have people steal the design.

I've never followed this brouhaha--was it stolen (i.e., was code lifted from svbtle) or is it a reimplementation? I mean, to me it looks pretentious and lame and I'd never use it, but it seems like it'd be legally actionable if there was actual copyright violations in the offing.

From vague recollection - there was some pretty damning evidence when it launched that entire swathes of css were direct copies - not just functional equivalence, but identical class/id/selector names.

(Note: this vague recollection might not have been about the particular WordPress theme in the parent comment, but I do recall looking at one of the early Svbtle WP clones and seeing this)

Re: Dear WordPress

#45
post #36
post #17

Dear Wordpress- meet MVC, git, postgres, sane security and 100% testing. Please leave your old friend FTP- he was never all that safe or great to begin with.

The thing is, Wordpress is used by people who don't know and do not want to know what those things are. I dare say, even PHP is mostly used by people who don't know what most of what you wrote is. I've seen even Magento forum members (Magento being a complex e-commerce solution written on the Zend framework) saying they do not know how to write more than a couple of lines of PHP.

I'm not sure I agree about the "do not want to know" part. After 5 minutes with Git I don't see how anyone would want to stick with FTP…

But yeah, the fact that WordPress hosting plays so badly with git is a big part of the reason why I probably won't be using it again.

Re: Dear WordPress

#46
post #31

Earlier quoted context omitted.

But Hacker Community is the one that guides others towards new technologies. 10 years from now, Octopress may be prime blogging platform or second best!

> But Hacker Community is the one that guides others towards new technologies. 10 years from now, Octopress may be prime blogging platform or second best! Not really -- they just like to believe it works that way. What the more people chose is based on more pragmatic issues and market factors that "what the geeks use". And no, "we advice the rest of the family / friends what to buy" doesn't cut it either. We may do i…

I'd say it was a mistake to be thinking that people who use Java or .Net aren't hackers. :)

Re: Dear WordPress

#48
post #17

Dear Wordpress- meet MVC, git, postgres, sane security and 100% testing. Please leave your old friend FTP- he was never all that safe or great to begin with.

How is that going to help when over 10 million people are running WordPress on shared hosting accounts where MySQL and FTP are the only database and only file transfer options?

Re: Dear WordPress

#49
post #36

Earlier quoted context omitted.

The thing is, Wordpress is used by people who don't know and do not want to know what those things are. I dare say, even PHP is mostly used by people who don't know what most of what you wrote is. I've seen even Magento forum members (Magento being a complex e-commerce solution written on the Zend framework) saying they do not know how to write more than a couple of lines of PHP.

I'm not sure I agree about the "do not want to know" part. After 5 minutes with Git I don't see how anyone would want to stick with FTP… But yeah, the fact that WordPress hosting plays so badly with git is a big part of the reason why I probably won't be using it again.

> After 5 minutes with Git I don't see how anyone would want to stick with FTP…

You're assuming you're dealing with someone at least a bit technical. To them, FTP is drag and drop, git is either 'hacking' or magic.

Re: Dear WordPress

#50
post #36

Earlier quoted context omitted.

The thing is, Wordpress is used by people who don't know and do not want to know what those things are. I dare say, even PHP is mostly used by people who don't know what most of what you wrote is. I've seen even Magento forum members (Magento being a complex e-commerce solution written on the Zend framework) saying they do not know how to write more than a couple of lines of PHP.

I'm not sure I agree about the "do not want to know" part. After 5 minutes with Git I don't see how anyone would want to stick with FTP… But yeah, the fact that WordPress hosting plays so badly with git is a big part of the reason why I probably won't be using it again.

FTP: lots of graphical clients available for all OSs, your host can probably give you a bookmark to drop into one for a Windows client and a Mac client, and if they don't it's pretty easy to make a new bookmark pointing to your server with your login/password. You're done, start uploading stuff!

Git: Hi! Let me teach you about version control! We'll start with the command line version. Also you may have to ask your host to turn on Git access to your files. And the likelyhood of them making it easy for you to just drop one file into a simple graphical Git client is close to zero.

Who in your life is clueless about computers? Imagine you're them.

Which one looks more appealing? Which one looks scary and intimidating and demands that you learn a thousand new things on top of learning all the stuff you'll have to learn to get a website up?

Post reply on HN