That would miss the point of this submission. But you can submit it again with the actual title... The discussion will certainly be different if there's any discussion at all.
From what I can tell (I could be wrong), Meteor has templates (view layer) that are reactive to data model changes. Espresso on the other hand both doesn't seem to impose a view layer but also introduces reactivity WITHIN the data model.
The article contains a lot of enterprisey gibberish. However, from what I inferred from the few meaningful passages, I suppose Espresso Logic could be quite useful.
Unfortunately, the sign-up process currently only returns a blank page. If the description in the article and on the website is correct though, Espresso Logic does for database-backed business processes what AngularJS does for front end logic or what Excel does for spreadsheets:
It allows you to create REST services from database tables. These services can be used for composing more complex business processes. The software watches changes to the data and propagates these changes to each process that uses said data.
Pretty much like when you change a cell in Excel that change is reflected in each formula that makes use of that cell's data.
If done correctly and in a usable fashion this is huge stuff along the lines of Bret Victor's reactive documents paradigm: http://worrydream.com/Tangle/
It's applying the the idea of reactive programming to the CRUD web app world. It sounds like a pretty reasonable thing to do. What is hard to understand about that?
It's the danger from leaning too closely on the press release—a good journo's job is to make sense of stuff, not add to the cruft. The headline is as clear as mud; it needs a good editor.
It should be noted that the article was posted by TechCrunch's enterprise writer, Alex Williams, who's a less-frequent author. (not to be confused with other TC writer-with-a-similar-name Alex Wilhelm)
Other articles by Williams have a similar style of prose, although with fewer buzzwords:
