https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=tru...
The brief frontpage life of a couple of the highly upvoted ones:
Because there's absolutely zero doubt that this release matches this criteria.
Here's "SNI":
That's one reason I'm using a silly acronym: SNI! — to convey that it's a specialized use of those words. When we say things like "this is not significant new information, so we're treating this post as a dupe", or even the gentlest, most watered-down and tiptoey version of that language, there are always people who feel aggrieved on the project's behalf, as if we're putting it down or belittling the hard work of its devs. This explanation is for those readers.
It's a made up term because it's a weird, made-up local meaning, it doesn't mean 'someone who uses the project might think it's significant'. So that's why I'm linking it, because it matches this submission very well.
It may looks like dupe to you, but it definitely doesn't fit the description of dupe given in the comment you linked to.
> It's a made up term because it's a weird, made-up local meaning, it doesn't mean 'someone who uses the project might think it's significant'.
Please re-read the comment you linked to, because it indeed defines what constitute SNI in a pretty clear fashion, and by this definition the aforementioned post definitely contains SNI.
Or maybe you didn't even both reading the actual post you are commenting, and because of that you fail to see how a “Bevy 0.14” post could contain SNI.
Now that I'm thinking about it, it's the most likely answer because I don't see how someone who's read the post could claim in good faith that it doesn't fit the description of SNI. Even just the implementation of Unreal Nanite in Bevy by itself is well beyond this bar, and it's only a fraction of the diff that the post is talking about.