Remix.run Logo
▲ grimgrin 5 hours ago

4y5k, have some self-respect. you could have cooked on this for a little bit longer than: yesterday. there is one commit! this is ... quite possibly, but I'm unsure, the first "show hn" with a single commit, lol

▲grimgrin a few seconds ago | parent | next [-]

update: idk how I have positive points on my comment above

I wouldn’t make one like it again. simply because I really have no clue how long the author thought about their project

hell, another front page Show HN has a single commit

▲indigodaddy 5 hours ago | parent | prev | next [-]

Why does it matter. It's pretty normal to do a bunch of dev locally and then at some point create a public gh repo and then push

▲verdverm 5 hours ago | parent [-]

you can do that with full git history, the first commit is "upload files" or something like that, which I assume is via the UI because that is def not dev speak

▲swaptr 22 minutes ago | parent [-]

Not necessarily. Plenty of devs (me included) clean up or reinit git history before a first release or going public. I understand it’s now read as an AI slop signal, but that’s no reason to dismiss their work.

▲arcanemachiner 4 hours ago | parent | prev | next [-]

Devil's advocate, it could have been a bunch of squashed commits. I've done that when open-sourcing stuff from work, after making sure the code didn't have any stray references to work-related items.

▲verdverm 5 hours ago | parent | prev | next [-]

back at peak Slop HN, there were a ton of these, the fastest I recall was a few minutes from first commit time to Slop HN time

example: https://news.ycombinator.com/item?id=47492202

I recall sub-10m, but don't care to search has any harder

▲4yk5 2 hours ago | parent | prev [-]

[dead]