Have you considered that you could potentially make a lot more by open sourcing NOLOH and building a support infrastructure around it? It seems like the closed source aspect of it might be holding you back. If NOLOH truly is the Rails of the future, it might be wise to unleash it.
I've always thought this was part of what kept REBOL from catching on. Nice little language, but its closed nature hampered its adoption.
We have. The problem of course stems from the more established brands picking apart our tech and incorporating it into their own, thus making our tech obsolete. There's also the issue regarding our existing customers that paid for Professional and Enterprise licenses. We currently offer free licenses to open source projects, but we do understand that there are those that are turned off to any proprietary tech, even if they'll never actually go under the covers.
We'll likely revisit this issue later in the year after we make a series of major product announcements. Those announcments may make it unnecessary for the tech to continue to be closed, until then, everything we do other than the core is open source and available on github, this includes numerous modules. I'll likely blog about this in the next month or so.
Comments
Have you considered that you could potentially make a lot more by open sourcing NOLOH and building a support infrastructure around it? It seems like the closed source aspect of it might be holding you back. If NOLOH truly is the Rails of the future, it might be wise to unleash it.
I've always thought this was part of what kept REBOL from catching on. Nice little language, but its closed nature hampered its adoption.
We have. The problem of course stems from the more established brands picking apart our tech and incorporating it into their own, thus making our tech obsolete. There's also the issue regarding our existing customers that paid for Professional and Enterprise licenses. We currently offer free licenses to open source projects, but we do understand that there are those that are turned off to any proprietary tech, even if they'll never actually go under the covers.
We'll likely revisit this issue later in the year after we make a series of major product announcements. Those announcments may make it unnecessary for the tech to continue to be closed, until then, everything we do other than the core is open source and available on github, this includes numerous modules. I'll likely blog about this in the next month or so.