A question for the blogigentsia:
"Should I make the switch to the new Blogger version, or should I stay put?"
I've heard a lot of complaints about the new version when it was in Beta, but working out all the bugs is the whole point of Beta (either that, or it's one of those fish that you have to keep in a little cup lest it become a fighting monster). And it seems that once you upgrade, you can't go back. Is the new version stable enough to jump?
Anyway, help me out here, folks? What IS the answer to the immortal Clash question?
I switched to beta and I haven't had many problems. It's much faster, and the new layout tool is easier to use. There are more options for customizing now that don't involve hacking the CSS code. It has been quite stable for me.
ReplyDeleteI stayed until the final edition came out. I've gone beta on other products, but a) didn't care if it messed up, b) had a good backup, or c) trusted that the beta was already reasonably stable. Judging by the mixed responses, I'm glad I didn't go early. However, now that the new Blogger is up and running, I'm glad to have switched. Just avoiding waiting 4 or 5 minutes for my blog to publish is a real plus. Maybe I'll back up my template and try some of the new bells and whistles one of these days.
ReplyDeleteWe switched our blog over a couple weeks ago and haven't had any problems. I love how much quicker it is to publish a post!
ReplyDeleteDear Bettler, Ory, and Kira:
ReplyDeleteThanks very much for your input! It sounds like the upgrade is worth doing.
Overall the new Blogger is worth the switch.
ReplyDeleteDear Steven:
ReplyDeleteThanks for your input as well. I've decided to go ahead and upgrade, but now I'm no longer getting the "switch now" icon to do so. It seems that they're going to try to make the upgrades orderly, so I suppose I'll have to wait until they offer it to me again.
But thanks again, everyone, for your helpful advice!
Even though I'm not a big Blogger user, I recommend it because new Blogger's comment feeds keep one updated on comments.
ReplyDeleteGo.
ReplyDeleteUpdate:
ReplyDeleteI have made the switch. Once again, thanks for all of your kind and helpful advice!