[DUG] Seattle questions

[Tony Blomfield]

Thanks very much John.

Why and how do you use both ?

From: delphi-bounces at listserver.123.net.nz [mailto:delphi-bounces at listserver.123.net.nz] On Behalf Of John Bird
Sent: Monday, 11 April 2016 4:33 p.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] Seattle questions

My perspective, and its a partial one.  But I work in a house using both XE8/Seattle and C#

Q1 – XE8 is fine (our current production version) and all the comments about Seattle I have heard are good – large projects more stable in particular.

Q2

·         Which is more effective at producing finished product. (Faster to market)

·         Both are fast – Delphi compiler and single file deploy is still very hard to beat.

·         Which is more effective at meeting customer’s needs. (Faster customisations)

·         Everyones opinion will differ on this

·         Solution performance. Which is better. (How snappy is the solution to use)

·         Delphi performance is hard to beat.   A lot of .NET is also very good these days.   But not all.

·         Security. Which is better. (.NET seems inherently flawed in this respect)

·         Delphi does not have zero terminated strings – this has to be a huge advantage as buffer overflows in strings are likely the main security weakness in C family of products.  Runtime languages such as .NET and Java have a spotty reputation too.   Security is ultimately much more than the language, but to my eyes Delphi starts with less weakness.

·         Deployment. Which is easier?

·         Single file vs a folder structure of hundreds of files – and the issue of figuring which files of those files to deploy for a new version.

·         Does the Delphi team sit comfortably alongside the .NET team ?

·         Yup, 3 teams using both.   Each team prefers one or other, but uses both.   Remember Anders Hejlsberg designed both

·         Which product fits better with latest business strategies such as IOT and Cloud ?

·         Everyone’s opinion varies according to what they know and like.

·

·         Q3 – WPF - Yes with differences – merits in both

·

·         Q4 – Credibility - refer surveys – latest TIOBE index has Delphi at Number 11, at half to two thirds popularity of C#.   Higher than Objective C and Swift still.  Java, C and C++ are still the biggest

·
http://www.tiobe.com/tiobe_index

Q5 – IOT/Cloud - Delphi does Web Services, IIS and DBs, and cross compiles to Win32, Win64, OSX, iOS, Android and linux server soon.  Others can add more specific cloud points.

Q6 -  Where - Europe seems strongest bastion of Delphi, but everywhere.   Maybe not India – they all want to seem to do SQL Server, C# and Oracle there so they can get jobs in California.

Q7 – Cost - Cost is reasonable to me.   If it has to be free looks like Free Pascal is a decent alternative too - never had to look at it myself.

Q8 – Support - Mainly good.   Generally resolve any issues within days or hours – and its usually the way I’m doing it that is at fault

Q9 – Developers - Mainly older developers tis true.  But only mainly.   Some of them think that Delphi may still be going strong when C# fades from popularity – mainly for the reasons of:

a – its a good language (Thanks Nicholas Wirth – designed as a good formal teaching language)

b – its already cross platform, so competes with the biggies of C and Java with advantages over each.

From: Tony Blomfield<mailto:tonyb at precepthealth.com>
Sent: Monday, April 11, 2016 1:21 PM
To: NZ Borland Developers Group - Delphi List<mailto:delphi at listserver.123.net.nz>
Subject: [DUG] Seattle questions

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: delphi at listserver.123.net.nz<mailto:delphi at listserver.123.net.nz>
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-request at listserver.123.net.nz<mailto:delphi-request at listserver.123.net.nz> with Subject: unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20160411/9d04118f/attachment-0001.html