Job Track:
Other:
me on twitter:
@metarobert
BeTwittered Home:
32Hours.com
The next BeTwittered:
zoop
It's been several years since we went to the Rose Parade float viewing. To be honest, I was OK with not going since I don't really like thick crowds, and there were a LOT of people there last time. 92.4% of those people either stepped on my right foot, or stepped in front of me to get a better view (a better view than me, that is) This year it was not bad. There seemed to be more open space, so I only ended up pushing a couple of people over and accidentally standing on their backs. Of course, I did apologize and wipe the dirt off of their shirts when I was done looking at the float and stepped down from them.
Getting to see the floats at the viewing is much more impressive than seeing the parade or watching on TV. You may be able to imagine the size of the floats, the amount of flowers and plants, leaves, and seeds being used. But to see the detail up close, like the orange peels that make up an eagles foot, or the pampus grass used as the hair for so many animals or people, or just the shear scale of things like the bugle player who stood 60 feet tall. That is something you have to be up close for.
Here I am posting about Drupal on my Wordpress based site. Probably ironic only if you are a geek and know what they both are. Anyway, I'm seriously considering moving my sites to Drupal, including this one. Among other options such as cackePHP and CodeIgnitor, I checked out Joomla and Drupal.
I'm really disappointed in all of the options I found. None seem to be a really nice way to quickly build a site or app while keeping the server and client sides separated cleanly. I currently write javascript for the client (The view in an MVC) and PHP for the backend and the API's (The controller in an MVC) I'm really wanting a platform to build on top of, so I'll see how this goes. Drupal simply seems the most promising and the most flexible.
I'll be starting out by simply moving my sites over, which will essentially be blog migrations. From there, I'll be working on creating modules or modifications that are AJAX and REST API oriented. I'll probably soon be giving up and learning how to write crap that generates sites from PHP, just like everyone else. Blech. Oh, well. that appears to be the direction of the universe.
Sometimes I feel like I'm in an incredibly small minority that thinks web pages should be written in their native lingo of HTML/CSS/Javascript and that the backend should just be a service. Would that entirely destroy the MVC framework economy? I mean, isn't using the browser as a client view and the server as a REST service an MVC model inherently? Maybe I'm wrong? Then comment and start a fun argument with me here.