Apple
A Review of Apple iWeb
03/06/06 09:04 PM | Permalink
So surely you've noticed the new digs. Why the
change? And why start another blog so soon
after 2.0 launched? And lastly, why start the new
blog with a review? Well the answers dear reader are
all the same. Do read on.
iWeb is a new application from Apple and as such it's version number is 1.0.1. Let me tell you, all that glitters is not gold. Sure, iWeb allows you to churn out professional looking websites without breaking a sweat. And with a little skill you can even do some cool stuff to differentiate your site from the norm. But that's where things start getting ugly. Even the simple things I did in my iWeb site (Jonathan's Sexy Blog 2.0) involved all sort of trickery to get around iWeb's inherent deficiencies.
An example: iWeb does not support ANY custom html. Thus when the built in web stats weren't enough for me, I had to take drastic measures. I wrote a program (using Automator) to manually pull the html pages from the server after publishing, then manually inject stat counter code and re-upload the modified pages. All this to do what almost any other web site builder would allow automatically prior to uploading. At this point, I should have known to stop using it. But I was so blinded by the glitz that Apple's "we know what you want better than you do" philosophy didn't even phase me.
It was only later when bugs started to appear that really hampered my productivity that I realized I should dump this 1.0 app. I became plagued by publishing bugs that essentially prevented successful uploads due to a variety of issues. iWeb is SLOW. Period. Add onto this the fact that my new iWeb site didn't do things even Xanga could do and well.... that's just plain embarrassing!!
So remember friends, you can do better.
iWeb is a new application from Apple and as such it's version number is 1.0.1. Let me tell you, all that glitters is not gold. Sure, iWeb allows you to churn out professional looking websites without breaking a sweat. And with a little skill you can even do some cool stuff to differentiate your site from the norm. But that's where things start getting ugly. Even the simple things I did in my iWeb site (Jonathan's Sexy Blog 2.0) involved all sort of trickery to get around iWeb's inherent deficiencies.
An example: iWeb does not support ANY custom html. Thus when the built in web stats weren't enough for me, I had to take drastic measures. I wrote a program (using Automator) to manually pull the html pages from the server after publishing, then manually inject stat counter code and re-upload the modified pages. All this to do what almost any other web site builder would allow automatically prior to uploading. At this point, I should have known to stop using it. But I was so blinded by the glitz that Apple's "we know what you want better than you do" philosophy didn't even phase me.
It was only later when bugs started to appear that really hampered my productivity that I realized I should dump this 1.0 app. I became plagued by publishing bugs that essentially prevented successful uploads due to a variety of issues. iWeb is SLOW. Period. Add onto this the fact that my new iWeb site didn't do things even Xanga could do and well.... that's just plain embarrassing!!
So remember friends, you can do better.
|