VOPS
in [Visual Objects]
|
From: Geoff Schaller on 18 Nov 2005 07:27 Johel, I am not denying that affordability can be very different in different parts of the globe but nor do you expect the guy who can't afford a mobile phone to be buying a PC. There are plenty of rich companies in your country quite capable of affording PCs at US rates as much as any other part of the globe. The execs fly around the world and spend money like any other exec. My point is simply that the business capable of operating with a PC and capable of purchasing a PC is not going to be disadvantaged by the price of software any more than anywhere else in the world. Geoff "Johel" <johelsouzafilho(a)uol.com.br> wrote in message news:1132311924.766451.285130(a)g47g2000cwa.googlegroups.com: > Geoff, > > > Not true around the World. > > > > > So no, it wouldn't represent the license fee equivalence you proffer.
From: Ginny Caughey on 18 Nov 2005 07:56 Johel, > make Vulcan a no option. In the long term it would be financialy wise > (less costly) to go from VO to C#, which costs nothing nowadays (MS-VC# > Express and #Develop). Of course. So why aren't you doing that? I'm not doing that because the cost and time of rewriting a large suite of VO apps in C# is many, many times more expensive. By the way you don't need #Develop for your free scenario. Just use C# Express - it includes a limited version of Visual Studio. Ginny
From: Johel on 18 Nov 2005 16:23 Ginny, > > make Vulcan a no option. In the long term it would be financialy wise > > (less costly) to go from VO to C#, which costs nothing nowadays (MS-VC# > > Express and #Develop). > > Of course. So why aren't you doing that? Because I'm evaluating the options available. Your idea (a VOPS only option to buy Vulcan) would move me to C# for sure. You're very good about programming but not about marketing strategy. I hope Brian and Don are wiser. > I'm not doing that because the cost > and time of rewriting a large suite of VO apps in C# is many, many times > more expensive. The problem is that you are a vertical market company that sells for a niche and local market. Vulcan is _not_ a vertical market product, the aim is to sell it globaly and _not_ for a niche market. Your experience has no value for the market Vulcan should be sold at. Or else Vulcan will be a vertical, niche and local (US/Canada) market product. Sorry to be that hard... but you must understand that your vision _may_ be a problem for Vulcan market strategy, that is, your vision could be sending potential Vulcan customers to competing products. Not a good way to grow a company... > By the way you don't need #Develop for your free scenario. > Just use C# Express - it includes a limited version of Visual Studio. If C# Express allow me to reference Mono assemblies (and it looks like it is possible, thanks to Don explanation) then you're right. I must try it. I was sure MS would make that impossible and did not even think about that possibility... Johel
From: Johel on 18 Nov 2005 16:58 Geoff, > My point is simply that the business capable of operating with a PC and > capable of purchasing a PC is not going to be disadvantaged by the price > of software any more than anywhere else in the world. That's not true anymore. Please, understand that PCs are local made here in Brazil using local resources (plants, employees, etc). MS software is US made using US resources (plants, employees, etc) and that's why MS software is so much expensive here in Brazil. Open source software (Linux, Ingres, Apache, PHP, PostGRE, OpenOffice, #D, etc), of course, is free. And now we are getting even some closed source software for free : VC# Express, SQLServer Express, Oracle 10, etc... For example, SQLServer Express + SQL Server Management Studio Express is a good enough solution for small businesses. Why should I buy the full SQL Server if those said businesses will never reach SQLServer Express limitations? It's all about cutting costs. If you're not sure yet, then read this: -------------------------------- Software: No longer business as usual The software industry, already reeling from consolidation, is grappling with a new problem: finding the right sales model. The old, traditional model of selling software, either through up-front fees or long-term licenses, is increasingly under strain as both consumers and big businesses demand change. http://news.zdnet.com/2100-3513_22-5958760.html -------------------------------- Regards, Johel
From: Ginny Caughey on 18 Nov 2005 16:57
Johel, > Because I'm evaluating the options available. Your idea (a VOPS only > option to buy Vulcan) would move me to C# for sure. You're very good > about programming but not about marketing strategy. I hope Brian and > Don are wiser. Actually what I was thinking of was an included one-year support contract with the purchase of a Vulcan.NET license. This would clear up issues concerning frequency of bug fixes, since VOPS provides frequent updates, and it would also fund continued development for Vulcan.NET. But it doesn't matter what I think really, because Grafx has already announced pricing for Vulcan. What they haven't announced yet is what the support and update policies will be. ;-) > The problem is that you are a vertical market company that sells for a > niche and local market. Vulcan is _not_ a vertical market product, the > aim is to sell it globaly and _not_ for a niche market. Your experience > has no value for the market Vulcan should be sold at. Or else Vulcan > will be a vertical, niche and local (US/Canada) market product. Perhaps, but I consider VO a niche product already, and surely Vulcan.NET will be too, at least initially. Although my apps are vertical, there is great similarity between my apps and the Grafx products in that they are both produced by small companies with limited resources. One thing wise purchasers might want to consider is how likely it is that company will still be around in a few years still enhancing the products they've invested in. A business plan that includes a recurring revenue stream from maintenance contracts tends to reassure people who do think about that sort of thing. > If C# Express allow me to reference Mono assemblies (and it looks like > it is possible, thanks to Don explanation) then you're right. I must > try it. Yes I think you should. Then your statements about what would move you to C# would be backed up by some knowledge as to what effort that might entail. That is really the only way to decide if Vulcan (at whatever price) is a good investment for you and your code. Ginny |