Announcing Opa 1.0
blog.opalang.org
Announcing Opa 1.0
1–10 of 15 posts
Re: Announcing Opa 1.0
#2Oh great. It's still AGPL :-|
Re: Announcing Opa 1.0
#3Oh great. It's still AGPL :-| https://github.com/MLstate/opalang/blob/master/LICENSE
The license has changed, read http://blog.opalang.org/2012/05/opa-license-change-not-just-...
The source code is released on github with a delay of several days.
Re: Announcing Opa 1.0
#4Re: Announcing Opa 1.0
#5So, first they ditch their native syntax for a more JavaScript-approach, now the native backend is being replaced by node and mongo? With all these fundamental changes, is this the right time for a 1.0 release?
Re: Announcing Opa 1.0
#6Maybe it's time to rename the project once again with so much changes ....
Re: Announcing Opa 1.0
#7Maybe it's time to rename the project once again with so much changes ....
Opa never changed name.
Re: Announcing Opa 1.0
#8So, first they ditch their native syntax for a more JavaScript-approach, now the native backend is being replaced by node and mongo? With all these fundamental changes, is this the right time for a 1.0 release?
There is a few reasons. Pick your favorite:
1) All the features we wanted are in.
2) We need to catch up on Chrome 19.
3) Team was thirsty and needed a good excuse to have beer party.
Re: Announcing Opa 1.0
#9Sad to see a project with so much promise jump on the latest trendy bandwagon. I think I'll stick to Ocsigen. http://ocsigen.org/
Re: Announcing Opa 1.0
#10Sad to see a project with so much promise jump on the latest trendy bandwagon. I think I'll stick to Ocsigen. http://ocsigen.org/
You can still use the native runtime if you want. Turns out, a majority of users prefer the standard JavaScript stack -- and now we give that choice.