Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

jonlennartaasenden.wordpress.com

Post reply on HN
Print view View original

11–20 of 162 posts

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

#11

Post by icelancer »

chrisco255 wrote: post #10
trixie_ wrote: 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…

Oh really? Please tell me about the ultra-productive "Built For Internet Explorer" days of web dev.

>> client side apps

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

#13

Post by pjmlp »

ComputerGuru wrote: post #8

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…

Unfortunately .NET Native seems to be on the way out with the project Project Reunion, and it is not clear how AOT support will be like post NET 5 release.

So far they are demoing single file release, which is basically packing everything into the same exe, but you get a JIT + MSIL instead.

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

#14

Post by dleslie »

trixie_ wrote: 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!

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

#15

Post by Jaruzel »

cttet wrote: 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.

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

#16

Post by cttet »

chrisco255 wrote: post #10
trixie_ wrote: 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…

Oh really? Please tell me about the ultra-productive "Built For Internet Explorer" days of web dev.

In 2008 I only tested my CSS-heavy small website on my only browser, which is IE6 and quite content with it.

Until I knew more later and it became a disaster.

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

#17

Post by watersb »

chrisco255 wrote: post #10
trixie_ wrote: 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…

Oh really? Please tell me about the ultra-productive "Built For Internet Explorer" days of web dev.

Most development in the 20th century was not web development.

Sure, there's always a tension of "simple" versus "limited". But simple was fun.

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

#18

Post by beamatronic »

trixie_ wrote: 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…

I very badly want to get back to this. Maybe with Python and Qt on Mac?

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

#19

Post by johnny_reilly »

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.

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

#20

Post by pjmlp »

Satire or not, one thing I do fully agree.

It was a big mistake not embracing AOT from day one, C++ wouldn't have kept its king position in MS ecosystem if the original .NET had been like .NET Native since the begging and kept Delphi like features for low level coding (some of each are have been added since C# 7.x).

JIT support could still be an additional option as well, just like on languages like Eiffel.

Instead we got NGEN (with basic optimizations), .NET Native (out of Midori, but which seems on the death march with Project Reunion), MDIL/Bartok (out of Singularity, used only in Windows 8.x), and all remaining efforts are from third parties (Xamarin pre-acquisition), Unity, CosmOS.

And no one really knows if CoreRT will ever be integrated into the main product.

Post reply on HN