5 ms·
This is getting down-voted, but there's some truth here. I didn't adopt .NET Core until v2, and happy I waited. Much stronger support from MSFT now, and a much
by softwarefounder 8y ago
This is getting down-voted, but there's some truth here.
I didn't adopt .NET Core until v2, and happy I waited. Much stronger support from MSFT now, and a much more stable framework.
- setquk 8y agoExactly the other side of my point. Once it’s supoorted it’s good.
- noir_lord 8y agoInsane performance on the most recent techempower benchmarks (usual proviso of all bencharks are meaningless etc etc.) they've caught Go with fasthttp already on one of them.
- Thaxll 8y agoNot sure if it's good or bad, fast http is made by one guy and it's not official, aspcore is done by MS and dozen of engineers work on it.
- noir_lord 8y agoboth top the charts and are within 1% of the fastest on the chart so pretty good for the go dev and MS.
- manigandham 8y agoASP.NET Core is a full-stack web framework and has about 100x more features and support. fasthttp is quick but it doesn't even implement the http spec completely.
- setquk 8y agoFor typical workloads that doesn’t make a whole load of difference. 10% difference in API meh. 90% of the latency and load is what goes on behind that and that’s your party not theirs.