ImageSharp VS Veldrid

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

I'd recommend Veldrid

So, for example, Veldrid, a low cross-platform graphics API-agnostic rendering and compute library for .NET, has its own bindings to provide different graphics backends. How were those created? Is it a completely manual process? are tools available? How are those maintained?

https://github.com/mellinoe/veldrid and https://github.com/dotnet/Silk.NET are nice wrappers around several graphic apis

Check out Veldrid.

Veldrid is a lower level engine that abstracts away a bunch of backends for you. Youll have to build your own pieces on top.

Also noteworthy: Veldrid

in addition to what everyone has said already, take a look at https://github.com/mellinoe/veldrid

Veldrid for graphics although I think SILK.net would also work well.

If you’re interested in C#, You could look into Veldrid. It is 3D however, so im not sure how easy it is to do 2D with it. ImGui.NET is a set of .NET bindings for Dear ImGui, which is one of the best immediate mode gui librarys out there imo. It has a canvas feature which allows you to draw 2D shapes via the gui renderer. Also, the creator of Veldrid and ImGui.NET has an example project for ImGui.NET using veldrid..

Veldrid attempts to wrap several graphics api, directx11, metal, opengl, and vulkan. You would have to write most things from scratch but this lib will work cross platform. Probably not consoles though.