61–70 of 87 posts
Earlier quoted context omitted.
Wordpress is the worst blogging system out there, except for all of the others.
The comment you're replying to isn't making fun of WordPress. The WordPress community has this bizarre obsession with getting people to capitalize it the way they want them to. http://www.wptavern.com/automatically-correcting-the-wordpre...
This seems like an awful lot of extra layering on top of WP's horribly ugly theming system... And adding Ruby as a requirement? What about building on PHP-based tools like Assetic, or a cleaner template format? https://github.com/kriswallsmith/assetic I've never understood why people were willing to jump through so many hoops building themes in WP's messy way. As a comparison, here's a complete theme (based on the Tw…
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
>>Ability to write PHP code using the beautiful Haml templating system; >>Ability to write CSS stylesheets using the awesome Sass syntax [...]; >>Ability to write Javascript logic in Coffeescript; Some may like that, but I want to write my PHP in PHP, and write my CSS in CSS, and write my JS in JS. I really never got why I would write one language in another language just to then use some tool to translate it (and if…
Coffeescript, haml, and sass are useful because they reduce the complexity of coding html, css, and js. They allow you to get much more bang for your developer-hour buck. Why use jQuery when you can just talk to the DOM directly?
>>Ability to write PHP code using the beautiful Haml templating system; >>Ability to write CSS stylesheets using the awesome Sass syntax [...]; >>Ability to write Javascript logic in Coffeescript; Some may like that, but I want to write my PHP in PHP, and write my CSS in CSS, and write my JS in JS. I really never got why I would write one language in another language just to then use some tool to translate it (and if…
The terser the syntax, the less room for error in comparison to its more verbose counterpart.
"just to then use some tool to translate it (and if it gets a little complicated have to manually fix translation problems afterwards)"
If you're manually fixing compiled code, you are doing it wrong.
"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.
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 minutes to setup a ruby environment with RVM ( https://rvm.beginrescueend.com/ ).
Now my PHP project are cleaner, easier to mantain, only with a little "trick": some really good Ruby tools... At the end, I think that the advantages are worth the costs...
This is a "templated" way to do so in wordpress projects... Why not? ^^
For those of you who want to use modern PHP with WordPress, there's Wordpress MTV: https://github.com/newsapps/wordpress-mtv
I thought I'd mention, for those who prefer a modern Ruby stack, it is possible to install a JSON REST plugin for Wordpress (like http://wordpress.org/extend/plugins/json-api/) on the back-end, and write your front-end display layer in Ruby.
This is awesome! I've often lamented how messy Wordpress is compared to Rails. Yet, there's nothing as mature and easy for anyone to use as Wordpress in Rails.
After working with Active Record, it's really hard to switch back to Wordpress and write:
$today = getDate();
$my_posts->query('year=' .$today["year"]. '&monthnum=' .$today["mon"]. '&day=' .$today["mday"]);I feel this is solving a problem that doesn't exist. The problem with creating a WordPress theme isn't that it's missing buzzwordy tech like HAML, SASS and CoffeeScript. The problem is that the PHP behind WordPress is hideous. Even in version 3.x If someone were to fork WordPress and fix all the spaghetti code, then I could stop writing themes like it was 1998...
Exactly. I don't think that a re-write for WordPress will be the best solution for the moment as it'll wreak havoc on the thousands of themes and plug-ins that exists in the market. I'm thinking of a theme framework that ease the theme creation process. It keeps you focused on doing what matters: putting the theme, CSS, HTML and JavaScript. Mainly there are three things to care about - A routing engine. Similar to th…