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.
@luzi:I admit that "magic" strings make me cringe a little but after dealing with distributed systems for a number of years and all the headaches around versioning and in place upgrades, etc... Even something as simple as an enum can be a real pain. I'm fine with the "magic" strings as long as their are nice abstractions on top of them. I would consider the "magic" strings almost like Assembly or IL, Wrap them nicely then you only rarely have to think about them.