Well on the technical side is makes sense and is a VERY attractive concept. BUT in the corporate world the companies easily see the idea of a huge multi-purpose do-it-all compiler/ide suite as an excuse to overprice it. Seperate them and that excuse is gone. In fact to get someone to purchase them together they're more likely to offer a bundle deal.Originally Posted by noeska
The other reason is that the Delphi development team of the recent past, has shown it's inability to take on too many new technologies and innovations. (Bull-headedness on the part of the project planners/bosses if you ask me...)
It's the corporate theme to make everything marketable and only hand out little pieces at a time so that they don't exhaust their fat juicy cash cow. (To be honest this is the 'evil' approach that Google employees talk about in their mission statement.)
This is the problem that has become Borland. Having 2 projects running side-by side, it's possible that neither team would have the excuse that they are adding enough to justify a new version and a new product to sell, when we developers know that thats complete bull.
Pascal programmers want to develop in Linux, Mac and Win32/64. But we don't get that. We want to do mobile devices too. But we don't get that either. We did get code refactoring and other similar enhancements, yes. We did get .NET ok fine. But we also got husstled into a higher priced do-it-all suite that ran like crap and half of it we didn't need nor want.
Breaking things down and simplifying it is a good thing in a way. The DevCo is not Borland, thats clear, but I think that from a corporate vs the consumer side of things, it's a better bet than these mega-super suites that Borland has been pumping out for an underfunded department is crap.
It is nice in fact to see(well hear) the opposite of that for a change.
Reply With Quote
Bookmarks