News for hackers. Stuff that matters.
Re:Windows 10 and .NET Native by lmm on Saturday October 03, 2015 @01:23PM (#10324576)
> Being used to memory safe languages with AOT compilation like Turbo Pascal, Modula-2, Modula-3, Oberon, Delphi, Ada among many others, I also would have prefer that Java and .NET had offered the same type of toolchain from the beginning.

Do those languages offer consistent, defined behaviour on all platforms (e.g. for integer overflow)? Particularly in the context of multithreading - do they have a crossplatform memory model? That to me was the big advantage of the JVM.

Re:Windows 10 and .NET Native by pjmlp on Saturday October 03, 2015 @02:15PM (#10324810)
They had their own set of issues, but not even close to the anything goes of undefined behaviour across C compilers.

That was actually a reason why many of us embraced Java.

C compilers were between K&R and C89.

C++ compilers were even worse with the standard still ongoing.

These other languages suffered from not being adopted by OS vendors and as you remember, back then we used to pay for compilers. So not being part of the official OS compilers was a burden to adoption.

Java being C++ like, more consistent behaviour and free (as beer) won the hearts of many.

Re:Windows 10 and .NET Native by amaranth on Saturday October 03, 2015 @02:18PM (#10324828)
But those have almost nothing to do with using a VM. You can achieve them with your compiler by emitting overflow checks and fences where appropriate to match the defined model.