News for hackers. Stuff that matters.
Re:Type erasure and reification by seanmcdirmid on Wednesday December 05, 2018 @01:46PM (#18611168)
The DLR was only going to ever work out for dynamic languages, and even then I think it was pretty limited to class-based ones like Python and Ruby.

Unfortunately, the DLR seems to be pretty much deprecated at this point. Its a shame, I was able to do great things with the run-time generation API (which now defaults to an interpreter in UWP).

Re:Type erasure and reification by benaadams on Wednesday December 05, 2018 @03:18PM (#18612085)
> Its a shame, I was able to do great things with the run-time generation API (which now defaults to an interpreter in UWP).

That's more to do with UWP being a AOT platform than it being deprecated; it should still work fine with .NET Core?

Re:Type erasure and reification by pjmlp on Wednesday December 05, 2018 @03:57PM (#18612462)
They are rebooting the .NET AOT story after the 3.0 release.

It was discussed during this week Connect(), on the ".NET today and tomorrow" Q&A session.

https://channel9.msdn.com/Events/Connect/Microsoft-Connect--...

The video is not yet available though.

Re:Type erasure and reification by seanmcdirmid on Wednesday December 05, 2018 @03:41PM (#18612303)
I have no idea. I’ve mostly been interested in UI work anyways, and not being able to move to the new UI stack really sucked for me. Now it’s all just a bunch of bad choices.