RayJW

joined 2 years ago
[–] [email protected] 2 points 1 year ago (1 children)

That's very noble of you, but as you will see in their repo they are still in pretty early stages of development and don't have a lot of advanced features yet, so don't worry about opening issues about such features. I think it helps them to prioritize!

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Great to hear and good luck! Another good thing to know is, that you can always convert back and forth between JPEG and JPEG XL without any data loss, I love that functionality!

[–] [email protected] 6 points 1 year ago (2 children)

https://res.cloudinary.com/cloudinary-marketing/image/upload/w_700,c_fill,f_auto,q_auto,dpr_2.0/Web_Assets/blog/Battle-of-the-Codecs_fnl.png

This is one of my favourite comparison of the bunch. Tl;dr JPEG XL is actually made for pictures and not just a still frame of a video and it truly shows. Cloudinary has a lot of great content talking about its advantages for the web: https://cloudinary.com/blog/tag/jpeg-xl

[–] [email protected] 2 points 1 year ago (3 children)

Honestly, I don't know if that is a problem yet. It's still very much WIP, but someone might be willing to work on an extension for closing tags if you open an issue! :)

[–] [email protected] 2 points 1 year ago

Definitely, it's already a great code editor, but it still needs some work to be a good ~IDE replacement. But it's looking great and the progress is impressively fast.

[–] [email protected] 2 points 1 year ago (7 children)

Honestly not working on it at the moment but been meaning to for a long time: lapce.dev I'm tired of every application being another Elextron wrapper with outdated versions having issues. VSCodium for me literally takes hundreds of MBs for just a small like ~20 files project and the native Wayland support is still lacking big time. It's time we go back to native applications!