Just checked and it's still up, hasn't even restarted.
Not sure why you think the presence of copyright makes something open-source. All open-source licenses depend on copyright, otherwise the code would be in the public domain.
IANAL, but I thought the phrase "All Rights Reserved" was in direct opposition to "Some rights reserved, some rights released under the following conditions" upon which Open Source licenses are based
So, yes, AIUI all creative works ever have copyright, but only Open Source grants rights to others, such as folks who might want to contribute to your project
I agree with the Objective-S goals [1], and it is cool to see research in this direction.
Are the mechanisms for defining architectural styles and some predefined styles (OO call/return, pipes & filters, REST and event broadcast) all that is new from Objective-S? Any other future goals? These seem relatively easy to implement as e.g. Lisp macros? Clojure supports many of these.
Personally, I would like to see more research in program semantics. I think languages should try to reduce expressiveness whenever possible by offering mechanisms to do so, i.e. DSLs and DSL tools. Along with the total lack of popularity of design-by-contract / Hoare logic / refinement types, I think this is the biggest mistake in modern language design.
In other fields, engineers strive to use components and to combine them in ways that yield artifacts with provable properties. An elementary example of this are truss structures in mechanical engineering.
There is not that much research direction in this area. Personally, I like Dafny [2]. There is quite a lot of research on advanced type systems and theorem proving, but I think there is still a big gap in usability and automation. I think DSLs to restrict semantics + automated program analyses could be an excellent alternative. Infer [3] is pretty nice. Similar approaches that targeted a language with better semantics would be able to offer a lot more guarantees.
Marcel, it might help non-language design experts like me to wrap their head around Objective-S and the notion that "OO call/return, pipes & filters, REST and event broadcast" are just (higher-order?) styles that can be implemented in a truly general purpose language (i.e. Objective-S) by providing concrete examples of how Objective-S does this and other presumably-general-purpose-but-not-actually-according-to-you do not?
Is functional programming yet another style, or is it a subset of call/return, or a subset of pipes & filters? If it is its own style, how might Objective-S implement this style? What would map-reduce look like? What about higher order functions and currying?
Or is Objective-S itself at root a functional language? You've said very categorically in another comment that Objective-S is NOT just reinventing Lisp. Can you explain?
Perhaps my questions don't make any sense. As I said, I'm no meta-language expert.
It looks to me like the situation we have today is that architectural components are deployed as separate binaries ( queues, proxies, web server etc), with PL being used mostly as glue code passing data between them using client apis.
Provided i correctly understood Objective-S endgoal, what makes you think integrating them into a language runtime will lead to better results ?
While there is support for autocomplete in the Stsh framework (for the interactive shell, but you can use it independently), there is no LSP support yet.
May I ask what you would be interested in doing with it?
Note: very pleased that the box serving the site is pretty consistently at less than 1% CPU during the HN hug of death.