VistaDB saga continues with Jason Short deleting blog comments
Jason Short the Ph.D. jackass continues to spew excuses in a weird attempt to justify his failings as a businessman and software vendor. What a joke. Very interesting to watch this story unfold as he made several blog posts explaining why he can't be in business selling VistaDB due to expenses.

The inside word is that the original developer sold him the product and customer base because he was offered a job at Microsoft. It seems that Jason Short will be joining the original owner at Microsoft and has decided to rant and rave about his failings to justify screwing his customers into buying upgrades. My buddy just tried to post a comment to his latest blog posting and it was deleted. Jason claims he never made promises about releasing a VistaDB Server edition when in fact there are numerous mentions of this on his blog and forums.

I hate dishonest bullshitters like this guy and someone needs to call him out since he filters the comments on his blog. For the record, I am a VistaDB customer and am not excited about how this is being handled, but I am more interested in calling a spade, a spade.

Here is the original blog post by Jason Short claiming:
http://infinitecodex.com/post/2010/08/11/Small-Business-Lessons-continued.aspx

""a@b" - no one ever promised a server - EVER. Get that very, very clear."

And here is the comment that Jason deleted. My buddy emailed this to me and I got his permission to repost:

Jason, maybe it's you that should get "very, very clear" on what in fact was communicated:

From the blog post found here:
http://www.vistadb.net/blog/post/2008/01/02/Looking-ahead-to-2008-and-back-at-2007.aspx

"The VistaDB Server will be released this year. I do not expect it to compete with SQL Server. I get asked that question a lot. VistaDB Server will first be designed to get around the file sharing problems of Windows. The initial design is for only having to change your connection string to talk to the server (like VistaDB 2.x did). Throw in some caching, and basic management and that is the product. It is not going to have complex user permissions like SQL Server, or all the OLAP and other enterprise abilities. Our goal is not to match on a 1:1 basis. We are looking at what people actually use, and need for small and medium business uses. Single user is the in process engine, now scale that up to a few hundred users."

In the same post, another mention of plans for server builds:

"I feel we will probably slow down on releases of the core engine now that 3.3 has been released, but we will start having builds for the server, sync, linq, etc."

And here ("next version" of the Server is mentioned):
http://www.vistadb.net/blog/post/2008/04/03/Subscription-renewals-dog-food-and-upcoming-changes.aspx

"Product design (especially the server) is going to be a foremost concern for us in the coming months. We will probably release an initial server that is similar to VistaDB 2.1 Server. It will be basically built to allow you to work around the Windows open file share problem, but it will not be a true server like SQL Server. While at Emerald we built several systems that scale to tens of thousands of concurrent users, and the next version of the Server will have to be able to scale much higher than the current design allows."

And here:
http://www.vistadb.net/blog/post/2007/10/30/VistaDB-business-case-Scalability.aspx

"The VistaDB 3 Server will be released next year for medium sized deployments."

And here, under "We are on target for our goals" no less:
http://www.vistadb.net/blog/post/2007/11/21/New-Feature-Frenzy.aspx

"We mapped out this year back in April as to what we would do and when. We are on target right now with where we wanted to be, feature wise. The server is probably going to be late, but the core engine is now where we want it to be as a feature set for 3.x. The only other major additions are the Sync Services, and LINQ. Neither of which will effect core engine design at all."

And here:
http://www.vistadb.net/blog/post/2009/05/11/VistaDB-3x-Product-Roadmap.aspx#comment

"Until the server edition there is no solution for that except to write a local caching agent for your application."