I hope the group does not mind me asking a few business oriented questions about Seattle.
I have had Seattle since its original release, but so far have not used it. I have become quite cynical about Delphi as a result of my XE2 experiences. 1. I’d like to hear from anyone that is using Seattle in full production, general thoughts about its features, and productivity. 2. If there is anyone also using .NET? It would be particularly useful if they could compare from a Business perspective the pro’s and cons. For example. · Which is more effective at producing finished product. (Faster to market) · Which is more effective at meeting customer’s needs. (Faster customisations) · Solution performance. Which is better. (How snappy is the solution to use) · Security. Which is better. (.NET seems inherently flawed in this respect) · Deployment. Which is easier? · Does the Delphi team sit comfortably alongside the .NET team ? · Which product fits better with latest business strategies such as IOT and Cloud ? 3. Does Seattle have any comparative presentation layer to compete with WPF ? Does anyone used it ? Does it support well MVVM ? 4. Market credibility for Delphi is low. Most International Corporate clients have never heard of it, and those that have are very cynical. How to overcome this marketing hurdle? 5. What is the Delphi developers strategy for Cloud deployment ? 6. Which country has the greatest penetration of Delphi Seattle ? Where are the best developers available ? 7. How do you feel about the high cost of Delphi compared to VS ? 8. How is the support for Delphi ? User groups, and Embarcadero maintenance contract ? 9. And finally: How is the market availability of Delphi developers these days ? Thanks very much, Tony
_______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
