Vortice.Windows VS ImageSharp

There are quite a lot actually, even if we ignore engines and frameworks (though some of them are quite low level). Some of the biggest are Silk.NET, Vortice.Windows, SharpDX (the last one is dead but it still should work well).

In C#, that means you'll need something like Vortice.Windows or Silk.NET. If you just want WIC (and not a bunch of DirectX stuff, there's also a plain old WIC interop library. And if you don't mind a well-tested, yet end-of-life library, there's SharpDX.

These days, you're better off with Vortice.Windows or Silk.NET.

For those looking for an alternative to SharpDX, Vortice.Windows is an option.

Microsoft has refused to support it. There have been community-made managed wrappers for DirectX, but SlimDX died years ago and SharpDX was abruptly abandoned and its github archived in early 2019. There's a new one called Vortice that seems to be trying to pick up where SharpDX left off.

> 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.