2 ms·
This is always their answer - whether it's about .NET vs .NET Core, Winforms vs WPF, ADO.NET vs EF, Webforms vs MVC, or even language features like "var" (remem
by efdee 7y ago
This is always their answer - whether it's about .NET vs .NET Core, Winforms vs WPF, ADO.NET vs EF, Webforms vs MVC, or even language features like "var" (remember that originally they would tell you to avoid 'var' unless you're dealing with Linq).
"The new thing isn't immediately going to replace the old thing going forward" and then it does.
(And it should. I just don't get why they're always tiptoeing around that same point.)
- algorithmsRcool 7y agoWell in this case they have made clear that WCF isn't going to be supported officially in dotnet core. They are just being non-committal about gRPC being the successor. But I have seen Fowler poking around in the RSocket codebase recently, so who knows.