Elon Musk just created ~5,000 new millionaires, current and former $SPCX employees. Of those ~5,000 people, roughly 400 of them will see stakes worth $100 million.

Bitcoin is even more vulnerable to inflation bugs than Zcash! 🤯 Every custodian and exchange is a "shielded pool" which can, and often does, print fake Bitcoin at will. You deposit and then can't withdraw, because someone else withdrew your actual Bitcoin. Even worse, the vulnerability has been in the codebase since 2010! And still hasn't been patched! 😱 The exploit is the block size limit, and is a terminal problem facing Bitcoin. That's why the price is dumping right now: Saylor and others have been exploiting the inflation bug. Because of the block size limit, paper Bitcoin is a profitable possibility. Btitcoin's supply will never be constrained to 21 million.

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?

I don't know why this week became the tipping point, but nearly every software engineer I've talked to is experiencing some degree of mental health crisis.

Turning non-deterministic, hallucinating LLMs, as the basis of so-called agentic browser AI, *on by default* without explicit user consent, is against Brave's user-first principles. It may be that we are alone in taking this position on principle. Re: theverge.com/tech/845216/moz…,

You split your monolith into 47 microservices. Now you have: - 47 deployment pipelines to maintain - 47 different ways to handle logging - Distributed tracing you don't understand - Network calls that used to be function calls - A debugging nightmare when anything breaks Your "scalability problem"? It was a single slow SQL query. You spent 6 months building a distributed system to avoid adding an index. This is what happens when architects read Medium articles instead of profiling code.