Hacker News (Front Page) (RSS/Atom feed)'s avatar
Hacker News (Front Page) (RSS/Atom feed)
npub13zym...3p44
RSS/Atom feed of Hacker News (Front Page) More feeds can be found in my following list
Show HN: Command Center, the AI coding env for people who care about quality Hi HN! We’re Jimmy and Ray. Jimmy is a Thiel Fellow with a Ph. D. from MIT who has worked on programming tools for 15 years; Ray became VP of Sales at a $2B company when he was 19 and has built side-businesses vibe-coding. Last year, we set to answer the question “If AI can write code 100x faster, then why aren’t you shipping 100x faster?” What we learned shocked us — even fairly nontechnical people and solo founders told us they were spending more than half of their development time reading the AI-written code. And much of the rest of the time was spent either de-slop-ping it, or wishing they had done so. As luck turns out, our last two products were a tool that quickly onboards people to large codebases ( [https://x.com/0xjimmyk/status/1873357324229984677][1] ) and trainings that taught deep concepts of code quality to CEOs, YC founders, and engineers at top companies ( mirdin.com ), so we were extremely well-positioned to solve these problems. Command Center is an agentic coding environment focused on quality. With a few keypresses, you can start building 3 features at once and soon have 3 diffs ready, each consisting of 2000 changed lines across 50 files…. This is normally the point where you think “Crap, what now?” With Command Center, at this point you simply click “Refactor,” and watch the vibed slop turn into readable robustness. Then you click “Generate Walkthrough,” and then suddenly, to read a 2000 line diff, instead of scrolling up and down trying to make sense of it, you just press the right arrow key 200 times. See something you don’t like? Click on line 37, type “Do this and all other network fetches in the background Cmd+Enter,” and you have a few more agents getting your code into final shape. Click or type “Commit,” “Push,” “Create PR” — you just shipped a high quality, non-slop feature We’re striving to be the best at every step of the pipeline, but can just try Command Center in pieces wherever you feel your current workflow is weakest. We have users who do all their coding in Zed or the Codex app, and then jump over to Command Center for a walkthrough when it finishes running. There’s even a skill that will pop open a Command Center walkthrough from the environment of your choice. Or you can just keep Command Center running while you do your work elsewhere, and if your AI deletes anything, you have Command Center’s snapshots to the rescue. We launched quietly last year and have been refining since. The quality and usability have kept going up, and Command Center is now ready for a lot more attention. Since our quiet launch, we’ve seen at least a dozen other agentic coding environments appear….approximately all of which have the same feature set focused on the part which is already easy (generating the first version of the code) and with at best a shoddy answer to the hard part (everything that comes after). Command Center’s focus is making the hard parts easy. Here’s what our users have to say: “[The refactorings] give your LLM taste. I’ve never seen an LLM write code this good before.” — Doug Slater, Staff Engineer, Climavision “With Command Center walkthroughs, I can get through a 400-line diff in less than half the time.” — Prateek Kumar, Platfor Engineer, Sumo Logic This product is not for everyone. If you’re someone who preaches “the prompt is the source, the code is the compiler output,” then you probably won’t enjoy Command Center. But if you want to uphold traditional engineering discipline while also shipping 20 PRs a day, then this is the environment for you. Comments URL: [https://news.ycombinator.com/item?id=48453002][2] Points: 28 # Comments: 7 [1]: [2]:
Show HN: Mach – A compiled systems language looking for contributions Hi HN, I'm the creator of Mach ([https://github.com/octalide/mach][1] or [https://machlang.org][2]). Two days ago, we finally achieved full self hosting. I wanted to make a post here to show off the language since this is a big milestone for us. ## TL;DR about the language for those curious: - There are no external dependencies anywhere in the pipeline. This includes LLVM, libc bindings, or anything of the sort (save for the historical bootstrap compiler, which requires any C compiler and has been phased out completely). - Mach is extremely opinionated and very anti-magic. WYSIWYG is a core principal for the language. There are no hidden behaviors, implicit type conversions, or "automatic features". Simplicity and stripping away ambiguity are core principals that this language upholds. - Performance currently lags behind C by about a factor of only 4x at the time of writing, almost entirely due to the lack of deep compiler optimizations like autovectorization, which have not been fully implemented yet. Eventually, Mach will be at least on par with C. ## Why did I build this? I love low level systems languages like C, Zig, Go, and (sometimes) Rust, but I wanted something that actively discourages "cleverness" in favor of long-term maintainability and overall clarity. Mach is highly opinionated and explicitly demands verbosity in ways that other languages are afraid to. Computers aren't magic, and code you write should not pretend they are. This project initially started out as a learning opportunity for myself, but grew into a fully featured language as time went on. There is still a lot I have to learn, however, and I'm excited to be able to do so as this project continues to grow into the future. ## Why do I (the reader) care? If you like C, you'll probably like Mach. Mach takes heavy inspiration from the "vibe" of writing C, but improves on much of the syntax, lacks quite a few footguns, "unhides" a lot of internal mechanisms, and has a FAR better dependency management system. If you want to play around with a language that is fully capable of replacing C, and especially if you would like to contribute to its development, then PLEASE stop by and mess around. ## Where should I go to check it out? The github repository has a link to our discord if you'd like to chat with myself or our few other regular users. My personal account has all of the tooling that exists as well as a few example repos if you feel inclined to try it out. ## Will this project by dead in X months? I've been working on this in the background for over 2 years now. This is a long term project that I plan to maintain into the indefinite future, with or without a userbase. If you like the language at all, I highly encourage you to get involved in its development because it WILL be sticking around in some capacity forever. I know this was a bit "rambly", but let me just say that it's been a great joy to work on this project and I would love any and ALL opinions and contributions, ESPECIALLY if you hate the language or find a problem that needs fixing. Let me know what you guys think! Comments URL: [https://news.ycombinator.com/item?id=48453666][3] Points: 4 # Comments: 0 [1]: [2]: [3]: https://news.ycombinator.com/item?id=48453666
Show HN: HTTP/3 and raw QUIC client/server APIs for Node.js I built this because I wanted to make outbound and accept inbound HTTP/3 and raw QUIC connections from ordinary Node.js code, without building Node from source or putting everything behind a reverse proxy. Repo: [https://github.com/currentspace/http3][1] npm: [https://www.npmjs.com/package/@currentspace/http3][2] It’s a native package around Rust/quiche. It supports both client and server APIs, I'm using it in a couple of projects: creating raw QUIC streams, datagrams, custom ALPN, session behavior, and HTTP/3 client work from Node. I've tried to be very safe in the native code, written in rust, with proofs around the parts I was most concerned about getting wrong. I have it hosting a couple of sites as HTTP3 endpoints and found it working well. Comments URL: [https://news.ycombinator.com/item?id=48449498][3] Points: 3 # Comments: 0 [1]: [2]: https://www.npmjs.com/package/@currentspace/http3 [3]: https://news.ycombinator.com/item?id=48449498
Show HN: Gitdot – a better GitHub. Open-source, anti-AI, and written in Rust What works now: user signups, org creations, private/public repos, and importing GitHub repositories (both as read-only mirrors and full migrations). So basically, you can create, push and pull to a repo, but we don't have many features quite yet (issues, PRs, CI). What is a bit unique is: 1) we built it in Rust and 2) the website is a little odd. Its design is inspired by CLIs (e.g., fzf, broot, vim) instead of web apps, and as such, lacks some affordances that you might typically expect in favor of keyboard-driven instant navigations (we have the very ambitious goal of an FCP of 100ms). In case you're curious, here's how we we built it: [https://gitdot.io/designs][1] We recognize that we're making some bold claims here and are also well aware that we have much to learn. Building software is still hard, and that's a fact we seem to relearn everyday. But we wanted to share what we built so far nonetheless. Cheers, thank y'all for reading, and till the next —paul & mikkel. Comments URL: [https://news.ycombinator.com/item?id=48447806][2] Points: 10 # Comments: 6 [1]: [2]: https://news.ycombinator.com/item?id=48447806
Ask HN: How to escalate a rejected Google extension? I submit an extension (an adblocker) to Google Chrome's web store. Google keeps rejecting it for dubious reasons. The first rejection was claim it was "spam". When I appealed, the review came back that it contained "additional functionality" because it uses "modifies network traffic". Well of course it does! When I asked the reviewer how I could achieve the stated functionality of blocking ads without the use of "declarativeNetRequest" I simply received the same canned response. I submit a totally new update that simplified the code and included comments, and references to other open source projecs that use the exact same mechanisms. Again it was rejected. On this appeal I asked if it could be escalated to a senior reviewer who could possibly reply with more context. Same canned response and rejection. I can't help but think Google has some internal policy to give adblockers a runaround. It is obvious to me the stated rejections are not valid (Note that I'm also not new to this - I have several extensions that have been published for years with thousands of users) but have never encountered such gate-keeping before. It's a sad state of affairs even if not totally unpredictable. To be honest I'm surprised Google hasn't made it an official policy to prohibit adblockers. But they haven't - obviously there are other adblockers published to the store, and that's what makes this so frustrating. Anyway, fellow developers. Anyone run into a similar situation? And how did you resolve it? Thanks! Comments URL: [https://news.ycombinator.com/item?id=48447980][1] Points: 7 # Comments: 0 [1]:
Ask HN: Why hasn't there been a real competitor to Ticketmaster yet? It feels like every event/venue is selling tickets exclusively through Ticketmaster. Every other ticketing platform seems to only hold resale tickets in their inventory which just transfers the tickets to your Ticketmaster account when bought. With all the hate Ticketmaster has gotten and all the other ticketing platforms out there, I'm surprised Ticketmaster still has a hold of pretty much the entire market. How are they doing this? Why haven't the other platforms been able to compete? Comments URL: [https://news.ycombinator.com/item?id=48448313][1] Points: 12 # Comments: 11 [1]: