6 ms·
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 w
by ck2 14y ago
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&prmdo=1 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 and it's now a godzilla of a program so it's becoming a huge nightmare. A cache miss in WordPress on a busy server is a horrible, horrible thing.
You cannot escape that problem by a fork.
- calinet6 14y agoThis 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 from—a misunderstanding of exactly what that would entail. Modern rewrite is what's needed, definitely. But don't call it anything related to Wordpress. Don't need to.
- johnonolan 14y agoI'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, businesses and users, as well as cutting down time to ship first working concept, are (in my mind) some important arguments in favour of a fork.
- tsewlliw 14y agoI'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.
- calinet6 14y agoI 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)
- ringmaster 14y agoFirst, let me say this: I love what you've done with the Ghost design. I think it's clean and useful. More on this below... I am one of the early contributors to WordPress (you'll see my name on wp.org's About page near the bottom), and one of the founders of the Habari Project. We started the Habari Project for many explicit reasons, but in part because the curators of the project (Automattic) were not behaving in a way that we felt was beneficial to the community they had begat. So let me tell you a little about our project: Not only is the Habari Project an entirely Open Source platform, but it recognizes participants in the project appropriately based on their contributions, something that I did not observe during my tenure working on WordPress. Habari employs the Apache Software License, which is more permissive than WordPress' GPL. Want to develop a plugin or theme? Is the code tainted by the GPL? In WordPress, I don't really know for sure what parts can be redistributed, if any. In Habari, you can sell your themes and plugins for profit if you want to, or contribute them back to the community -- most themes and plugins so far have been. The passion of the Habari community for producing good, documented code has (in my mind) been one of the driving forces behind WordPress' "recent" adoption of similar policies. The quality and friendly tone of assistance I get from people who know about Habari has been consistently orders of magnitude better than anything I've seen come out of WordPress, which is a characteristic that everyone working on Habari strives to maintain in the project. One of our guiding principles has been to be a project that is useful for web development education; We've seen a lot of people join our project and learn how to code well, both in the method they use and in the collaborative environment our development often lives in. We've accepted a policy of keeping up with as current a deployment of technology and standards as our core users can stand. We recently adopted a PHP 5.3 minimum version, and I'm pushing hard to take that to 5.4. Habari simply does not run on PHP 4, and never will because it's no longer secure. We code for HTML(5). We're using CSS3. Our roadmap (admittedly difficult to find online) includes PSR-0 and namespace adoption to more easily integrate with vendor libraries. The use of current technology and techniques is really good for developers, and a refreshing change from projects that insist on supporting every old (insecure) server architecture out there. And I'm currently making a living (yes, paying the mortgage) deploying Habari as a CMS for clients. It is viable. It is open source. I know first hand how long it takes to build a working product with a small community. We are admittedly behind in our implementations of some features that WordPress was able to steam ahead with due to their larger community. There are also non-dev areas like marketing where we could use some work. We've been trying (albeit weakly) to lure those kind of contributors to the project. We had a talented designer help us with our current admin design, and one of the things people comment on most about it is how it's not as cluttered with st as WP's. I like the design you've used in Ghost because it's similar to ours, yet modernizes, and I think our community would like it, too. We've been talking heatedly about a new admin design for our next release... Habari may not be the thing for you, but I do encourage you to take a look, visit our IRC channel on freenode, and take from it what you can. If you still want to try to bend a WordPress fork, I'm at least interested in the story of your effort and struggle. And if you want to chat about why we started over (though I think it's obvious, maybe it's not to everyone else) instead of forking, or why a new project with a handful of addons (compared to a competitor) can still be a contender, I'm happy to chat. Here we are: http://habariproject.org/ http://habariproject.org/
- voidfiles 14y agohttp://octopress.org/ 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.
- calinet6 14y agoI love it, been looking for something like this for a while. Thanks for the link.
- mortenjorck 14y agoNo need to either fork Wordpress or write anything from the ground up – build it on top of ProcessWire (http://processwire.com http://processwire.com). A small distributed team could probably build basic Ghost functionality in a couple of weeks based on PW.
- STRML 14y agoSlow loads are an individual implementation problem as much as it is a Wordpress problem. Wordpress will happily give you more than enough rope to hang yourself with (e.g. Recent Comments), but even slightly savvy engineers should be able to avoid the pitfalls and AJAX expensive queries when needed. I agree that Wordpress should have saner defaults but it is not impossible to build a fast site with it.
- ck2 14y agoI'm not talking about front-end, I mean back-end. WordPress is over 100 files of code 3mb size, loading on every page, BEFORE plugins. It's impossible to build an active, non-cached site with it. I have 100% dynamic php forums running side-by-side with wordpress and they are completely uncached - for WordPress that's impossible at the same load.
- agumonkey 14y agoI used the sociable plugin (like/tweet/+1 buttons). Out of extremism I tested under elinks, saw some weird empty ul/li hanging around, inspected the plugin config and then went into the code. The latest release at the time was barely beta code, large spans of deadcode, copy/pasted pages-long loops that were 90% similar. Wordpress plugin pages quote millions of download for this plugin. Who needs quality ?
- tsewlliw 14y ago(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 work valuable.
- agumonkey 14y agoAgreed, and my question was half sarcastic / half pragmatic. But I don't know where I stand on this issue. Answers lie somewhere in the middle, and to me, this case was quite out of balance.
- pi18n 14y agoYes, this is could be a much better project if it was written fresh, and preferably in a different language altogether.
- bergie 14y agoPHP has the big benefit of being deployable anywhere. Without that fact it is unlikely that projects like Drupal or WordPress would've taken off as they have.
- Karunamon 14y agoNewer languages aren't? Every linux distro that matters (including BSD, Gentoo, and others with a ports system), heck even Windows, has a full Rails stack that's about two commands away from being fully set up. Unless I misunderstood what you mean, here :)
- huskyr 14y agoSure, you're right. But i suspect that 95% of all WP installs are by non-techies on shared hosting, that very rarely have Rails or Python support.
- mosselman 14y agoYes thats the way to create great new products. Make it easy for non-techies to get them up and running and make sure they run on shared hosting and are created in a language that beginners use to learn about programming.
- drivingmenuts 14y agoI can't tell if you're being sarcastic or not, so I'll just assume the worst. Yes, it is - there's a lot more non-techies than there are of the other kind, so it makes sense that you focus your efforts on the larger market. As for the whole "language that beginners use to learn about programming", do you mean Python or Java? PHP is everywhere but the last I checked, Python and Java are the teaching and taught languages. PHP itself is designed to get things done, not necessarily elegantly. For all it's problems, it is a workhorse and blaming the language for what the users have done is just wrong. Programming languages are like hammers and should not prevent one from doing something stupid or irresponsible. Doing the smart or right thing is the responsibility of the user.
- scott_s 14y agoI see no reason why it can't be a fork. You may not want it to be a fork, but that's different from it needing to be a new project. There is a very popular piece of software that millions of people use today that was a fork of a large, sprawling suite of a mess of several programs that used an actual Godzilla as its mascot: Firefox.
- _pferreir_ 14y agoAnd, if I recall correctly, Mozilla had a hard time keeping it at the same level of WebKit/Chrome, partly because the code was too old and needed a lot of changes.
- Maro 14y agoOne should be careful not to frame a new product as an engineering problem. Users don't care if it's a Wordpress fork or a rewrite. Users care about the product experience, what it delivers, benefits, etc. Having said that, you may be right.
- aj 14y agoThe images and the proposal part was what I noted first as well. I left the site as soon as I noticed that all content was in images. I wonder what the reasoning behind such a poor choice of displaying content was? Prevent Search Engine crawling? Prevent easy copying of the text?