Live data from Hacker News

Ghost — rethinking WordPress

john.onolan.org

121–130 of 236 posts

Re: Ghost — rethinking WordPress

#121

Question for photomatt if you're still reading this comment thread, and since it might be my only chance to get dialog with you. Are you considering any changes regards the stack, since many installations can have a issues with speed now (not intended as a criticism). So eg something like Postgres, or MongoDB even for the DB Backend?

I forgot to mention our biggest architectural change, which is already ongoing: an ever-increasing percentage of our codebase is shifting to Javascript instead of PHP. At some point I expect it to be the vast majority.

Re: Ghost — rethinking WordPress

#122

Earlier quoted context omitted.

I've been committing code to the core WordPress codebase for 3 years, so while I'm not a PHP developer - I have some idea. Perhaps one thing overlooked in the argument for fork vs new build is that there aren't a huge number of developers with the skills to make this happen who would do it entirely on an Open Source contribution basis as opposed to, say, a startup basis. Appealing to existing WordPress developers, bu…

I'm relatively new to the WP scene, and already its totally clear that WordPress is tolerated because it has a vibrant ecosystem. Getting to keep that is way bigger factor in uptake over the next five years than anything a rewrite could deliver.

I think you could gain momentum surprisingly fast with a new project if it offered a quality alternative. (I say this as the author of a CMS in another content-type space which has done that fairly well)

Re: Ghost — rethinking WordPress

#123
post #66

Earlier quoted context omitted.

Just because it's a rough concept, and I wanted to put it out as quickly as possible rather than delaying by procrastinating about coding a layout. I actually stole got the idea for making it a big page of images from the original .Mail concept page. If there's interest - of course we could put something more professional (and machine readable) together!

It really put me off. It's not about making it machine-readable, it's about making it human readable for the sizeable number of people who are visually impaired, prefer or need to read in large print, are on high DPI devices, or even copy/paste. It's a massive, huge step backwards. I can't even search the page. I wanted to try and read all of it, but I gave up. I understand that it's quick and dirty, but I don't real…

Just came to comment on the lack of accessibility for this page - thank you for pointing it out to the author.

If you insist on using images instead of actual text, at LEAST add alt-text of the content to the images! Then the page would be screen-reader accessible.

Re: Ghost — rethinking WordPress

#125
post #7

The whole page is images, and it's a non-existent product, it's just a theory/proposal. Buried in the text is it would be a fork of wordpress . Net is filled with that sentiment, but it never takes off: http://www.google.com/search?q=fork+wordpress&tbo=1&... If you want to replace wordpress you need a modern rewrite, not a fork. The #1 problem of wordpress (among many) is it loads every darn thing on every darn page…

This would absolutely be better solved by an entirely new application, written from the ground up. And the whole-page-is-images thing really bothered me too. Some nice designs and interesting ideas for sure, and knowing CSS isn't a prerequisite for being a designer, but damn, I have some doubts about the understanding of the technologies here. Which is probably exactly where the concept of "forking Wordpress" came fr…

http://octopress.org/ is essentially something written from the ground up that addresses many of the concerns in ghost, but that doesn't mean its the solution.

Because WordPress is built on PHP it has a wider array of deployment options, including many low-cost options, while maintaing a relatively easy to use sheen.

I think it makes sense to evolve WordPress to merge the benefits of something like octopress with WP.

Re: Ghost — rethinking WordPress

#127

Earlier quoted context omitted.

(100% totally non sarcastic here) This is what I love about PHP devs. Imagine how much effort it was to write that. The author may not have have the chops to refactor that into something elegant, but he wanted it done and was perfectly willing to just do it the hard way and FUCKING SHIP IT, warts and all. Its easy to laugh at code after the fact, but you can't argue that a ton of people aren't finding the author's wo…

I think there's a false logic present in arguing that "lots of people use it, so it's ok even if it's shit." Apply this same argument to one of several poorly coded plugins that have introduced basic security vulnerabilities and had widespread adoption. I think this is even worse when there's no commitment to improving it. I find it curious we don't necessarily aspire to quality; and I think we should. I'm not happy…

Sure, but "working" is a perfectly reasonable lower standard.

Re: Ghost — rethinking WordPress

#128

Why is all the text a giant image? (That aside, the system looks great)

Just because it's a rough concept, and I wanted to put it out as quickly as possible rather than delaying by procrastinating about coding a layout. I actually stole got the idea for making it a big page of images from the original .Mail concept page. If there's interest - of course we could put something more professional (and machine readable) together!

I kept trying to select the text (when I scroll that's how I keep my place on the page). You probably don't need to re-do this page, but consider a text option in the future.

Re: Ghost — rethinking WordPress

#129

Earlier quoted context omitted.

This would absolutely be better solved by an entirely new application, written from the ground up. And the whole-page-is-images thing really bothered me too. Some nice designs and interesting ideas for sure, and knowing CSS isn't a prerequisite for being a designer, but damn, I have some doubts about the understanding of the technologies here. Which is probably exactly where the concept of "forking Wordpress" came fr…

http://octopress.org/ is essentially something written from the ground up that addresses many of the concerns in ghost, but that doesn't mean its the solution. Because WordPress is built on PHP it has a wider array of deployment options, including many low-cost options, while maintaing a relatively easy to use sheen. I think it makes sense to evolve WordPress to merge the benefits of something like octopress with WP.

I love it, been looking for something like this for a while. Thanks for the link.

Re: Ghost — rethinking WordPress

#130

As someone who makes WordPress sites almost 8 hours a day, what would be the best start is a rewrite of the WordPress core on a popular, modern framework (my vote would be Symfony2). This would bring a breath of fresh air to coding for WordPress. Ideally much of the API would be similar too.

However, OP says WP is over 3mb. Including any popular PHP framework means adding a lot of weight in the start (take CakePHP for example).
Post reply on HN