Dear Future architect of some neat new technology to be someday posted on HN please do the following:
If you make anything with a UI, even a GUI stack, always include screenshots. If you make a programming language or programming framework / library, always include code samples!
Really show us nerds the bits we want to see right away, screenshots / code or even a video (fully optional, unless its some type of terminal shell or something where a video would illuminate things!) would sell it better. Many of us are working and don't yet have time to pull down everything to run it locally.
Honestly, even if its not open source, if you're selling a product, SHOW THE PRODUCT not just descriptions of the product.
So, given that this is almost brought up every single time a GUI framework/library is posted on HN, and has been for decades at this point, and given that it apparently doesn't make any difference, what's a better approach for educating the ecosystem at large about this problem? Do we need a website? Nation outreach program? Do we need a arewescreenshottingyet.com landing page with stats to keep track? How can we finally fix this constantly persisting problem of people not adding screenshots for visual things they've built?!
Two options: continue to spend the effort to teach new cohorts community expectations; or eliminate the production of new cohorts so the existing lessons eventually saturate the population.
The second approach may have side effects.