I don't have an HDR display, but I do have two high color gamut displays. And when using Linux and my displays set to Adobe RGB all the colors on the screens look neon because color management in Linux (Windows, too) only adjusts LUT values. Only apps like Krita, GIMP, Blender, Firefox (after manual configuration), etc. show correct color. It's pretty annoying. Hopefully that'll change one day.
This is good news. Despite what the article says it's not novel to handle high dynamic range in color management. macOS does this already. The interesting part of this for me isn't the HDR but the fact that Linux will end up with macOS-level color management because of the necessity to clamp the UI to sRGB while allowing anything using an HDR-capable color profile to show as such... like macOS.
Open Source Lego Controller
A mechanical and manufacturing engineer by day, [Tyler Collins] taught himself electronics and firmware development in his spare time and created an open source Lego controller called Evlōno One. It is based on the STM32 and … https://hackaday.com/2020/11/05/open-source-lego-controller/
Original tweet : https://twitter.com/hackaday/status/1324508436554518529
Wow someone sure lost his ever loving mind over having an unpopular opinion about youtube-dl.
I personally haven't used it that much, but when I did I was glad it was there. Last time I used it was when I flew to Canada and downloaded a few videos to watch on the plane there.
Did it cause those people to lose ad revenue? Yeah, but they're not getting any at my house anyway with a pi-hole and ad block.
Blink on Linux has stopped color managing the past few versions. I don't quite know how long. I submitted a detailed bug report with photos, but they barely read what I had to say, spurned my efforts to help, and then labeled it as "won't fix". Meanwhile, it's still broken.
It probably will remain broken for a while because probably precious few people using Linux have displays able to view far beyond sRGB.
There’s no bread let them eat cake
There’s no end to what they’ll take
Flaunt the fruits of noble birth
Wash the salt into the earth
But they’re marching to Bastille Day
La guillotine will claim her bloody prize
Free the dungeons of the innocent
The king will kneel, and let his kingdom rise
-- Rush, Bastille Day (1975)
This has been an excellent resource on something I've been working on, but I'm not sure what to do with aria attributes on a three column web app UI that collapses to a single column on small screens. What exactly is the correct way to go about it here? Was thinking originally of using role="grid" using the layout grid example for guidance and everything that applies with that but that doesn't really apply anymore when it's one column and now has navigation buttons.
What we need is real DOM operations in web workers. It's understandable why we don't, but you don't have to do DOM operations on the main document. Allow DOM operations on a separate temporary document. The worker would message a DOM object back to the main process where you'd adopt the DOM object to the main document before insertion. This is DOM level 1 stuff.
One of the most annoying things in web development is when you have a lot of DOM operations to do, and it creates jank. We have web workers for doing lots of things in other processes... except DOM. React and others bypass it by doing everything in a virtual DOM, but in reality it makes things stupid slow because it's a DOM-like api rewritten in JS.
Designer & Illustrator. Opera Software alum. Ook!
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!