Live data from Hacker News

Announcing .NET Native Preview

blogs.msdn.com

81–85 of 85 posts

Re: Announcing .NET Native Preview

#81
post #51

Earlier quoted context omitted.

That's a language, this is a compiler tech.

That's already known. If you knew anything about 'M#' you'd realize these two have to be related somehow. That's the question.

@BuckRogers, these two are related somehow. We've definitely benefitted from conversations with the M# people and they've likely benefitted from conversations with us. In fact, Joe Duffy once worked for our humble little .NET team :)

Re: Announcing .NET Native Preview

#82

Earlier quoted context omitted.

Probably -- I don't care too much about the windows store, I'm more excited about being able to write C# code that doesn't require a VM. Not that there's anything /wrong/ with the CLR, but one thing I miss about C++ when I'm not writing it is self contained programs where it's just a small exe without a bunch of huge dependencies.

> I don't care too much about the windows store Don't get excited then, this is only for windows store.

Today.

Re: Announcing .NET Native Preview

#83

Earlier quoted context omitted.

No MDIL. NGEN can still JIT for things like cross domain generics and because it loads non-native code, still needs to optimize at run time. Project N compiles to fully native code, so there can be no JIT, and significantly smarter optimizations can happen since they don't impact performance at runtime.

@Pantaloons: Right on all counts. One clarification: .NET Native and MDIL are orthogonal. MDIL was used in Triton to split NGen into conceptually two pieces: the optimized part (in the Windows Phone Store) and the part bound on the customer's device to the installed Framework. .NET Native produces completely native binaries. MDIL/Triton produces NGen binaries that still need a runtime and, occasionally, a JIT.

And Triton is...

Re: Announcing .NET Native Preview

#84

Earlier quoted context omitted.

@Pantaloons: Right on all counts. One clarification: .NET Native and MDIL are orthogonal. MDIL was used in Triton to split NGen into conceptually two pieces: the optimized part (in the Windows Phone Store) and the part bound on the customer's device to the installed Framework. .NET Native produces completely native binaries. MDIL/Triton produces NGen binaries that still need a runtime and, occasionally, a JIT.

And Triton is...

Pay attention, Scott :)

Sorry. Triton is the Windows Phone 8 "Compiler in the Cloud". It basically split NGen into two pieces, allowing the optimization to happen in the Store while the .exe generation happened on the device. The interface between these two halves is MDIL.

Bing will tell you a ton about Triton.

Re: Announcing .NET Native Preview

#85

Earlier quoted context omitted.

And Triton is...

Pay attention, Scott :) Sorry. Triton is the Windows Phone 8 "Compiler in the Cloud". It basically split NGen into two pieces, allowing the optimization to happen in the Store while the .exe generation happened on the device. The interface between these two halves is MDIL. Bing will tell you a ton about Triton.

Sorry, I see this in just one place. Sounds like an internal code name. https://www.google.com/search?q=Triton+.net+compiler
Post reply on HN