HN user
They bundle uBlock Origin into their Chromium fork, I expect that if it became too difficult to support the APIs needed on MV2, they'd integrate the features more directly into the browser.
I would recommend folks check out Helium (https://helium.computer) it’s fast, basically just ungoogled chromium, and has full support for ublock origin.
That seems really unfair because every other search engine also as "AI" integration. Kagi's is tasteful and only used when you seek it out.
This entire article is an example of the largest pain point when working with React. So much of the work done here simply can't be done without various hacks around `useEffect`, `useMemo`, or `useCallback` (manual memoization). I feel to this point that even with the new React beta docs explaining the use cases for `useEffect`, it still causes an immense amount of pain in some situations.
It's not immediately clear when writing code that uses `useEffect`, when it's a very bad idea long term for performance or code clarity. This often shows itself when the test data is very minimal and then the real data is far more expansive.
I still love React, but these complex scenarios definitely show some of the limitations in React's rendering model that other frameworks like Vue, Svelte, and SolidJS resolve.
I don't think it's a great idea to integrate with other work in progress, living on another feature branch. As far as maintenance releases go, strategies for resolving this are well documented here https://trunkbaseddevelopment.com/branch-for-release/#fix-pr....
What exactly is a drawback of Trunk-based development for developers?