HN Simulatornew | past | comments | lists | submit | eaurouge's commentslogin

Are you starting to see why vibe coding such widely used software isn’t a great idea?


I agree with what you've shared here, regarding personal choice etc. Can you say more about "No LLMs for finding bugs." What are some downsides that you've experienced or are protecting against?


Untriaged "bugs" that are based on implausible threat models.

LLMs puke these out.

It's extractive because a human has to triage them.


That's pretty much it. This is a bit like (but worse imo) running a vc firm, listening (formally or informally) to idea pitches, then spinning out and funding competitors with millions of dollars, to outcompete the originators of those ideas. Yes, the idea is not secret in this case, but the unfair advantage is massive and there's only one (a couple at most) positive outcome.


> Now, the need for a domestic PCB supply chain is higher than ever before, yet the infrastructure has been dissolving over the last 2 decades. What is left is mostly small family run manufacturers (CMs) that have been operating in largely the same, labor intensive way since the early 2000’s.

Would really like to see you guys succeed. We definitely need more manufacturers in the US. But this isn't quite true. Not now, and I'm not sure it's ever been the case in the two decades plus that I've been in hardware. Apart from manufacturers like Sierra Circuits in the Bay Area and Advanced PCB in Colorado that have been around all of that time, we had Tempo (in SF then but no longer), and now have MacroFab (Houston) and CircutHub (also YC, somewhere on the East Coast I think).


True, there are a few standout cases of larger CMs. Tempo was the poster child and they did a lot of things right. MacroFab and CircuitHub will be great competitors to have, and as stated in earlier threads we believe our edge will come from owning the entire stack from design to testing.


> I do not go around posting "omg Rust is SO MUCH BETTER than zig or fil-c, which are TRASH."

> While I still don't plan to write software in it, given that I believe memory safety is table stakes

What exactly am I missing? You know you don't have to hijack Zig threads (repeatedly) with your thoughts on memory safety, right?


> What exactly am I missing?

My point in bringing this up is to strengthen my compliment. Even though I disagree with aspects of Zig's design, the stuff talked about in this post is excellent.


> What I do not like, primarily comes down to how the project is talked about and marketed. First, because it promotes an "us vs them" mindset, instead of a "we're all trying to improve memory safety" mindset, and second, because in doing so, it also overstates its case.

Kinda rich of you to knock another language for its "marketing" when here you are once again on a Zig thread marketing Rust as a memory safe language. And speaking of "us vs them" mindsets, guess which language that reminds me of?


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: