So, one of my functions in life is to explain and encourage flexible uses of weblog software for a variety of purposes, and as part of that endeavor I would like to demo and describe BloggerPro and TypePad (link corrected —thanks, Liz, for catching m,y copy-and-paste glitch), with some sense of what the services will cost. Unfortunately both services are not accepting new accounts just now, and it’s not clear to an outsider how either one will ultimately turn out for users (especially naive users). I’m not asking that TypePad beta-testers write in to assure me how cool it is, or BloggerPro users to express themselves about the past and present of that service (since it8’s evidently going through an overhaul). It’s just inconvenient timing, and it’s particularly awkward to present this stuff to potential users while saying, “Well, I don’t know how much it’ll cost you or exactly what you’ll be able to do — but someday it probably won’t be too expensive and I think it will be a great service for you to adopt.”
Posted by AKMA at July 17, 2003 11:34 AM | TrackBackI am a TypePad beta tester, former BloggerPro user: 6 Apart hasn't announced prices for their three levels of service, but the economics of competition should give ball park numbers. They can't charge much more than comparable web hosting services. I don't think the beta phase will last too long.
The TypePad interface is very simple; the user can't be a complete naif to use it, but doesn't need to be a XML geek either. There are some display problems on my site.
I'll be happy to answer any questions you have, if I can. I'm not supposed to give too much away.
Probably won't endear you to 6 Apart to have the typepad name link to blogger pro. :)
Posted by: Liz at July 17, 2003 07:06 PMWhen the machine compiles your code, however, it does a little bit of translation. At run time, the computer sees nothing but 1s and 0s, which is all the computer ever sees: a continuous string of binary numbers that it can interpret in various ways.
Posted by: Lawrence at January 13, 2004 07:10 AMLet's see an example by converting our favoriteNumber variable from a stack variable to a heap variable. The first thing we'll do is find the project we've been working on and open it up in Project Builder. In the file, we'll start right at the top and work our way down. Under the line:
Posted by: Gilbert at January 13, 2004 07:10 AMWhen the machine compiles your code, however, it does a little bit of translation. At run time, the computer sees nothing but 1s and 0s, which is all the computer ever sees: a continuous string of binary numbers that it can interpret in various ways.
Posted by: Gabriel at January 13, 2004 07:10 AMThese secret identities serve a variety of purposes, and they help us to understand how variables work. In this lesson, we'll be writing a little less code than we've done in previous articles, but we'll be taking a detailed look at how variables live and work.
Posted by: Charles at January 13, 2004 12:21 PMThe rest of our conversion follows a similar vein. Instead of going through line by line, let's just compare end results: when the transition is complete, the code that used to read:
Posted by: Lettice at January 13, 2004 12:21 PMFor this program, it was a bit of overkill. It's a lot of overkill, actually. There's usually no need to store integers in the Heap, unless you're making a whole lot of them. But even in this simpler form, it gives us a little bit more flexibility than we had before, in that we can create and destroy variables as we need, without having to worry about the Stack. It also demonstrates a new variable type, the pointer, which you will use extensively throughout your programming. And it is a pattern that is ubiquitous in Cocoa, so it is a pattern you will need to understand, even though Cocoa makes it much more transparent than it is here.
Posted by: Randall at January 13, 2004 12:21 PM