Not hard. I have such a thing as just a few lines of quickly put together python code, using pyserial, dockerized. Has run for an entire year w/o issue. ASCII and Unicode.
It replaced a very unreliable, problematic setup somebody else had set up in the past, which was based on an android phone.
Once I got the sim900-derived device from aliexpress, I moved the sim over and had it working in less than an hour. Polished the code and its setup during the first few days of use, and hadn't had to touch it since.
As someone that worked for the spin out from GS, then got acquired by TR, then sold off to Blackstone, I wonder how much of our tech debt is still there for you to deal with 10 years later. :)
I haven't been at TR in 10+ years as well. AT TR, I mostly dealt with Eikon's pipeline for estimates, actuals and the like (IBES data) ingestion, querying and analytics. So can't say much, though some of my old colleagues still seem to be there.
Slashdot/Reddit/Facebook etc all build communities, when they get too large they splinter until they become increasingly specific. You've done the opposite. I think you are going to need to group common products, then gradually break it out. ie, food -> deserts -> cakes -> chocolate cake -> chocolate cake from <shop> etc
That's how I pictured it, users scan all the bar codes they have access to and it builds similarity profiles.
I pictured scanning all my CS books for example, and I'd probably end up in a group with everyone from my class at school who did the same, for example.
As you said, I tried to keep the room name general so it wouldn't be too scattered when the barcode is scanned. So, if someone scanned for a cake, it currently deletes the chocolate cake and brings up that cake brand, but later, users will be able to create a room for chocolate cake with the same barcode if they wish.
> Literally everyone does this. OpenAI is doing this with Codex, far more than Anthropic is.
And yet, OpenAI have publicly said they welcome OpenCode users to use their subscription package. So how are they being anti-competitive "far more" than Anthropic?
You've still not explained why, you've just reasserted "because they said so".
What is the upside to Anthropic if we use ClaudeCode but not OpenCode? If it is such a loss leader, why would they even offer it? By using it, even within their terms, you are still abusing their good will. No?
(You also said the alternative to not liking the terms is to use their API. There is another alternative, which is to keep using it against their ToS and risk a ban. Or use a different provider. So the situation is more nuanced than "this" or "that")
Yes. That is all that matters. That is the contract you've signed with the business, end of story.
They have their reasons (3P clients suck at caching, this is a subsidized tier to create subscription lock in, etc) but that's besides the point. If you sign a contract, you abide by its restrictions or you categorically abusing the offering.
> There is another alternative, which is to keep using it against their ToS and risk a ban.
No one working on a project of value and no sane business would do this. The people doing this are not serious/mature people.
Frankly any dev that intentionally does this at a real company would be fired.
Ah, but the ToS I agreed to didn't state it.. they even admitted it wasn't clear and then unilaterally revised it.
And yes, I agree businesses must abide by the ToS, it would be too much of a business risk not to.. but individual users, using for their own purpose can make their own choice.
An individual choosing to not abide by their unfair ToS is perfectly reasonable and doesn't make them unserious or immature people, and it's pretty weak to make it an ad hominem attack.
But if you think their reasoning is solely that opencode has poor caching, then the solution is to make it chew through the quota quicker (which i think it already does), or provide guidance on how to do it better. The arms race of trying to block it will be a war they will eventually lose.
If Claude code can have great performance by optimised caching and Opencode doesn't.. I'll run out of quota using a third party client and have a terrible experience, and the choose to use Claude code instead because wit is superior.
Consider this: you are Anthropic. There are some Claude Code used cases that will have poor caching performance. Let's say these are 10% of your use cases.
You explicitly don't count cache misses right now because it would make the UX poor for these use cases. It's no big deal since the remaining 90% of use cases can subsidize the 10%.
Now open source clients become a thing. Instead of 10% of usage having poor caching, it grows to 50%. You can no longer subsidize those users because the economics don't work.
You have to start counting cache misses and the UX goes to shit for everyone.
reply