I used Mercury for a startup a few years ago, they were great. Looks like they have personal banking now, but it's $20/mo unless you also have a business account.
My land is adjacent to public land and yes we have people coming through all the time. There is a forest road that becomes a private road and cuts through our land and people use it. We could put up a fence if we wanted but we don't want to... we're high enough up the hill that as long as people are being cool it's nbd. There are signs and most people (not all) are respectful.
I've found that living next to public land is an insanely undervalued luxury. There's very little I would trade it for.
I’m doing exactly this (in TypeScript) for buildings / construction. It can’t really do woodworking (not designed for that) but I can confirm that it’s an effective strategy for spatial assemblies.
Stealth-ish startup right now (https://bear.build) but we’re working with some large contractors to develop the product. Assemblies are nested and go from a corner detail through walls or MEP systems to levels to the full building being the ultimate assembly.
Snarky comment aside, I am very interested in how we evaluate the performance of these systems and what kinds of work match best with different approaches.
I didn't read it this way. I think I equated it most to "culture" in current companies. A culture that fosters excellence is necessary (but not sufficient) to have a great company. There are also many types of cultures that have been shown to work (ie there's not one right answer).
The article argues (and I think I agree) that how you choose to incorporate agents into your work will be a differentiator and most great companies will have a unique take on it.
With the one I’ve made, it’s best effort. We record whether or not tool calls have succeeded and if the agent dies without knowing whether or not the call succeeded, then when we resurrect it we tell it the state is unknown and it can either inspect the resource or try again depending on the side effects.
Your position appears to be based on crude production and drawing an equivalency between Middle East crude and US crude. They are unfortunately not equivalent. I agree that it’s amazing that the US doesn’t wholly depend on the Mideast for oil, but until we can process our own crude as cheaply as Mideast crude can be processed, strife in the Middle East will still push energy prices up.
I’m biased (my wife works there) but Fireworks or another US-based inference provider is going to be a better fit than OpenRouter. Fireworks has zero data retention by default[1] and has tools to make it easy to run your existing harness against open models [2]
OpenRouter isn’t a provider, they route to other providers, so you would need to specify which ones you’re comfortable with anyway.
I think the parent was referring to hosting the entire NPM registry, not having a project that uses NPM. In that case there's substantial duplication from version to version.
reply