3 ms·
"platform" is vague and doesn't describe much on its own. .NET is vast, and the runtimes are what actually run the code packages on various devices. .NET Frame
by manigandham 8y ago
"platform" is vague and doesn't describe much on its own. .NET is vast, and the runtimes are what actually run the code packages on various devices.
.NET Framework has been the original Windows implementation and now we have a fast, lightweight and modern cross-platform implementation with .NET Core. It makes sense to consolidate on a single runtime that now works well on Windows and is at 99% parity with legacy features.
- garganzol 8y ago.NET Core is not on par. It is seriously lacking in vision and attitude. It has some nice properties like portable deployment and that's basically it. The rest is just one to one copy from .NET Framework, plus a bit of quick and dirty additions here and there without a further thought. Please note how the latter statement signifies the endangered future state of the platform.
- manigandham 8y ago"vision and attitude" is 100x more vague than platform. Care to actually explain what you think it should be then? .NET Core is cross-platform. That is a massive change that you seem to just ignore.
- deleted 8y ago[deleted]
- Mountain_Skies 8y agoHopefully Core 3 has better serial port support. I've run into all kinds of edge cases for serial ports where things work great on the .Net framework but are flakey or non functional on Core 2. It's my only major complaint about .Net Core.
- caseymarquis 8y agoI've had better luck using OS api calls for serial ports. It's not portable, but it's the only way to understand the behaviour of the underlying driver, which can vary greatly with different hardware. It's very hard to get a vendor to fix their driver and firmware when you can't tell them which API calls they're making a mistake in.