Live data from Hacker News

Why C# coders should shut up about Delphi (2016)

jonlennartaasenden.wordpress.com

51–60 of 162 posts

Re: Why C# coders should shut up about Delphi (2016)

#51
post #15
post #4

This was published in 2016. And the title included "C# coders". I am not a C# coder, but all C# GUI coders I know had praised Delphi for its design and convenience for GUI... edit:grammar

The one thing that bugged me about Delphi apps on Windows, was that they used their own custom buttons on the forms (with little graphics of crosses and ticks etc.). I am not a Delphi programmer, but I always wondered why this was.

I always assumed it was a licensing thing where they couldn't use the MFC DLL to have the same buttons.

Made it easy to spot a Delphi app.

Re: Why C# coders should shut up about Delphi (2016)

#52
> Some people seem to think that Delphi ended with version 7 back in the 90s

For me it is the case. Before Delphi was a really the greatest, smartest and easiest RAD IDE. I even think that today dev tools are in a bad state and nothing match what we once had back then! Especialy for creating 'responsive' Gui apps easily.

Then, as shitty companies always do, they changed completely the tool and the language with the new bad .net like one. Despite it to be wrong, they claimed that this was better than what we had before and forced it on users. But it was not anymore the Pascal Object that we liked!

Re: Why C# coders should shut up about Delphi (2016)

#53

It’s a really good crash course on the shared origins of Delphi and C# plus a brief reminder of all the modern features offered by Delphi that have flown under the radar, but the anger and emotion is rather immature and really detracts from the argument. Those words could have been better spent selling its strengths further. That aside, things have changed rapidly in the last five years in the C#/.NET world first wit…

sometimes channeling a bit of anger as an engineer can be a pretty good motivator to do things The Right Way(TM). that is to say, I have some sympathy with engineers being angry at technology - obviously it's not ideal as a communication tool like here...

Re: Why C# coders should shut up about Delphi (2016)

#54
post #9

It's hard being an old programmer as some technologies that you used in the past, that were more productive than certain technologies today, are no longer popular. Creating client side apps in the 90s was arguably easier than creating web apps today with the soup of html/css/js frameworks that are changing every month. edit/mass reply: I've been coding web apps with the rest of you guys for 20 years. The web isn't th…

Back in those days, one could take a full two-week summer vacation, and come back to the company still using the exact same stack!

Re: Why C# coders should shut up about Delphi (2016)

#55
post #9

It's hard being an old programmer as some technologies that you used in the past, that were more productive than certain technologies today, are no longer popular. Creating client side apps in the 90s was arguably easier than creating web apps today with the soup of html/css/js frameworks that are changing every month. edit/mass reply: I've been coding web apps with the rest of you guys for 20 years. The web isn't th…

but you can still use those tools on your own projects right? I've been learning and using XQuery and XSLT 3.1 and I really enjoy them! Also, common lisp :-) But yeah, it will be harder to use tech like that on my day job, wish I could.

Re: Why C# coders should shut up about Delphi (2016)

#56
post #14
post #9

It's hard being an old programmer as some technologies that you used in the past, that were more productive than certain technologies today, are no longer popular. Creating client side apps in the 90s was arguably easier than creating web apps today with the soup of html/css/js frameworks that are changing every month. edit/mass reply: I've been coding web apps with the rest of you guys for 20 years. The web isn't th…

You've even drank some of the koolaid by calling them "client side apps". They're simply applications, or if you must, native applications! ;) I'm heavily reticent towards using web-based interfaces to remote services, and I think that's healthy and fine. As a developer, of course it's less complicated to not be negotiating network communication in order to create an application!

You've even drank some of the koolaid by the personal computer industry to call them applications: real applications clearly run on mainframes and reach the end user via terminal display units!

Re: Why C# coders should shut up about Delphi (2016)

#57
post #41

I love this post. My first gig was slinging Delphi for a telecoms company, my second was C# and I've been involved with TypeScript since it was announced. I'm a complete fan of Anders Hejlsberg work. To the extent that I gave genuine consideration to naming one of my son's "Anders". My wife was not onboard.

As someone that also used languages designed by Anders I'm also a huge fan of his work. Too bad there are just a few quality interviews with him: https://www.artima.com/intv/anders.html

There's a chapter from Anders on [1].

1: https://www.amazon.com/Masterminds-Programming-Conversations...

Re: Why C# coders should shut up about Delphi (2016)

#59

I love this post. My first gig was slinging Delphi for a telecoms company, my second was C# and I've been involved with TypeScript since it was announced. I'm a complete fan of Anders Hejlsberg work. To the extent that I gave genuine consideration to naming one of my son's "Anders". My wife was not onboard.

Could you have gotten away with naming him 'Sharp' instead?

"Turbo Pascal" :-p

Re: Why C# coders should shut up about Delphi (2016)

#60
post #23

Delphi is one of those languages which was a good product from a failing company - Borland. Just as Modula 3 was a good product from a failing company - DEC.

Have they been failing by themselves or have they been destroyed by Microsoft, e.g. [1]? [1] http://techrights.org/2009/09/14/ms-admits-draining-to-destr...

Both.

Anders has a couple of interviews where he mentions that he resisted invitations from ex-Borland colleges that moved into Microsoft.

It was only when Borland stop being what it used to be, that he decided it was time to move on.

Post reply on HN