Tauri – Electron alternative written in Rust - https://news.ycombinator.com/item?id=29807022 - Jan 2022 (419 comments)
(The cutoff for dupes is a year or so: https://news.ycombinator.com/newsfaq.html)
(The cutoff for dupes is a year or so: https://news.ycombinator.com/newsfaq.html)
I wrote a longer explanation about this if anyone wants more: https://news.ycombinator.com/item?id=23071428
The SNI here is that Tauri has hit stable, an information that does change how a lot of people would approach it.
I might need an even longer explanation, though, because I don't get it still. There are projects like Blender which were allowed to the front page like 5+ times in the past year, exclusively with posts about new releases. The discussions always hit the same notes. Why is that any different?
Sorry Dang - I would have to point to you that YC companies term their releases as 'launch day' or 'launch week' with YC W/Sxx badge in the title get preferential treatment and are allowed to be discussed multiple times over year - why is that ? I dont want to name names here.
Launch HNs do get special treatment in that we place them on HN's front page. This is one of three things that HN gives back to YC in exchange for funding it—those things are all clearly listed at https://news.ycombinator.com/newsfaq.html#yc.
Btw, don't be sorry! We want everyone to know how this stuff works, and we want it to be clear what the principles are (and that there are principles). Other than the three things I just mentioned, YC startups don't get preferential treatment on HN. They have to struggle for attention just like everyone else, and with the exception of a few community darlings, they find it just as tough going as everyone else, and aren't particularly happy about it.
* although I think I'm going to make an exception next week for a startup that did the very first Launch HN 5 years ago and is still kicking.
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...
The problem with changing that policy is that the front page would see a massive influx of "Foo 1.2.3 release" stories. This would not be a step in the direction of the global optimum (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...).
From an HN perspective the important thing is not the version number, nor even the significance of the release, but how recently the project last had a major discussion.
There's one workaround for this that might work sometimes: if software has undergone major recent work that is interesting in its own right, then an article devoted to the specifics of that particular project—the why and the how, with interesting technical details, and an explanation of that makes it hard and also what pain it solves / what makes it worth doing—might have a chance of generating a more specific discussion in the comments. That's what I would do if I had a big release that I hoped to get attention for on HN.
Even then, people are likely to mostly post generically about the project—just as announcements of new things from $BigCo tend to attract lots of generic discussion about $BigCo too. But if there aren't too many of those, we can downweight them and then the more specific comments can hopefully float to the top.
The linked URL nor the video has not been posted before.
I'm just pointing this out as many projects seem to post their 1.3.2 Beta 1 blog posts and that seems to be ok -- or at least I see them pretty often.
That is, it's not primarily about the diff between announcement N and announcement N+1. It's about the diff between HN thread N and thread N+1. Comments in these threads are almost invariably generically about the project as a whole. You can see that with e.g. https://news.ycombinator.com/item?id=31764384 in the current thread - which is a fine comment in its own right. There's nothing wrong with these threads! The only problem is that we have to regulate how much repetition of them there is.