JARVIS VS Microsoft.Maui.Graphics

Jarvis: github.com/microsoft/JARVIS

You can build it yourself now. https://github.com/microsoft/JARVIS

https://github.com/microsoft/JARVIS (when ready says >=24GB VRAM)

Can be. There are projects that run fully locally like Microsoft’s Jarvis. https://github.com/microsoft/JARVIS

JARVIS, a system to connect LLMs with ML community (https://github.com/microsoft/JARVIS)

HuggingGPT is a clever idea to boost the capabilities of LLM Agents, and enable them to solve “complicated AI tasks with different domains and modalities”. In short, it uses ChatGPT to plan tasks, select models from Hugging Face (HF), format inputs, execute each subtask via the HF Inference API, and summarise the results. JARVIS tries to generalise this idea, and create a framework to “connect LLMs with the ML community”, which Microsoft Research claims “paves a new way towards advanced artificial intelligence”.

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