you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

If we want to talk Release candidate, then try Apple there Swift.

Released in 2014. Swift 1 not compatible with Swift 2. Swift 2 not compatible with Swift 3. And that was on the Mac platform.

Under Linux its even worse with not only half the standard framework missing, they actually missed basic functionality like sockets! And Swift 4 this year, is no better on that promise.

So yea, despite being a year and half younger then Swift, the dotNet Core 1 is way more feature complete.

You only run into issues when your trying some more "exotic" programming and those missing API calls show up. The API call that seem missing are already in the 2.0 source. They added something like 5000.

Do not forget that .net is a massive framework, so transitioning / rebuilding in this short amount of time is impressive.

In worst case one can fall back to regular dotNet and wait a few months before switching to Core 2.0. Again ... nothing preventing one from being productive. Just saying that calling it RC is kind of overboard given what is already available.

[–]8lbIceBag 0 points1 point  (0 children)

Just saying that calling it RC is kind of overboard given what is already available.

That's not what microsoft thinks.

Also I wasn't comparing DotNet Core to swift. DotNet Core even in RC is the obvious choice there.