Will Browar 👨🏻‍💻

@nhoizey@mamot.fr @gianni@disobey.net I couldn’t argue with the data here, and I understand that the argument in this post are more on the compression side of things that the end user will benefit from, but I think the reason I’m still excited about JPEG-XL is the idea of simplifying the authoring workflow. I wouldn’t want to store my photo library from my phone or mirrorless cameras as AVIF or WebP images, but I can see a world where shooting in JPEG-XL would be a good replacement for JPEGs (maybe not as good as RAW, but more capable than current JPEG at least). From there it would be great to be able to upload off of a camera or phone, review the source images in a CMS or publishing platform, and do more of the editing process in the browser. Then, if the image is compressed and converted to a WebP or AVIF, that might be the best way to go for the front-end. JPEG-XL might not be the answer, but as much as I understand that JPEG-XL isn’t always the best image compression tool, it could open up more options for image creators than I think the current formats achieve.

@BenRiceM@mastodon.social enjoy! It’s a good one.

@ianh@phpc.social that is some bullshit and I’m really sorry. Hope you get a new gig figured out soon.

@teleclimber@social.tchncs.de oh, that is cool! I looked at the Hello World example and I like how simple the user management stuff is.

@adactio looks like a fun show!

@craftcms@masto.craftcms.com a good year, indeed! It sounds like 2026 will be an exciting year, but it’s good to recognize good progress made already!

I’ve been making some progress on the 2.0 branch! Keyboard navigation is done, but I’m still working out focus-visible styles. I also added aria-labels where I think they make sense. Plus made it easier to extend these components. #WebComponents #CSS #JavaScript #HTML #CraftCMS

@vale totally! Every time..

Here’s a link to the project repo, in case anybody’s interested in taking a look: https://github.com/wbrowar/kids-money/

I’m leaning towards re-writing it in Node/Vanilla JS and HTML since upgrading it might take just about as much time. I was planning on removing Tailwind and rewriting and re-structuring the HTML anyway. #WebDev

As of last night I got through the list of things in here: https://wbrowar.com/article/code/critique-my-web-component-please#project-goals I also went down a path of a new feature that I think wraps up all of the 2.0 items! Just need to finish some tests 😀 #WebComponents #CSS #JavaScript #HTML #CraftCMS

Also, while I don’t feel like I’m “allergic” to frameworks, I find myself no longer assuming one is needed. I’m still not sure how I feel about LLMs, yet, but I wonder if I’ll come to the same place eventually.

@gianni@disobey.net @nhoizey@mamot.fr from what I understand (and I’m not an expert, so I’m happy to learn here), JPEG-XL can get you closer to RAW in terms of what features the format supports (higher resolution and color depth), so if you want to hang onto the most data from the cameras that you can, it sounds like JPEG-XL works better as a source file than AVIF. So not to say AVIF wouldn’t work here, but knowing that JPEG-XL is on the way to full browser support, that’s the one I’d like to see camera makers adopt as a replacement for JPEG.

@BasicAppleGuy@mastodon.social I only know about this because I have kids who watch the shows. There is a whole line of Pear-based tech devices in the Dan Schneider universe: https://icarly.fandom.com/wiki/Pear_Company

@mvsde@mastodon.social thank you! I’ll keep an eye on colorspace because that’s exactly what I was looking for.

I saw a few web component color pickers that support extended color pallets, but it would be very nice to have it through the browser.

@stublag@xoxo.zone Paul, you have a really great style and I hope this works out for you. The site looks great, by the way!