These would be great for many places that have storage restrictions on e-bikes, but not normal bikes. So you can easily detach and bring with you before storing it.
Building an unified admin platform[0] for Source game servers & the alikes. I grew up playing Source games and ran a few, but there were always gaps between all the various OSS plugins you install and were quite fragmented, and never designed to work well with each other.
Senior software engineer with 5+ years of experience building large-scale distributed systems, CDN/edge infrastructure, and developer-facing platforms. Currently at Disney working on the DTC media platform powering ESPN, Disney+, and Hulu - designing intent-based CDN policy controls (with Z3 formal verification), optimizing multi-CDN traffic mix, and integrating with Akamai, Fastly, and CloudFront for live events. Previously a founding engineer at a YC-backed messaging startup (Texts) and ran my own infrastructure-heavy SaaS for several years. Comfortable across the stack but happiest deep in backend/infra work - distributed systems, networking, performance, and tooling that makes other engineers faster. Currently pursuing an M.S. in CS at Georgia Tech (Computing Systems, 4.0).
They could at least become faster and more reliable. There are still too many situations when Claude is running in circles and not noticing its own mistake.
After getting burned so many times on libraries, frameworks, services and platforms, even entire languages - one learns to be wary of critical dependencies. Every new project offers convenience in exchange for you giving up control of part of the software stack, and the power dynamic is often exploited sooner or later as revenue source. You can't trust anything that becomes irreplaceable, or that you can't write it (or at least understand it) yourself.
I mostly agree. But without argument, I can point out that a modern webapp requires tooling for capabilities like testing, linting, formatting, and bundling. Vite (and its ecosystem) has proven its mettle, and when it comes to being able to understand your dependencies, I'll take fewer, and simpler, and way faster, and more coherent, and more independent of misaligned corporate influence, every time. It's not even a trade-off, it's just better. I have deep expertise in wrangling eslint plugins and prettier configs and webpack, and am so grateful that's all in the rear-view mirror. An astonishing percentage of the world's most popular websites are built on a fragile and nearly-incomprehensible stack which no sane developer would choose. VoidZero (and TanStack, FWIW) are a breath of fresh air in making it possible to reason about your frontend tooling and architecture, and stepping away from unnecessary complexity and/or vendor lock-in. Of course it will eventually change. But as someone who's been building and improving web-based experiences for a living since the late 90's (for tiny startups and F500 enterprises and everything between), this is as good as it's ever been, and I recommend it without reservation.
VoidZero's business model is in Void, their deployment platform. Open source projects will always stay open source. This was announced at the very beginning.
Yes, nothing different from any other VC dev tool startup. When the community fractures people simply move on to something else. See rome -> biome for a very recent example.
