iWeb generated code is crap
Well as I expected the code generated from iWeb is really crap, I searched a lot for any examples of iWeb generated pages but I failed, but now the first pages are showing up, and I'm sorry to say that they're crap, check the source code of those examples or disable there CSS and see how they look, Todd Dominey has describe it as not that good & BusinessLogs describe it as awful.
I'm sorry Apple I always trust you and adore your products but this app was a disappointment to me. I can't imagine how a company like Apple in 2006 still use those old school ways, I hope they fix this mistake in new releases but for now I don't advice any one to start a blog with iWeb, just go with Blogger it's way better and it's easy too.
January 13, 2006, 07:03 AM | Apple , Web standards , XHTML , blogging
TrackBack
TrackBack URL for this entry:http://www.point-studios.com/cgi-sys/cgiwrap/boudym/managed-mt/mt-tb.cgi/30
Comments
1 | February 4, 2006 11:14 PM, Justin said:
I just bought iLife today. I bought it mostly for an update in Garageband that wasn't there (crap!), but I looked at the code for the iWeb page you posted.
It isn't so bad really. It's awful to look at but the code is generally compliant.
The problem is that it's only useful for .Mac accounts, which would be fine if they were free. Also, reading that first iWeb page offers up quite more advice about using iWeb.
I personally like "O" or "none" code because it gives you quick edit options without having to look up CSS properties. Now Microsoft...Microsoft generates some crap code. You try saving a .doc as .html and you barely be able to read the source at all. The code in iLife is just fine.
Still an overall disappointment though in terms of portability and openness.