-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open-source the compiler #2
Comments
So far, the IDE ( a work in progress) and the localization tool have been published, and the runtime is in JS so quite readable. I haven't released the compiler. Beads needs to find a home or at least a supporting environment where it can continue to evolve. Not sure which direction is best yet. We need a lot more users to understand whether this would be better as a supported product with guarantees for fixes, or your typical hope-and-wait situation with open source. A compiler is a very fundamental tool, and i think most people want support if they are going to use it seriously. |
Obviously there is a trust issue with closed-source applications which may turn off potential users. For me, the compiler needs to be "source-available" even if not "open-source", so I have the option of verifying and building it myself. As an interim measure, perhaps the code could be licensed for reference use only. Whatever, I can very much understand your caution and desire to put the project on a sustainable footing. |
The problem i am seeing is that people don’t have any time to try any of the new languages, from Enso, to Red, to Elm, to Beads, etc.; the current environment is so taxing to programmers they have little left in the tank to puzzle over a new design pattern or way of building.
If google or apple introduces something there are legions of people who check it out.
It’s a fair tough environment for indie projects.
edward
|
Any plans to open-source the compiler?
The text was updated successfully, but these errors were encountered: