qoi VS toit

Her request is politely-phrased and reasonable. I don't think there's a legal or ethical issue, but respecting the wishes of others when it costs nothing is just kindness.

However, the way that some have seized on it, and then interacted with others in their communities is ... neither polite nor reasonable.

e.g. https://github.com/phoboslab/qoi/issues/35

How do you know it's not a problem for the people who work with computer vision? Let's take this for example - sure, the request itself was presented very unprofessionally, but this is still an example of someone in a computer vision-adjacent field stating in no uncertain terms that they have a problem with the image.

Yes. Without a supporting statement, it's ad hominem. But I provided a supporting statement.

This is the issue I'm taking about: https://mobile.twitter.com/richgel999/status/146443578680850...

Which links to here: https://github.com/phoboslab/qoi/issues/35

Where everyone agrees, yes, the image should be removed. They didn't know about its history. Would he please stop being a gigantic asshole about it.

So if that's not blowing things out of proportion, I don't know what is.

I don't know about CUDA, however I've made an AVX2 based encoder a few months ago : https://github.com/phoboslab/qoi/pull/143

I intend to create an AVX2 based decoder but I had absolutely no time to work on side projects in the past three months.

You might also want to take a look at this streaming encoder if you want to encode large files with a tiny memory footprint : https://github.com/MKCG/php-qoi/blob/main/src/FFI/lib/qoi.c

Not only does compression improve this situation today, but using QOI means improvements may continue to come over time. QOI is a very new, open source image format, and that's already proving to be an advantage. By itself, QOI compression is pretty weak, but YoYoGames have forked it and worked in BZ2 compression to surpass the old PNG format. As QOI itself improves and as YoYoGames continues to work on it, it's almost guaranteed that we'll see the compression ratio in GameMaker get better over time.

It uses toit, a high-level language, and is thus quite easy to learn. At the same time it's an order of magnitude faster than micropython.

We have been faced with the same question and decided to open-source pretty much all of our product (https://github.com/toitlang/toit).

I also really like MicroPython! Having said that, I have been working on an alternative to it for a number of years now -- primarily to provide a more robust and performant high-level alternative to C and Rust on the ESP32-family of chips:

https://github.com/toitlang/toit

I'd love to pick your brain and fully understand your experience with MicroPython. I've been doing programming languages for a number of years now, and I find that it is incredibly useful to understand what developers appreciate (and dislike) about the available stacks.

Thank you for the mention!

I have been working on the Toit language for the ESP32 for a number of years now -- and it has been an enjoyable challenge to build an open source stack capable of supporting live reloading on a micro-controller that can run for years on batteries.

https://github.com/toitlang/toit

We use it for some of our tools, so it's possible (and works nicely). Our LSP server was initially written in Toit: https://github.com/toitlang/toit/tree/master/tools/lsp/serve...