I'm excited for Eve and next-gen programming languages but as details emerge, it seems like it could easily have been a few libraries and an architecture pattern in most other functional programming languages. When I first learn about things like the continuation monad or CQRS, I have similar reinvent-the-world fantasies but it's often sufficient to expand my toolkit and change my style (in full disclojure ;-), my default language is clojure/script)
I was keeping a close eye on Eve until it changed direction from <i>programming for everyone</i> to <i>yet another lisp</i>. Is there any writeup/discussion on why this happened?<p>I do like learning about mind-expanding languages, and something resonated with me when the CardWiki interface was revealed. I get that this language is very 'human readable' but at the end of the day if I want to read or write it I will actually have to put a lot of time into learning it.<p>I'm already suffering decision paralysis with my current language shortlist and this language doesn't make the cut. The card wiki was innovative, like LightTable. To me, this is 'just a language'. I realised you moved away from the wiki idea for a reason but is putting a GUI on the language still on the roadmap?
Can Eve call into C without any overhead?<p>If it can't, then "your entire programming stack" is excluding the kernel and a lot of existing libraries/code.
Not convinced either way whether having the same interface for all of the stack is a good idea or not, but it did remind me of Joel Spolsky's blog post on leaky abstractions <a href="http://www.joelonsoftware.com/articles/LeakyAbstractions.html" rel="nofollow">http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...</a>
The part I'm most skeptical of is Eve's universal use of set-based semantics, whether it's needed or not. It seems like making sets and single values look different in the code would be more understandable than making everything look the same. Treating them as different types might be a good way to catch errors, too.<p>But SQL is very successful so maybe they'll do okay anyway.
I've been looking for the holy-grail for years (TodoMVC being my benchmark), and Eve takes the cake.<p>I'm looking forward to compatibility with semantic Web technologies.
After all these promising presentations and blog entries about what thoughts went into Eve, I'm a bit dissapointed by the result. Or I'm ignorant and don't get it (yet?). Sure, it utilizes literate programming and it abstracts a lot away but it does not seem as revolutionary as the communication around it suggested. Maybe the next articles in this series will enlighten me.
I'm glad there are people rethinking how we develop programs. But as a web developer, the examples in Eve looks more complex then a naive implementation using vanilla CSS, HTML and JavaScript would look like, for example, how do you make something 10 pixels wider in Eve ?
Title : "your entire programming stack".<p>I feel sad when I find that web programmers think there are only web stacks and "programming" refers only to web programming.<p>It is not entirely the case here, but the description of "a core system" as :<p>- Database layer<p>- Remote API layer<p>- Application layer<p>made me tick.
Yeah until I really see some practical applications written in Eve I don't think I'm ever going to really get it. It's nothing against Eve, it might be great, but nothing I've seen about it so far as really captured my imagination and I'm wondering if I'm just missing something.
> Eve is the culmination of years of research and development by the visionary team who previously founded Light Table.<p>...and then abandoned it after getting me excited about a possible Emacs replacement...