Comment by m132 | Hacker News Reader

Comment by m132 | Hacker News Reader

The README mentions ARMv7-M, RISC-V, and AVR, but no actual SoCs or boards, and the source code contains unconditional inline assembly for Arm. Similarly, there are measurements of context switch time on RISC-V, while the scheduler is one big stub that doesn't even enter a task, only returns from itself using Arm-specific assembly [0]. The examples rely on this scheduler never returning, so there's no way any of them can run [1]. The bootloader is also a stub [2]. Not a single exception vector table, but plenty of LLM-style comments explaining every single line.

Others (well, two people really) have also noted the lack of a linker script, start-up code, and that the project doesn't even build.

82 points at the time of writing, which is 4 hours from the post's submission. Already on the main page. The only previous activity of the author? Two other vibe-coded projects of similar quality and a few comments with broken list formatting, suggesting that they were never even reviewed by a human prior to posting.

Does anybody read past the headline these days? Had my hopes higher for this site.

[0] https://github.com/cmc-labo/tinyos-rtos/blob/2a47496047fdb45...

[1] https://github.com/cmc-labo/tinyos-rtos/blob/2a47496047fdb45...

[2] https://github.com/cmc-labo/tinyos-rtos/blob/2a47496047fdb45...

HN these days is filled with people saying basically "Show HN: I had an LLM shit out something I wanted, I didn't read it, but you should!".

And then a bunch of green new accounts commenting on how it's cool and they learned something. It's just a never ending attack on our attention.

HN used to provide a really high signal to noise ratio for me, but it's degrading pretty quickly. There are new accounts below saying "hey I just learned what RTOS means, thanks!"

I reflexively reload HN many times per day, but I'm wondering if I need a walled garden with some sort of curation of individuals - which sucks - to get the signal level I want.

I wish HN upvote data was public, I feel like I could build some kind of improved algorithm that reduces the vote weight of people who upvote slop.

This site is very much drowning in all the slop. It's over half of posts now I think, not just the "Show HN" posts. Those are 100% slop, as are all the non-show-hn new project announcements.

All the moderators have done is drop Show HN posts by newish accounts. It fixed nothing. I have to hope they have some ambitious plan along the lines of what you suggest.

This probably isn't just an HN problem (GH's model is broken now). It's so cheap to make software that the previous process of releasing something new associated with a person is probably outdated. AI knows what sounds impressive too. So now we're drowning in software releases and attributing software to a person is meaningless.

As a rule people do not read the linked content, they come to discuss the headline.

The first indication to me this was AI was simply the 'project structure' nonsense in the README. Why AI feel this strong need to show off the project's folder structure when you're going to look at it via the repo anyway is one of life's current mysteries.

Honestly, maybe this is the problem.

A web-of-trust-like implementation of votes and flags, as suggested below, might be a solution, but I feel like it's an overkill. I've recently flagged a different clickbait submission, about Android Developer Verification, whose title suggested a significant update but that merely linked to the same old generic page about the anti-feature that was posted here months prior. Around 100 points too, before a mod stepped in, changed the title, and took it down.

Maybe the upvote button is just too easy to reach? I have a feeling that hiding it behind CSS :visited could make a massive difference.

Don't forget the 71 stars on github, and counting!

Oh wow, was 60 just a while ago. Guess the dead Internet theory is no longer just a theory.

Reply on news.ycombinator.com