I've noticed that toggle sets a local storage entry, but the value of it doesn't appear to matter at all for new tab loads. I hoped it's "just" a UI bug, but some agent-driven reverse engineering of the page should reveal the answer, as well as how intentional it was.
OpenCode has been great in my experience. I still get the best results using it with Anthropic's models, but some of the open weights ones are catching up (GLM 5 works reasonably well for me).
I had the same thought too. It's probably not too difficult to fine-tune a small model for it using the "introduce a random mutation and describe the issue" workflow from TFA
rillian was also instrumental in helping to integrate Rust into Chromium at Brave. I worked with him for a few years; since getting to know him, I started noticing his handle in the contributors list across a surprisingly diverse range of other open source projects. RIP, Ralph.
fwiw, LEDs with higher CRI will generally be less power efficient, so the premium category has a 3-way tradeoff between brightness, power, and color quality. It's common for high efficiency LED lightbulbs to be much worse at illuminating red objects.
True enough, although CREE's XT-E offers 140 lm/w at a CRI of 80 and a colour temp of 3000k.
I assume this product has not met any regulatory requirements, because selling a ~600W hot plate suspended at eye level cannot be legal.
These LEDs are just the ones found on imported LED strips. Adjustable colour temperature is a novelty that is not compatible with LED efficiency or lifetime.
Fair point. Given that this product has adjustable colour temperature, I really doubt all of the lumen, CRI and watt values. It sounds like the designer also got stung when the chosen LEDs didn't give the expected power output.
FlatBuffers was definitely the majority of the improvements here!
On 64-bit systems, pointers themselves can really start to take up a lot of memory (especially if you multiply them across 100k+ adblock filters). Switching to array indices instead of pointers saves a lot of memory that's otherwise wasted when you don't need to address the entire possible memory space.
I guess code bloat is proportional to schema complexity, and performance improvement is proportional to volume, so in ad blocker with many large block lists the latter dominates.
The biggest improvement for us was deduplication by using generators an referencing already emitted objects. Don't run flatc on a JSON, it doesn't do that.
reply