Hacker News Reader

Comment by al2o3cr | Hacker News Reader

CORBA called, they want their ideas back

Even in JS, the Meteor framework was basically created to implement this.

Except they actually implement things like validation, because as much as one may want to unify both environments, the reality is that exposing all your methods to the outside world may have some pitfalls, to put it mildly.

What ever happened to Meteor? It was flavour of the month a few years ago, with many a frontend dev ranting about how great it was. Now seems to be forgotten about.

Hassles with installing NPM packages (they used their own package manager (!)), it was incredibly heavyweight, baked in reliance on MongoDB, and a weird templating language caused a kind of death-by-a-thousand-cuts situation.

Plus, React came out and blew Meteor out of the water.

One of the early Meteor developers, Evan You, went on to create Vue.js.

We tried to use it in real life for smilebooth. It was nice for little sample apps but as soon as you hit something it was not designed for, the workaround was more painful than if you had just gone with a plain rest api. Scalability was pretty limiting too.

Facebook came out with GraphQl and they went on to build Apollo for it and left Meteor behind.

Smart phones. Meteor came when people used browsers. Once the app model became prevalent, and users expected native integration, slow butt JavaScript in an HTML5 app on your 2012 phone CPU was a non starter.

I ran into a company recently that was still using Meteor (B2B with roughly 50 million USD of funding). It made me realize the consequences of choosing a technology for a major project before it's gotten widespread acceptance. Made me realize I need to be a bit more cautious, and that I've gotten very lucky.

I worked on an app that was Angular 1. That did get widespread acceptance at the time, but still got dropped like a hot potato when React came along. Probably the backwards incompatible changes with Angular 2 were a big factor as well.

And Opa language and framework. (To note, the language itself was awesome, too bad it was tightlyccoupled to the framework since that approach never seems to work)

By default, a Liaison backend doesn't expose anything to the frontend. For a method (or an attribute) to be exposed, it must be explicitly declared as such.

Yup.

Diagram from this project: https://github.com/liaisonjs/liaison/blob/master/assets/cros...

Diagram from CORBA: https://en.m.wikipedia.org/wiki/File:Orb.svg

Yup. Looks exactly like it. SOAP is not that different either.

Add: my PTSD from a few months with DCOM is acting up :)

Reply on news.ycombinator.com