A $1 entry subscription where you have to type your name and credit card and submit and wait and now you have a relationship to manage, is infinitely more expensive than a 10 cent, automatic, non-recurring, one-time, no cancelation needed, pseudonomous, microtransaction.
The key lesson is that duplicate code is not necessarily "code duplication" - it was always really about abstraction duplication. If two unrelated variables happen to momentarily share a value, it doesn't mean that value should be made common between them, they are fundamentally different things. It would be a confusing lie and error-prone if the code implied they were the same and that efforts should be made for them to be in sync.
I did mine without anesthesia/sedatives. There were moments of discomfort when they pump gas to expand the area - feels like a big fart is stuck in your gut - but otherwise no big deal, especially knowing that the pain is not dangerous. Recommend. It eliminates recovery time afterwards (you can drive yourself home) and increases safety.
I interpreted it as: with the nature of fans and the associated vibration/movement, some gap is necessary and this is the limit given the precision of injection molding.
Phrased differently: a 0.5mm gap is the minimum possible to also be able to account for the 0.1mm (or whatever) variation in injection molding.
Who decides things if not the entire voting population? There's nothing inherently wrong with your suggestion, if it's what everyone wants. We've been doing it for a century, see the national debt. But people like their kids, so we restrain it. People don't want a society full of desperation, so we restrain it. People want a strong nation, so we restrain it. It's not a crazy hypothetical, it's how the system works. Humans just aren't basic consumption machines.
Other things that I would like the web to "fix" without knowing the solution:
- replace email for notifications: email is the default notification channel for most websites, but because it is inherently insecure and lacks privacy, messages are often reduced to generic alerts that omit the actual content (statements, bills, secure messages, etc.). Anything of value instead requires navigating to the site, logging in, and locating the relevant item. Ideally, the content itself would be delivered directly through a secure, private notification system without email as a proxy.
- eliminate account creation/login: browsers should be able to authenticate to sites cryptographically using locally held keys, allowing APIs to securely identify and associate a user with an account without explicit registration or login flows shifting credential management from centralized servers to the user’s device, simultaneously reducing exposure from credential storage and leaks.
- automatic selection of gdpr "only necessary cookies" (or whatever your preference) without prompts/ui and similar
Is running your llm through azure insecure? I mean more so than running anything on cloud? My understanding was that azure gpt instances were completely independent with the same security protocols as databases, vms, etc.
Say you do have those sub-agents, they will likely each have tools, and sometimes many, in which case you'll have you route to those tools somehow. The sub-agents themselves are also almost like tools from the main root agent's perspective, and there may be many of those, which you also have to route to, in which case you can use this pattern again. Put simply, sometimes increasing the hierarchy is not the right abstraction vs having many tools in one hierarchy, and thus the need for more efficient routing.