4 ms·
Announcing Opa 1.0
- mahmud 14y agoOh great. It's still AGPL :-| https://github.com/MLstate/opalang/blob/master/LICENSE https://github.com/MLstate/opalang/blob/master/LICENSE
- mhd 14y agoSo, 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?
- hbbio 14y agoThere 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.
- thesorrow 14y agoMaybe it's time to rename the project once again with so much changes ....
- hbbio 14y agoOpa never changed name.
- gaius 14y agoSad to see a project with so much promise jump on the latest trendy bandwagon. I think I'll stick to Ocsigen. http://ocsigen.org/ http://ocsigen.org/
- MidwestMuster 14y agoIf the bandwagon is a programming language that runs everywhere, on the client and on the server, what's so bad about that?
- hbbio 14y agoYou 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.
- tikhonj 14y agoWhat's wrong with compiling to JavaScript? Is it just bad because it's popular? Of course, I'm biased: the only tool I've used from ocsigen is js_of_ocaml :P.
- halter73 14y agoThe link from the blog back to the project's main website doesn't work properly. Is appears that the logo in http://opalang.org/header_blog.xmlt http://opalang.org/header_blog.xmlt should be linked with target="_top" since the navbar is an iframe.
- yefrederic 14y agoThanks for the report !
- reddit_clone 14y agoWas the native runtime multicore capable ? If so, going to Node is a huge step down.