"This change will allow us to do X in Y days when normally it would take some multiple of Y."

It sounds like what you want is a more salient list of pain points in the current development environment and exactly how the proposed new thing would address them. Additionally, you'd want to hear the new set of pain points that the new thing will impose (cue the quote about some devs knowing the value of everything and the cost of nothing).

You may also, for their benefit, direct the next kid with the cool idea towards a link that's commonly thrown around here: https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence

I'm going to pull the more direct section "What this means on Wikipedia":

> If you're considering nominating something for deletion, or changing a policy, because it doesn't appear to have any use or purpose, research its history first.

> You may find out why it was created, and perhaps understand that it still serves a purpose.

> Or if you do feel the issue it addressed is no longer valid, frame your argument for deletion in a way that acknowledges that.

(Nice link. I was unaware of the name for that heuristic.)

I think that is a really important thing to bear in mind when reading Hacker News, or pretty much any online venue. People who contribute or even post comments are not the majority. SO rates me in the top 20% of Ruby developers, because I answered a few questions on the site.

After all, you consider C# an uncool language.

That couldn't be further from the truth... I love slinging C#, it's far and away my favorite. It doesn't have that HN hot-shit cachet that Go or Rust or Scala or Lisp-likes or ML-variants have, however.