Microsoft.Maui.Graphics VS ImageSharp

Microsoft.Maui.Graphics (which relies on Skia anyway but whatever)

I'm not sure if this is out of scope for https://github.com/dotnet/Microsoft.Maui.Graphics, but that seems to be the designated successor to the platform-specific graphics libs.

Yea, they can keep using the old versions, but that locks them out of the new versions and breaks expectations, especially since they were a member of the .NET Foundation. So it's up to them to keep using a version that won't get fixes or new features or accept the new license.

This whole thing just points out how hard all of this is to get right. I understand both sides. But I do at least get the feeling that the ImageSharp team is a bit high strung.

https://github.com/dotnet/Microsoft.Maui.Graphics/issues/47

I think this is probably an intentional move to move away from Microsoft and the .NET Foundation in addition to trying to capitalize on people making a lot of money from the software package.

After having looked at the license, it seems reasonable enough to me aside from the technicalities others have brought up. The vvvv tool follows a similar license of, it's free unless you make money from it.

You can also write a MAUI app and then use https://github.com/dotnet/Microsoft.Maui.Graphics.

This set of SkiaSharp views can be added to any .NET MAUI application for drawing. This is similar to what you can do with the built-in GraphicsView and Microsoft.Maui.Graphics, but directly to SkiaSharp.

There's Microsoft.Maui.Graphics as well so that the renderer will not rely on native controls just like Avalonia and Flutter (but currently it's experimental). MAUI's flexible enough to enable that scenario, the bigger question is more on motivation from either MS or the community to make it happen.

For colors you have your choice of solid paint, linear and radial gradient paint, and more provided by Microsoft.Maui.Graphics.

This work is a pre-cursor to Blazor WebAssembly support coming in the Microsoft.MAUI.Graphics repo, giving us a single .Net API to draw on all platforms MAUI supports, along with Blazor.

In .NET 6, there will be Microsoft.Maui.Graphics (doesn't depend on Maui, despite its name).

> High quality progressive decoding at reduced filesizes is a big positive for me.

This is really cool!

Honestly, I want to use regular progressive JPEGs for a current project of mine, but it seems that even that doesn't have support in all the tech stacks yet despite how long it's been around for, for example: https://github.com/SixLabors/ImageSharp/issues/449

Here's hoping that in the case of JPEG-XL this will be more commonplace!

Here's an example:

https://github.com/SixLabors/ImageSharp/blob/main/LICENSE#L2...

https://news.ycombinator.com/item?id=33301518

Again, nothing stops someone from forking and maintaining.

Are you saying this is not legally enforceable? Because I am under the impression from my legal council it is. I can ask again to get more clarity.

ChatGPT is very good at being confidently incorrect. I asked it for some programming related thing and it gave me some code that used a class from a library as if it was generic, when it was not, and even made up some classes. You should also remember that things have since updated and things that might have been true back in 2020, may not be anymore. SixLabors.ImageSharp, for example has reworked some code since then and ChatGPT regularly messes up the methods that it uses, most notably Image.GetPixelSpan.

There is one in dot net too https://github.com/SixLabors/ImageSharp

ImageSharp is another option, but could have licence implications.

One example from the top of my head is ImageSharp.

Library users should come together and fork the last open source version (https://github.com/SixLabors/ImageSharp/tree/v2.1.3) and maintain that together. Just having a version still available, even if it's got no new features, may be enough to make the Six Labors reconsider their approach because why pay for a library that can mostly work for free?

Since .net doesn't yet support avif and neither does ImageSharp, files of this type just didn't have a MIME type available and trying to use them would result in a 404 error.