I'm a big fan of Functional enhancements but I would put all them aside for the performance enhancements you speak of. Much less copying, pointer returns, Native Buffers, all that sounds great. I even wrote my own buffer wrapper around VirtualAlloc so I could get aligned memory that worked super fast with file system pinvokes. Was working on a super fast .net persistent queue and write ahead log. To be honest I would love to see tons more performance related enhancements to the language.
I'm so excited about all of this, declarative with a way of extending declarative models and hiding all the imperative scripts seems obvious to me. I'm so glad this is becoming the norm for Azure and On-Prem deployment. I wish it would leak into my coding world more than just deployment. I'm a huge fan of declarative approaches with the ability to add new declarative features backed by imperative code.
Okay one question, can I do any of this On-Prem yet? Even with 2016 preview versions? If so can you point me to any tutorials? Azure Stack installs? Thanks.
I have not seen any videos on how to take errors from grunt and redirect into the ui. For instance if I were compiling less or some other type of file I would like to show errors in the vs error window and be able to double click to take me to the failing line of code. Thanks.
@wkempf: I agree with you on your opinion of IObservable vs Task. Tasks are great in their place but if IObservable is the right decision because of a reoccurring event then you loose a lot of composition options if you return a Task instead. Too bad I can't give you a plus one
@ljw1004: I also think these async tips have been very informative and would love to see more on the subject in a more in depth fashion.