Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Their response to why it's faster to move while closed source seems kinda like a false dichotomy. They can choose to start with it open disallow input from the community or close their issue tracker to the community.


Why bother doing it that way? Just to entertain people who works like to observe the commit history as the language evolves?


It gives people confidence to start working with it now.


I don't want to commit to a language/ecosystem that might pivot and not open-source.


So that people trying out the language have the freedom know what they're running on their computer.


It's closed so others don't catch up quicker or add those optimizations upstream? Then they have no moat.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: