Oh that’s what they mean by “subagents”, now I get it.

On mobile there’s a snowflake toggle button in the top left corner. I only noticed this after reading the whole article in reader mode and wondering why my iPhone was on fire…

Yep also ran into this while trying to search the article. It’s maddening when the share action is now also hidden within a context menu.

I was starting to wonder why my iPhone got crazy hot. I’m using reader mode and it appears to continue running the web page and animation in the background… crazy.

> I'm speculating here but I'm pretty sure if you did an MRI on my brain you'd see lesions from the mixing of mdma and sertraline (I get myoclonic jerks to this day).

Could you speak more to this? A family member was recently diagnosed with myoclonic jerks without a clear root cause, so treatment has been hit or miss so far. I’m trying to learn what I can to help inform them.

> Really... how data flows through your program is actually a separate graph structure, and how HTML elements are organized in your program is another separate graph structure we try to graft into the first one and that creates a mess.

My team migrated away from Redux and for over a year I’ve been unable to pinpoint why I’ve been longing for it again. This has hit the nail on the head for me. Redux (and other “global” state management solutions) allowed me to decouple the data graph from the UI graph. When a UI event is triggered, an action is dispatched and then the data graph takes over. This makes the UI graph extremely simple - render UI and dispatch actions - but these days we’re mixing state with business logic, event handling, API calls, rendering UI, styling, etc. This is very much a problem of our own making that could be solved by a different architecture, but yeah… thanks for clarifying this feeling for me.

Yes but this doesn't solve the problem fully.

because any component that uses that state management solution becomes coupled to that global state. So let's say I want to use such a component in context of a completely different "global" state, then I can't do that anymore. Global state only saves you from prop drilling where you have to insert props into every parent element above the relevant element.

Believe it or not Jquery + html actually did the seperation of data flow and GUI much better than react.

The question is, how do I get re-useable GUI widgets that are decoupled from state all together such that every widget on my SPA can be reused anywhere on different global contexts and even on different apps. React does NOT solve this problem.

For windows: https://obsproject.com/forum/resources/obs-virtualcam.949/

The CEO of Shopify put up a bounty last year to support similar functionality on macOS, I’m not sure if it was ever completed.

EDIT: looks like OBS officially supports it for Mac and Linux since 26.1 - https://github.com/obsproject/obs-studio/releases/tag/26.1.0

Yes that is what I am saying, teams broke virtual cams unfortunately

I understand the sentiment, but a better comparison would be if your tool of choice had to be shared between everyone on your team.

Would that imply that the GP needs to reconsider their willingness to use TypeScript, or is it just a friendly reminder that there is utility in finding teams with shared values?

> This is surprising to me because I find content locks and editing friction very annoying.

The first rule of UX design: it’s not about you.

Perhaps OP isn’t Notion’s target audience, but dismissing something because you don’t share their perspective is not great.

I think you’re conflating UX with UI, which is usually the cause of confusion in these discussions.

What you’re advocating for - solving the problem - is the essence of UX design. Visual design is only part of the design process that comes after user research, information architecture and interaction design.