Hacker News new | ask | show | jobs
by pjmlp 3645 days ago
I went full circle, from a critic how they cloned Java back when my employer had the privilege to beta test .NET as a Microsoft partner, to someone that enjoys delivering solutions on the .NET stack.

For me the sweet spot will be when .NET Native becomes more mature and I can get Delphi/Modula-3 back.

1 comments

What do you mean by "getting Delphi/Modula-3 back" here? There are some implementations for .NET? or that C# is kinda similar? or something else?
C# was originally designed by Anders Hejlsberg, the C# 1.0 features that weren't taken from Java (J++) were based on Delphi, like Properties.

You also have RAD development on .NET.

Although .NET always had AOT compilation via NGEN, it always depends on the runtime being available at OS level.

With .NET Native it is like things were on PC before JVM took off, with strong typed system languages like Delphi and Modula-3 that compile directly to native code.

I know one needs a bit of imagination to make the comparison, but it is how I like to think about it.

FWIW, yes, there is "Delphi for .NET" (but it's actually much more than that - it can also target JVM and Cocoa):

http://www.elementscompiler.com/elements/oxygene/language.as...

i can't speak for the author, but my first thought was the speed. Delphi was almost as easy to develop as Visual Basic, but the result was fast. a native EXE, no big framework-dependencies.
Delphi binaries dont have any dependencies, right?
You can have it both ways, dynamic or static compilation.

If you using COM or third party dlls, which is quite common on Windows, then you need those as well.