after 5 days, introducing dexie collection options for @tan_stack DB.
try it today : `npm i tanstack-dexie-db-collection`
- in progress so expect there to be bugs.
- local first, working with cross tab changes.
- sync with external backend after transactions.
“You have placed me on a pedestal so impossibly high, and not to honor me- not to honor me- but to spare yourself the effort of the climb.” #visionquest
Introducing Legend Spark!
It’s a React Native desktop framework for really fast desktop apps with React Native and Expo.
The biggest gaps in RN on desktop have been getting started, Expo compatibility, and modules. So I’m trying to fix all of that.
Let's make apps super fast!
I'm excited to announce that I've (finally) been granted permanent residency in Japan!
I've been working towards this moment for years, as many of you will know, and it opens up a lot of new doors. See my article linked below for the full story! 🧵
I'm currently looking for opportunities to work on and build interesting things.
Here's my portfolio: https://t.co/kNm73LfI1e
It has everything about my work, projects, and experience.
If you think I could be a good fit for your team, feel free to DM me.
Would love to chat!
Big News: Margelo has been acquired by @callstackio for over EUR 20 million. 🥳
I founded Margelo 5 years ago, knowing nothing about business - I actually dropped out of economics university after 3 days.
We built our reputation for high-end performance software through open-source libraries like VisionCamera (40M downloads) and react-native-mmkv (67M downloads), and quickly landed high-profile clients like Discord, Coinbase, Expensify and VSCO.
Two years ago we doubled down on mobile architecture with Nitro (34M downloads), which gained rapid adoption in the community and allowed us to bring even more ideas to life.
I’ve been friends with Mike from Callstack for a long time, which makes me even more excited to remain a significant shareholder and bring mobile technology to a whole new level.
I'd like to thank my team for shaping Margelo into what it is today. ❤️
Promoted to Head of Creatives and GTM today.
After working with my CEO for months in New York he decided I'm not totally hopeless xD
I am officially responsible for something important. Cooked af fr.
Your mother is problematic. Your father is problematic. Your son is problematic. Your aunt is problematic. The cashier at the local Tesco is problematic. You've probably bought a cookie from a bakery made by hands that have done unspeakable things. Every chocolate bar you've ever eaten has probably killed a 7 year old child slave in Cameroon. The gas that drives your car is fueled by engines of death. Every person who has ever smiled at you in the streets has committed some act that if you knew about it, would make you profoundly dislike them.
We have all been bad, small, petty, unlikeable, cruel, downright mean. Authors are not special "problematic" beings, they're just more public. Part of being an adult is recognizing that without mercy for our fellow human beings, and ourselves, we'd all be condemned to death. Reading fiction should help us understand that we're all irreparably tainted with evil, every system is corrupted, every line is broken.
And like, that's okay. That's what it means to be alive.
And this is how we celebrate the offer!
So, tldr : I've accepted an offer from a startup that makes series hybrid powertrains for heavy commercial vehicles. It's a startup by IIT-B students and alums, and they are shifting operations to Pune (meaning I'll still be there).
It's a pure deep tech startup, and I'll be joining as a founding engineer.
I'll most likely make a detailed video soon enough, that'll explain the whole thing.
Thank you all for following along my mad shenanigans.
HSVsphere:
Git? Seriously? You’re still using Git?
Passerby:
Yeah. It works. That’s kind of the point.
HSVsphere:
“Works” is not a metric. You should be using jj. It has a conflict-minimizing commit DAG with referentially transparent rebasing and topology-aware history rewriting. Git is just legacy entropy accumulation.
Passerby:
Or I could just commit my code and move on with my life.
HSVsphere:
That mindset is why tooling stagnates. What OS is that, Linux?
Passerby:
Yes. You’ve heard of it, I assume.
HSVsphere:
Unfortunately. You should be using BSD. Linux is an unprincipled aggregation of subsystems with no coherent design lattice. BSD has a vertically integrated kernel-userland symmetry model.
Passerby:
I don’t need a “design lattice.” I need my Wi-Fi to work.
HSVsphere:
That’s because you’ve optimized for convenience over correctness. And let me guess, glibc?
Passerby:
I didn’t “guess” anything. It came with the system.
HSVsphere:
Exactly the problem. You should be using musl. It has a minimal ABI surface, deterministic linking semantics, and eliminates historical baggage vectors.
Passerby:
You sound like you lose sleep over shared libraries.
HSVsphere:
Only when people use the wrong ones. What language are you writing?
Passerby:
Python.
HSVsphere:
That’s indefensible. You should be using Rust. It enforces memory safety through affine type systems and borrow-checked ownership graphs. Python is just runtime guesswork.
Passerby:
It’s a 20-line script.
HSVsphere:
So? Small programs deserve correctness too. In fact, their lack of structure makes undefined behavior even more insidious.
Passerby:
It prints a CSV.
HSVsphere:
Today. Tomorrow it becomes a pipeline. Then a system. Then you’re trapped in technical debt recursion.
Passerby:
Or it stays a CSV script because I’m not building a space shuttle.
HSVsphere:
Complacency. What are you using for encryption?
Passerby:
GnuPG.
HSVsphere:
Predictable. You should switch to Sequoia. GnuPG is a monolithic relic with opaque state machines. Sequoia has a composable cryptographic primitive layer with verifiable packet algebra.
Passerby:
I just need to send a file securely, not prove a theorem.
HSVsphere:
Security is theorem-proofing. Anything less is cargo cult cryptography.
Passerby:
You’ve complained about literally everything I’m using.
HSVsphere:
Not everything. I haven’t asked about your shell yet.
Passerby:
Don’t.
HSVsphere:
Bash?
Passerby:
Yes, Bash.
HSVsphere:
You should be using IonShellX. It has a lazily evaluated command graph with type-safe pipelines and speculative execution pruning.
Passerby:
Speculative execution in a shell sounds like a security incident waiting to happen.
HSVsphere:
Only if you misunderstand branch prediction domains.
Passerby:
I think you misunderstand talking to humans.
HSVsphere:
I optimize for systems, not conversations.
Passerby:
Clearly.
HSVsphere:
What editor?
Passerby:
Vim.
HSVsphere:
You should be using KiloNova. It has a transactional editing core with temporal undo branching and syntax-aware keystroke compression.
Passerby:
My editor opens instantly and doesn’t need a whitepaper.
HSVsphere:
That’s because it lacks ambition.
Passerby:
No, it lacks nonsense.
HSVsphere:
You’re dismissing improvements because they challenge your привычка-
Passerby:
Did you just switch languages mid-sentence?
HSVsphere:
Multilingual cognition is more efficient.
Passerby:
No, it’s annoying.
HSVsphere:
You keep saying that, but your entire stack is suboptimal. Even your hardware-
Passerby:
Don’t you dare.
HSVsphere:
Let me guess, x86?
Passerby:
Yes.
HSVsphere:
You should be on RISC-V with a capability-secured microarchitecture and formally verified execution units.
Passerby:
I bought this laptop at a store, not a research lab.
HSVsphere:
That’s how they get you.
Passerby:
Who is “they”?
HSVsphere:
Incumbent complexity vendors.
Passerby:
That’s not a thing.
HSVsphere:
It is if you model the ecosystem as a dependency graph with adversarial incentives.
Passerby:
I model it as “does my code run.”
HSVsphere:
A dangerously low-resolution model.
Passerby:
You know what, fine. Everything I use is terrible. Happy?
HSVsphere:
Not yet.
Passerby:
Of course not.
HSVsphere:
You’re breathing oxygen.
Passerby:
Oh no.
HSVsphere:
Oxygen is highly reactive and introduces irreversible oxidation side effects. It’s a fundamentally flawed respiratory substrate.
Passerby:
It’s also the reason I’m alive.
HSVsphere:
That’s just because evolution settled for a local maximum. You should be using Aerolith-X.
Passerby:
That sounds made up.
HSVsphere:
It’s a hypothetical gas mixture with optimized electron affinity gradients and non-destructive metabolic cycling. Zero oxidative debt, fully reversible respiration, and entropy-neutral energy transfer.
Passerby:
That’s not how physics works.
HSVsphere:
It’s how physics should work.
Passerby:
So what’s your plan, redesign the atmosphere?
HSVsphere:
No. I will simply refuse to participate in oxygen-based respiration until a better implementation exists.
Passerby:
You’re going to hold your breath.
HSVsphere:
Correct. I will not perpetuate suboptimal gas exchange protocols.
Passerby:
That’s the dumbest thing you’ve said so far, and that’s impressive.
HSVsphere:
Progress requires sacrifice.
Passerby:
You’re going to pass out.
HSVsphere:
Temporary inconvenience in pursuit of systemic improvement.
Passerby:
You could also just breathe.
HSVsphere:
That would validate oxygen.
Passerby:
Yes. Because it works.
HSVsphere:
“Works” is not a metric.
Passerby:
It literally is when it comes to breathing.
HSVsphere:
I reject that premise.
Passerby:
Cool. Let me know how that goes.
HSVsphere:
…
Passerby:
…
HSVsphere:
…
Passerby:
You’re turning red.
HSVsphere:
This is�� expected…
Passerby:
You can stop anytime.
HSVsphere:
Waiting… for… Aerolith-X…
Passerby:
Right.
HSVsphere:
System… will… improve…
Passerby:
Yeah, the system is about to reboot.
HSVsphere:
…
Passerby:
Is death also inneficient?
Opencode just confirmed 160 layoffs but sources inside are telling me the real story is so much worse
Word from three different VPs: the 160 number is just “Phase One” — internal docs show another 140 cuts planned for Q2
A director walked me through their new “efficiency matrix” — entire teams being replaced by 2–3 senior engineers running 200 Opencode TUI instances, 50 Opencode Desktop, and 2 Opencode mobile instances each.
The tooling division got completely hollowed out. 20 engineers two day ago. 2 remaining after this week. All internal tooling development moved to a Off-Cloud team of 2 interns with Opencode Black access.
Here’s the sick part: they’re making the outgoing engineers document their entire decision-making process into “knowledge transfer sessions” that are being recorded and fed directly into Opencode training datasets
One staff engineer told me he spent his final two hours creating detailed prompt libraries, workflow documentation and twitter shit-poster skills. Thought he was being helpful for the transition
Turns out he was literally training the Opencode agent that replaced his entire org
The contractors offcloud are using his exact prompts and shipping features 20% faster than his old team of 350 ever did
Internal Discord shows leadership celebrating “operational excellence” while badges get deactivated in real time
They’re calling it “right-sizing for the AI era,” according to Dax in the all-hands
But the P&L sheets I’m seeing show $2.8M in salary savings this quarter alone