It's pretty hard to have an accidental a use after free in the FireFox CSS engine because it is mostly safe Rust. It's possible, but very unlikely.

That came to my mind as well. CSS was one of the earliest major applications of Rust in FireFox. I believe that work was when the "Fearless Concurrency" slogan was popularized.

Yup. To this day, Firefox remains the only browser with a *parallel* CSS engine. Chromium and WebKit teams have considered this and decided not to pursue since it's really easy to get concurrency wrong.

If I recall correctly, the CSS engine was originally developed for Servo and later embedded into Firefox.

Wow so cool! I think a big part of the Show HN slop are GitHub links or libraries that haven't even been read or used by their authors outside of the test suite on their local machine.

I'm sure a happy medium is shutting off links to vibe coded source code, and only letting vibed hosted applications or websites. For us who want to read code, source code that means nothing to anyone is pretty disappointing for a Show HN.

Yep, hide new accounts except to higher karma users is an easy win.

But very gatekeepy. New accounts are already highlighted and get mercilessly reported and downvoted if they post spam.

Maybe just hide them if they post GitHub links.

I've loved some of the vibe coded apps that are hosted somewhere that have made the front page, but a lot of the links to GitHub projects intended to farm stars for throwaway portfolio padding (which often don't work).

Egh. No silver bullet here.

As someone who has posted a couple of Show HNs that went to GitHub, I'd have to respectfully disagree. :) We are sharing language libraries, so GH makes the most sense. You can get the library and sample apps there.

Oh yes, I'd be very disappointed with no GH links or new code libraries, but making GH links for new users go through stricter review/more limited visibility might be a good trade off.

You still somewhat mute new users who want to share a useful/interesting GH link, but I'd hope higher karma users can help us out here.

I just have no interest in seeing code that hasn't even been read by the author. At that point, just show us what it does, don't show us the GitHub link.

On the front page, someone made a cool isometric NYC map via vibe coding - another front pager was someone who also claimed to make an ultra fast PDF parser that failed on very common PDFs and gamed the speed metric by (useless) out of order parsing.

Guess which one I installed and spent more time using? These vibe coded projects aren't interesting for their code and almost always not intended to be used by anyone if they're libraries/frameworks, but the applications made with vibe coding are often very cool.

An easy win is turning off the firehouse of vibe coded GitHub portfolio projects and just ask for a link to a hosted application. Easy.

I much prefer 4.6. It often finds missed edge cases more often than 4.5. If I cared about token usage so much, I would use Sonnet or Haiku.

>with fewer footguns, easier to work with, easier to read and write, and easier to test.

With the exception of fewer foot guns, which Rust definitely takes the cake and Zig is up in second, I'd say Zig is in last place in all of these. This really screams that you aren't aware of C/C++ testing/tooling ecosystem.

I say this as a fan of Zig, by the way.

I mean, you're right that still so many of us can't use the language yet, but I think we can still applaud progress towards major features when it's less than stable.

Kudos Zig contributors!

>I know we instinctively want to frame this as a privacy problem

How is that not also a privacy problem?

man who has only used the american financial system: the world not singularly using the american financial system is less dynamic. surely there are no counterexamples to this.

GitHub downtime is going from once a month (unacceptable) to twice a month (what the fuck?)