> I hope that you publish your work so that we may properly critique it.
I don't know about this author, but for me, this would emphatically not be a motivating reason to publish my work. I might publish work so that someone could get some use out of it, or to show off my brilliance. But if all you're going to do is critique it (no doubt with all the familiarity born of five minutes of looking at the tutorial), then I'd just as soon you never see it.
I don't think the person you're quoting would advocate that languages must start out as open source. Go sure didn't. It was developed closed source within Google for two years before it was even announced.
I guess it depends on how the critique is delivered. I would unironically love it if an expert level in [repo language] would come along and critique my open source code.
If they were an arrogant shit-head then I'd probably just block them, regardless of the technical merit of what they wrote.
casual criticisms on hackernews are still more valuable for drawing attention to your project than in depth comment chains from renowned experts on [repository manager of choice].especially since those comment chains are undiscoverable unless you're already interested in the project(or the chain gets linked on hackernews)
plus this may just be me as a non (designing a tool language for a project) dunce speaking but reading a critique of a language/framework that i haven't thought of makes me want to try out the language and see how that shortcoming affects the way i work. it's the reason i tried out Go and Elm and Vue.js
I don't know about this author, but for me, this would emphatically not be a motivating reason to publish my work. I might publish work so that someone could get some use out of it, or to show off my brilliance. But if all you're going to do is critique it (no doubt with all the familiarity born of five minutes of looking at the tutorial), then I'd just as soon you never see it.
>Here is another language designer who is not me saying "closed languages die" (https://blog.golang.org/open-source).
I don't think the person you're quoting would advocate that languages must start out as open source. Go sure didn't. It was developed closed source within Google for two years before it was even announced.