Earlier quoted context omitted.
I know it's a total pipe dream, but this is what makes me most sad about lisp never being taken seriously. It could have been common practice to create and pull in new language constructs like what this is doing.
Clojure seems to be gaining more and more momentum, unfortunately just as I changed jobs away from a clojure shop.
Cell Lang: Why yet another programming language?
51–60 of 126 posts
Re: Cell Lang: Why yet another programming language?
#52> Why yet another programming language? 'Because I wanted to' is a sufficient reason. Create all the programming languages you want and share it with the world!
I know it's a total pipe dream, but this is what makes me most sad about lisp never being taken seriously. It could have been common practice to create and pull in new language constructs like what this is doing.
This is why D does not have a macro preprocessor.
Re: Cell Lang: Why yet another programming language?
#53What's with people tacking "Lang" on to the end of language names? I can kind of understand it with Go, since Google didn't exactly come up with a very searchable name, but now I'm seeing it spread to other languages like Rust, and now here with Cell.
Re: Cell Lang: Why yet another programming language?
#54So basically an actor system with relations between actors, reactivity and automatic persistence. Very interesting concept! Although I do wonder if this couldn't be implemented as a library for an existing language. Doesn't seem like it is actively developed though, the compiler repo hasn't seen updates since November and the runtime repo since 2018.
temporal.io = durable actors for microservices workflows
Re: Cell Lang: Why yet another programming language?
#55> Then there's support for reactive programming, which is still in its infancy State management for UI I would think should be a first class objective rather than 3rd on the todo list. See SwiftUI for something evolving toward this direction. > The best way to illustrate the advantages of functional/relational programming over OOP is through a case study No, the best way is to be right up front with a real life commo…
> real life common problems and code examples that make life better That is exactly what a case study is. Looking at examples of real world cases.
It is possible to present common problem scenarios and examples up front, even if something is at the idea stage.
It’s commonly done, and can be an effective way of conveying your ideas and getting feedback without pages on end of speculative requirements.
Re: Cell Lang: Why yet another programming language?
#56Re: Cell Lang: Why yet another programming language?
#57I've always been intrigued by the idea of a language that enforces a separation of queries and command. Functions (queries) return values and have no side-effects, where procedures (commands) that can have side-effects and don't return a value.
Re: Cell Lang: Why yet another programming language?
#58Huh?
Re: Cell Lang: Why yet another programming language?
#59I came across cell-lang a few years and really liked the ideas in it. It does a lot of the things that was proposed in Out of the Tar Pit, which is probably the paper that has influenced my opinions about programming the most For applications that don't have high performance requirements I could see this getting adopted - automation and IoT devices are a couple of areas that spring to mind
[0] http://kmdouglass.github.io/posts/summary-out-of-the-tar-pit...
Re: Cell Lang: Why yet another programming language?
#60What's with people tacking "Lang" on to the end of language names? I can kind of understand it with Go, since Google didn't exactly come up with a very searchable name, but now I'm seeing it spread to other languages like Rust, and now here with Cell.
Lisp does it too ( https://lisp-lang.org/ ) - I think it's a reasonably familiar convention