eaurouge

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?

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).

> 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 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?

I read the article you referenced. It's based on, and described wrt, Python's `async with` (so quite a few layers of abstraction), so I can't say with certainty how it's implemented. But, as I noted earlier, it isn't really that different from a run-till-completion task scheduler and is not particularly novel or interesting, imo.

So this is why 30/40 yo track athletes look older than their age mates? Right.

> The people who pay into this are either taken in by the pretense that they’re sponsoring open-source work

> Honestly, I think the first category is somewhere between "microscopic" and "nonexistent", but most people in the second category will end up holding the bag when this thing inevitably collapses.

I agree. There may be folks willing to support open-source software via a crypto-friendly vehicle, but most involved in this are hoping to make money on a pump and not get left holding the bag.

Everyone involved in this scheme is fully aware of the game being played (or should be) and the risks involved. The notion that "crypto grifters" are corrupting naive open-source developers just strikes me as an odd way to describe such activity.

If I may, who are the grifters here and who are the innocent parties? Why? Who does this harm?

So another strawman?

> It's like someone is claiming they unlocked ultimate productivity by washing dishes, in parallel with doing laundry, and cleaning their house.

But we do this routinely with machines. Not saying I don't get your point re 100 PRs a week, just that it's a strange metaphor given the similarities.