I find it unbelievable that they would even consider releasing this without System.Drawing or equivalent being available.
So many people would embrace a truly cross platform framework will all bells and whistles. But instead we have this disturbing split between .NET, .NET Core and Mono.
Long term Mono is probably just going to become a sort of .NET "distribution" on top of .NET Core, it will include things which Microsoft deprecated such as Winform. And it will probably be not maintained at the same level .NET Core itself is. I don't think there will be any reason to use Mono in the future, except for legacy Mono apps...
Take a quick scroll through here: http://referencesource.microsoft.com/#System.Drawing/commonu...
To re-use System.Drawing Microsoft would need to re-implement all those methods in a cross-platform, bug-compatible way. And there's a lot of code behind those methods.
In my opinion they made a reasonable decision to leave it out of v1.
Even for websites, depends on what sort of websites you do, but I often need to display charts, so being able to generate images on the fly.
Isn't SVG or canvas more suitable for that on the web?
I have written a few commercial cross-platform applications with Xamarin. They deal with images - and System.Drawing would not have been helpful to me. iOS has UIImage and Android has Bitmap.
Frankly, the thing I liked best about the whole .net ecosystem is that it didn't go for the open source "release early, release often, release incomplete and buggy" philosophy. I'm just very disappointed to see Microsoft going in this direction.
If Microsoft isn't providing a rock-solid, feature-ful framework with impeccable backwards compatibility, who will? Nobody will.
System.Drawing is a good example, if you read the msdn docs it is clearly not supported on ASP.Net or from a Windows Service.
Libraries like imaging should be a nuget package.
