Live data from Hacker News

How Eve unifies your entire programming stack

hackernoon.com

51–60 of 109 posts

Re: How Eve unifies your entire programming stack

#51
Title : "your entire programming stack".

I feel sad when I find that web programmers think there are only web stacks and "programming" refers only to web programming.

It is not entirely the case here, but the description of "a core system" as :

- Database layer

- Remote API layer

- Application layer

made me tick.

Re: How Eve unifies your entire programming stack

#53

> Eve is the culmination of years of research and development by the visionary team who previously founded Light Table. ...and then abandoned it after getting me excited about a possible Emacs replacement...

Still being developed, though: https://github.com/LightTable/LightTable

Re: How Eve unifies your entire programming stack

#54
post #4
post #2

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.

Author here. I certainly understand that seeing progressively more sophisticated practical applications will help people "get" Eve. I look forward to that myself. In the meantime, I hope I can show a "plausibility argument" for Eve's potential by pointing to areas where the status quo of mainstream programming is visibly less than ideal. Uniformity of data formats and operations across the programming stack is one su…

This article got me curious about eve. Now i think you need to find your "killer use case".

Ror had none, because it was doing what everything else was doing, just faster. But a successful business used it so people got interested.

Node.js first demonstrated chat server

Angular.js showed two way binding of dom to data using declarative syntax

React had those crazy dom update benchmark.

Golang showed various pattern for synchronizing using channels. The "hello world" of go was a chat server.

Etc.. now all those tech had many other great feature. But you need to find one single killer concrete example for the tech, that it performs an order of magnitude better / simpler / faster / safer than any other.

Also, never ever forget runtime speed benchmark. You don't need to be the best, just not catastrophicaly bad.

Re: How Eve unifies your entire programming stack

#55
post #51

Title : "your entire programming stack". I feel sad when I find that web programmers think there are only web stacks and "programming" refers only to web programming. It is not entirely the case here, but the description of "a core system" as : - Database layer - Remote API layer - Application layer made me tick.

Always watch out for using word always.

Never say never.

Re: How Eve unifies your entire programming stack

#56
post #3
post #2

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 member] Out of curiosity, what would you classify as a practical application? We're looking for some interesting examples to build to help show Eve to folks. EDIT: For instance, one of the examples we're throwing together now is an app that a food truck owner could use to put up their menu, manage a queue of orders (in person and online), alert people when their order is ready, accept payments, and post to socia…

I would be interested in any application that crosses many layers. If you create an IoT device you need:

+ bootloader

+ radio stack

+ HAL

+ custom code layer, say Arduino

+ communication layer

+ mesh hub (+ mesh communication layer)

+ sink code on mobile (bridge, no access to encrypted data)

+ local communication on mobile (low latency)

+ cloud

+ remote access

+ interfaces, mobile/dashboards

It has also a lot of crosscutting concerns: latency, scalability (keep it local stupid), bandwidth, security, safety. Till out in the field: how to remotely define if it is hardware or software to reduce number of devices that gets returned.

Re: How Eve unifies your entire programming stack

#57
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.

Re: How Eve unifies your entire programming stack

#58
post #51

Title : "your entire programming stack". I feel sad when I find that web programmers think there are only web stacks and "programming" refers only to web programming. It is not entirely the case here, but the description of "a core system" as : - Database layer - Remote API layer - Application layer made me tick.

Same here when they refer to front-end as a synonym for Web UIs, as if there wasn't quite a few of us doing 100% native UIs.

Re: How Eve unifies your entire programming stack

#59
post #15
post #10

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 de…

I think your point is valid in general, but Eve's semantics are deeply rooted in Logic Programming. IMO that's a more fundamental change than what we can hope to get from layering a pattern/library/architecture on top of an existing database or programming language.

Eve is a nicely engineered environment and has basic relational semantics that many streaming query frammeworks and dataflow frameworks have in mind (select with aggregation, update)

But the site doesn't have any discussion of the language's semantics. I know they have mentioned Bloom (bloom-lang.org) as one of their influences. I would like to know how the Eve evaluator handles negation (and what negation means in an Eve context), whether there is a guarantee that a single tick's evaluation will terminate, whether the evaluation is incremental, and whether in doing so, the results are equivalent to a simple evaluator that does not work incrementally (looks at the entire database every time). etc.

Post reply on HN