People will say that there is no reason to use Opus, unless you have too much money lying around. But I got to disagree. The gap between Sonnet and Opus is HUGE!
I personally use Opus only when I encounter issues that I and other "regular" model scan not fix. Most of the time these are infrastructure or build-step issues, not really application related. For example:
My local test pipeline for Coco started failing recently. The issue was an import that could not be resolved. I started debugging it manually and could not spot any issues. After 30 minutes I let Sonnet, Composer, Gemini and GPT at it. All of them took AGES (30 minutes +) and came to the conclusion that there must be a bug in Bun's package resolution logic. I knew this was not the case as the Github CI was still running fine.
Opus took 3 minutes to find a broken symlink that pointed to a newer version of the package that removed that particular export. But at the same time this single request cost about 5% of my regular monthly AI spending :D
Can we talk about how super smart Fabric is about component trees?
These are two different screens with their own component trees. But Fabric understands that the MintSelector component does not need to change and simply moves its position in the tree, keeping the same reference.
React Native has come such a long way π₯
I think this is exactly how many will feel in the future. Just like nostr, Cashu provides super easy to comprehend rails for building apps and services. People will fall in love with the product someone is offering without even realising they are using Cashu. ππ₯
View quoted note β
This isnβt a dip. Itβs whales messing with the market specifically so you look dumb at Thanksgiving. The bull run resumes right after, I swear. π€
I guess pure irony is when you try to fix your services by reconfiguring routing around your cloudflare dns, but can not log in because the hosters captcha is powered by cloudflare...
Another day and TWO new coco release candidates:
RC23 and RC24 tackle some issues with handling the novel keyset v2 format. Now applications built with coco should have no issues once keyset v2 rolls out. π₯
Cashu-ts v3.1 and v2.8 have been released!
These releases include new features and improvements with some backports to major version 2 for users that have not made the jump to v3 yet.
- Support for arbitrary tags in P2PK secrets
- Support for P2BK (v3 only)
- getTokenMetadata for an easy peek into an encoded token
- Improved CBOR handling and guardrails
- Lots of amazing DX and CI improvements
https://www.npmjs.com/package/@cashu/cashu-ts/v/3.1.0https://www.npmjs.com/package/@cashu/cashu-ts/v/2.8.0
I have been an Adobe Scan maxi in the past. Ever since I value my own privacy more I obviously stepped away from Adobe to keep my documents save. Ever since I was lost in paper chaos.
Today I discovered paperless-ngx and its a complete game changer. I setup some easy workflows that scan and email documents quickly. Paperless will automatically process them and use OCR to index them. π€―
Man I gotta say, Expo is really killing it. Upgraded the new eNuts to the latest SDK version (lots and lots of new stuff). Single command, 2-3 minutes solving peerDep issues. After that triggered a new build, went through without any issues. App is working fine.
This is peak DX and I don't think I would be building React Native projects without it.