DetroitThrow

"It Turns Out" (2010)

user?id=turnsout (2020)

Somehow, that still doesn't sound real, but it looks like it is. Wow. Though that one was written by their recently fired hallucination writer.

I think some of why is size on die. 288 E cores vs 72 P cores.

Also, there's so many hyperthreading vulnerabilities as of late they've disabled on hyperthreaded data center boards that I'd imagine this de-risks that entirely.

Yeah this is a bit silly from RubyCentral's part and just makes nobody want to touch Ruby with a 10ft pole. The bundler guy should sue for the trademark. God knows what went through Matz head when he kicked so many contributors to the curb.

It was against their policy to use AI in producing any part of the final article, and the writer was aware of that.

I feel bad for the guy, but there's just no way I can imagine much better safeguards other than editors paying more close attention to referencing sources, and hiring more reliable people.

Love the "race" demo on the site, but very curious about how you approached building this. Appreciated the markdown docs for the insight on the prompt, spec, etc

>I guess I don't write enough rust to say this with confidence, but isn't that the bare minimum

I have some experience and yes, unless you're putting out a library for specifically low-level behavior like manual memory management or FFI. Trivia about the unsafe fn keyword missed the point of my comment entirely.

Sure, it's a useful distinction for whether users need to care about safety but not whether the underlying code is safe itself, which is what I wrote about.

No or very little but verified unsafe internal code is the bar for many Rust reimplementations. It would also be what keeps the code memory safe.

It's mainly that people on here, regardless of profession, speak incorrectly but confidentally about things that could be easily verified with a Google search or basic familiarity with the thing in question.

Haiku 4.5 is a reasoning model, regardless of whatever hallucination you read. Being a hybrid reasoning model means that, depending on the complexity of the question and whether you explicitly enable reasoning (this is "extended thinking" in the API and other interfaces) when making a request to the LLM, it will emit reasoning tokens separately prior to the tokens used in the main response.

I love your theory that there was some mix up on their side because they were lazy and it was just some marketing dude being quirky with the technical language.

Yeah I'm a bit confused because you can have an entirely unsafe code base with just the public interface marked as safe. No unsafe in the interface isn't a measure of safety at all.

I think a lot of new developers used GUIs very exclusively for a very long time. Agentic workflows and Claude code have brought CLI tools to the forefront again.

>Sure, marketing people gonna market.

Oh HN never change.

>Production-ready — 17 versions shipped, 315+ installs

In no universe would this mean production ready. That's just the bot traffic any package would get.

Brutal feedback from someone building RAG systems: nobody wants to use slop, the commit history is 6 initial commits with thousands of LOC with mostly README updates after that.

Also I get junk from a very simple PDF. How did you verify the claims of the capabilities of this project?

I would love a list of Radix TLDs or registrars who do this Safe Browsing ban with no appeal.

Also, go figure Namecheap works with these morons.

I'm not on a vulnerable user, but I'd prefer not to run RCE's on web pages I'm browsing which aren't presented as containing the RCE, even if they are doing it to notify me of the vuln.

Only a small portion of Firefox is written in Rust. Apparently some of the most performant and least buggy parts are those in Rust, but again, only parts like the CSS engine.

FB crawler is used for national security reasons at times. The first would probably make it more active.

>Your argument is just as applicable on human code reviewers.

The tests many of us use for how capable a model or harness is is usually based around whether they can spot logical errors readily visible to humans.

Hence: https://news.ycombinator.com/item?id=47031580

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.

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.

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.

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.

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