SoylentNews is people
SoylentNews
Submitted via IRC for AndyTheAbsurd
Today, we're announcing that the next release after .NET Core 3.0 will be .NET 5. This will be the next big release in the .NET family.
There will be just one .NET going forward, and you will be able to use it to target Windows, Linux, macOS, iOS, Android, tvOS, watchOS and WebAssembly and more.
We will introduce new .NET APIs, runtime capabilities and language features as part of .NET 5.
[...] We intend to release .NET 5 in November 2020, with the first preview available in the first half of 2020. It will be supported with future updates to Visual Studio 2019, Visual Studio for Mac and Visual Studio Code
Source: https://devblogs.microsoft.com/dotnet/introducing-net-5/
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Anyone can make an omelet with eggs. The trick is to make one with none.
(Score: 0) by Anonymous Coward on Tuesday May 07 2019, @01:34AM (14 children)
Microsoft apparently has problems with counting.
(Score: 3, Insightful) by Anonymous Coward on Tuesday May 07 2019, @01:49AM (1 child)
.Nyet
(Score: 1, Touché) by Anonymous Coward on Tuesday May 07 2019, @09:49AM
DontNET!
(Score: 2) by sshelton76 on Tuesday May 07 2019, @02:06AM
Truthfully the differences between 3.0 and 3.5 should have warranted a change to major version. Glad MS is finally rectifying this mistake.
(Score: 1, Informative) by Anonymous Coward on Tuesday May 07 2019, @02:10AM
That was Windows 10 AKA NET 4
(Score: 0) by Anonymous Coward on Tuesday May 07 2019, @02:22AM (3 children)
https://en.wikipedia.org/wiki/Chinese_numerology#Four [wikipedia.org]
Just looking out for their Chinese business. [4 is unlucky in superstitious China]
(Score: 2) by DannyB on Tuesday May 07 2019, @01:47PM (2 children)
Why was there an MS-DOS 4.0? Remember that one?
Nope? Neither do most people.
"The DOS ain't done until Lotus won't run!" banner hanging from the wall in the room of developers working on MS-DOS 4.0.
It was bad. Very bad. And I mean much more badder and far worser than the usual Microsoft bad. The efforts to break Lotus also caused it to break many other things.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 2) by Hyperturtle on Tuesday May 07 2019, @02:26PM (1 child)
I thought MS-DOS 4.x let people finally make use of a partition/volume greater than 30MB in size via the FDISK partitioning tool.
Except for that one bug in 4.0 that didn't affect everyone (but when it did...sorry your data is gone)... then they released MS_DOS 4.01 to fix that. I didn't experience it myself, so whatever the trigger was didn't affect me.
But as far as office productivity, really, their tactics with Windows for Workgroups version 3.11 was probably worse. At that time, people had become much more dependent on PCs connecting to mainframes and Novell and other "network" operating systems that the MS approach to the problem of cross-platform connectivity was pretty much the same solution you eluded to in regards to not enough people using Excel...Win for Workgroups broke a lot of competing applications and services.
I don't remember any positive features introduced between Windows for Workgroups 3.1 and 3.11 aside from it breaking nearly everything a business used that wasn't Microsoft, though. Maybe someone here does... maybe it enhanced 802.5 while degrading genuine IBM branded token-ring or something.
At least MS-DOS 4.x provided the option to have much larger disk drives that didn't have to be divided up into 30MB chunks, and better memory management too!
(Score: 2) by DannyB on Tuesday May 07 2019, @02:53PM
Thank God I only had to use MS DOS 3.0 briefly and write some x86 assembly screen handling routines for our software.
Then, years later, my first real use of MS-DOS was 5.0 + Win 3.1. Had to develop for that. Yuk. But I was still mostly a classic Mac developer. Boy am I glad I mostly skipped using PCs until about Win XP.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 3, Informative) by ikanreed on Tuesday May 07 2019, @02:49AM (3 children)
4.0 Came out in 2010. Are you literally a decade behind?
(Score: 2) by c0lo on Tuesday May 07 2019, @09:52AM (1 child)
The SDK, yes. However, the topic is .Net Core, which will skip 4.0
https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
(Score: 3, Informative) by ikanreed on Tuesday May 07 2019, @03:01PM
That's because while the compiler and platform features changed, the actual VM had no changes to support 4.0 or 4.5. All the major changes were in "high level" functionality. Things like async and await were built on existing multithreading libraries. To a developer, they were real features, but to the VM it was indistinguishable from pushing task objects onto threadpools.
(Score: 2) by driverless on Tuesday May 07 2019, @10:04AM
No, he's literally nine years behind.
(Score: 2) by driverless on Tuesday May 07 2019, @09:37AM (1 child)
Yup. 3, 3.1, 4, 2000, XP, 7, 8, 8.1, 10. Sheesh, I know it's "no child left behind" but perhaps it would have been better to let this one repeat a few classes.
(Score: 2) by EEMac on Tuesday May 07 2019, @12:49PM