> Because it started with the CEO making a WCF service.
The CTO, not the CEO.
From what I understand, you are in fact correct though. The CTO happened to be a MS guy, so the whole company had to be MS.
Did you mean "a WTF service"?
Re:On how Jet.com chose F#
by umanwizard on Wednesday July 29, 2015 @07:01PM
(#9972189)
Not sure if you're just joking or don't know what WCF is, but in case the latter is true:
https://msdn.microsoft.com/en-us/library/ms731082(v=vs.110)....
Can it be both?
Re:On how Jet.com chose F#
by AdeptusAquinas on Wednesday July 29, 2015 @06:59PM
(#9972176)
Although I havent worked with WCF for sometime (Web API is all the rage now), WCF wasnt too bad. Pretty good for making REST services, if you wanted absolute control. They streamlined a lot of the configuration needs in 3.5 and 4.
Best to keep to what you know when you are starting something risky - and there is nothing wrong with the MS stack for this sort of thing.