2 ms·
There is nothing concerning Windows 10X that undermines anything I have said. UWP is the future of Windows - correct. I'm not sure any significant part of UWP
by nbevans 6y ago
There is nothing concerning Windows 10X that undermines anything I have said.
UWP is the future of Windows - correct.
I'm not sure any significant part of UWP has ever been in the kernel per se.
It sounds like you're a consultant where taking risks on behalf of your customers, no matter how small or logical the risk, is obviously not part of your job description.
Your offerings of good luck appear to be disingenuous.
- pjmlp 6y agoPicking F# over official supported languages has zero value on the sales of customers, that is what they care about, not cool software stacks. So if their IT goes down and the reason is that a risky loving consultant used unofficial workarounds, I rather not get unnecessary phone calls. As for the wishing luck, I was being honest, take it as you wish.
- nbevans 6y agoWe've been running F# in production since 2014 - almost 7 years. It is quite shocking to hear anyone imply that F# is not ready for production use - that it is just "cool" tech. (when has F# ever been cool in the minds of the masses?) I suspect you'll say "7 years is nothing" and maybe it is nothing. But it is still something. It is long enough that we made a couple bad framework/library dependency choices early on and to have learnt lessons from such mistakes. By far the biggest technical challenge we've faced in that time is the .NET 5 migration - but even that might turn out to be a lot easier than I currently envisage.
- pjmlp 6y agoOn the context of Windows GUI frameworks and UWP, no it isn't ready. Still no VS or Blend tooling support, no project templates and .NET Native requires workarounds with stuff that most corporate enterprise developers don't care to learn.