I don't think the question is actually correct. Visual Studio is an IDE - it has no "language", so if you don't switch to VS you would switch to something like C#, asp.net, or something supported within VS.
We use PB, .Net (C#/asp.net), and Java but have been moving away from PB. The move is a lot easier from PB to Microsoft then from PB to Java for PB developers. Five years ago I would say PB had the edge over .Net but that lead is far gone in my opinion. VS2012 just rocks with features and .Net is a tier 1 platform.
My biggest concern is the same as some other's which is the lack of direction or seeming commitment to the Sybase products. I use PowerDesigner extensively and it has become almost useless in many areas. e.g., .Net is at version 4.5 and PD only supports up to 2.0.
When it comes down to it though in my experience the cost of change should be the greatest concern. I just can't imagine switching to PB at this point with so many concerns around support, resources, and a product roadmap. If you had a large product portfolio in PB I might say stick with it for a while and see what happens, but I think it would be pretty hard to argue for a change.
Be careful you don't get slaughtered by the VS/.Net advocates if you don't have all of the details nailed.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.