3 ms·
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. Unfortunat
by seanmcdirmid 8y ago
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).
- benaadams 8y ago> 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?
- seanmcdirmid 8y agoI 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.
- pjmlp 8y agoThey 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--2018/T150 https://channel9.msdn.com/Events/Connect/Microsoft-Connect--... The video is not yet available though.