Right, the issue is that we are owning our stuff less and less. You used to be able to even buy a copy of an OS on a CD. Thus, I don't think a subscription justifies the cost of maintenance, and a lot of app models don't do subscriptions for app updates.
Of course, if there is a cloud component, that's a different story because there are recurring costs to hosting a server. Or maybe a user uses the service enough to justify the subscription (e.g. Apple Music subscription vs paying per song on iTunes or how Claude Code and Codex are actual subscriptions that are extremely worth it for the user).
Glad you're having a good experience, but I personally switched from Mise back to Brew. I don't know if it was just my skill issue, but there were too many packages which found Mise to be problematic.
Because with so many metals in high entropy alloys, you can tune it to whatever, and that's why it's currently being investigated for potential room temperature superconductors.
Hello Hacker News! This is more of an experiment/statements I wanted to make about needing specs for things (e.g. for agents to output) more than an actual "spec for itineraries."
While schema.org exists, it is a massive specification with a lot of cases that are likely unused if you were to optimize it for application use. This project really just points at the tension between using such an extensive schema versus more "practical" and application-focused ones, especially when token costs are in the question.