On 5/23/02, Brian Carnell said:

>"We wonder, how long before Dave "upgrades" Radio to limit it's TCP
>connections, like the old Radio7 product? This would cut off
>Conversant's air supply quite quickly. Sounds like Dave's got a trunk
>of his own he's gonna stuff..."
>
>The problem is not so much that I think this would actually happen as
>that Winer's so erratic, who knows for sure what he's going to do?

In fact, until they hire somebody to work on the kernel, that's not
going to be an issue.

Also, they'd be shooting down one of their own products. The Radio
Community Server, which was designed to run on Radio, *REQUIRES* the
ability to have lots of TCP connections at once. RCS isn't doing well
right now, but it's an important part of their plans for pushing a lot
more copies of Radio.

>It's not just this issue over whether he does or does not point to the
>software, but rather that is just one in a long series of events that
>add up to one big question mark about Userland and, unfortunately,
>Macrobyte. Do you really want to be dependent on software from a
>company that is constantly bickering with its third party developers
>and customers?

Once you've installed it, you're not dependent on them. We plan to
handle ALL tech support once 1.0 is released and the support agreements
have been decided on. One thing we'll do is make very clear
recommendations about upgrading the underlying products, etc.

Existing software doesn't always run the same on newer operating
systems, and it's your own fault if you upgrade the operating system
without checking first. We have a very similar situation here.

>(All of which, btw, is why I appreciate Seth's decision not to use his
>weblog to discussion Macrobyte related issues -- Scripting.Com sends
>contradictory and confusing messages to potential Userland customers).

It's nice to be able to return to that position, too, after a couple of
departures from it. Now I have official sites for macrobyte stuff.

Of course, I no longer have the time, since I have to spend half of it
talking to clients, the press, and other people, and the other half
writing documentation. Oh, and the third half riding my bike. ;-)

This is probably a lot more than I should have said in this space. Oh well.

Seth