4 ms·
But there's a catch, isn't there? There's always a catch. At work (Big Company TM), we call it the "MS Happy Path." If you're on it, you're golden and life i
by mullr 17y ago
But there's a catch, isn't there? There's always a catch. At work (Big Company TM), we call it the "MS Happy Path." If you're on it, you're golden and life is good. The overall development experience is great. If you're not, well, sucks to be you. With the other choices you probably have a way out. Even if there's no scaffolding for you, you can at least implement something yourself. Granted it takes more time up front, but it pays off when your priorities vary from those of your tool vendor's.
We've made lots of choices explicitly for the purpose of staying on the MS Happy Path, since we knew it would make our life easier. Not because they were the best solution to the problem.
- joe_the_user 17y agoWow, This is the first time I've heard anyone else describe the happy-path phenomena, yet I previously talked about it any time anyone ever asked about the goodness of MS software. I'd also mention that the Happy Path is also a verbose path. I recently looked at a C# application and a C++ application that each did about the same thing. I was amazed to find the C# app had least ten times the source code. Moreover, the C# app seemed to be coded in the proper C# way and worked generally well. The main thing is that the problems that it did have (memory leaks) were utterly, irrevocably, totally, completely unsolvable... So there are trade-offs in all these things that are very "unobvious"...