Less Hashi, more Corp
Mitchell's gone and without the Hashi it's just another Corp who once made great tools being swallowed. Do you think IBM will be as good of a steward?
eBPF is kinda insane and nobody talks about it enough
Netflix uses it to trace flow logs across their whole fleet without tcpdump eating the CPU.
Cloudflare drops millions of malicious packets per second with XDP, before the kernel even bothers building an skb.
that's the trick btw: XDP runs at the driver layer, so you reject junk traffic before the network stack wastes a single cycle on it.
Google GKE dataplane v2 is built on Cilium/eBPF, and Google wrote about pushing it to 65,000-node clusters, which is frankly a stupid-big number.
Netflix found a noisy-neighbor disk latency bug in prod that classic tools just couldn't see, because the latency was hiding between syscall and disk.
practical tip most people miss: you don't need to write raw BPF bytecode like it's 2016.
grab bpftrace, write a one-liner, get histograms of syscall latency in 10 seconds.
and boom, you can see your prod read sizes live. no recompiles, no restarts, no downtime.
the wild part is it's basically a tiny VM running sandboxed inside the kernel and the verifier won't even let you crash the thing.
observability without the observer effect, finally.
btw, I am building pktz - https://t.co/nqmL5d7beH - eBPF-powered network traffic monitor, per process, per connection, live.
#ebpf #networking #cilium #devops #k8s #kubernetes #sre #cloud
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
By the time you are losing @mitchellh, you have to assume @github has destroyed an incredible amount of community goodwill. Setting aside the lack of vision, the uptime alone is unacceptable.
Hi. Professional C/C++ programmer here. The open-source code I can find written by Adam Back and Satoshi Nakamoto don't look remotely similar.
Back's code looks typical of academic Unix programmers who also hack their code to run on Windows.
Satoshi code was written by a professional Windows programmer who also wrote for Unix.
Stylistically, they look nothing alike. There's not enough time between 2005 when I can find the newest Adam Back and January 2009 when Satoshi published Bitcoin/0.1 to account for the change. Both are perfectly competent programmers, but stylistically, they are completely different.
The NYTimes tried to compare their English language in posts/emails. I'm compare their C/C++ language in their open-source code. The NYTimes merely points out they both use C++ as if that's another corroborating detail, when the actual code seems to disqualify Adam Back.
You both made a significant mark on our industry and made it a blast to be along for the ride as you rolled out such useful tech at just the right moments to push us further. Thank you Sir’s!
This Friday is my last day at @HashiCorp, after nearly 13 years, all starting with @mitchellh and a crazy dream. I'm thankful to all the amazing investors, employees, customers, partners, and community members who joined for the ride, it's been a blast! https://t.co/VIgxfQkUrq
What a disaster. CA has good weather and vibrant tech ecosystem, and NYC has world-class amenities. WA comparative advantage was the tax regime, and now they've eliminated that. Sane founders would rather be in SF/NYC given the marginal delta in taxes and megacorps will relocate.
From empty repo to a functional minimal standalone terminal based on libghostty in 2 hours, presenting Ghostling! ~600 lines of C and you get extremely accurate, performant, and proven terminal emulation.
https://t.co/kPJ1aPHwKi
Feature list:
- Resize with text reflow
- Full 24-bit color and 256-color palette support
- Bold, italic, and inverse text styles
- Unicode and multi-codepoint grapheme handling (no shaping or layout)
- Keyboard input with modifier support (Shift, Ctrl, Alt, Super)
- Kitty keyboard protocol support
- Mouse tracking (X10, normal, button, and any-event modes)
- Mouse reporting formats (SGR, URxvt, UTF8, X10)
- Scroll wheel support (viewport scrollback or forwarded to applications)
- Scrollbar with mouse drag-to-scroll
- Focus reporting (CSI I / CSI O)
- And more. Effectively all the terminal emulation features supported by Ghostty!
The libghostty C API is not formally released, but I built this project to prove its ready to go. 😎 https://t.co/kPJ1aPHwKi