RailsConf / RubyConf / AgileConf / EclipseCon / EclipseWorld Speaker. OSS Author of Glimmer. MS in SE DePaul (Chicago) and BS in CS McGill (Mtl). Rock Drummer / Snowboarder.
Location
Montreal, QC, Canada
Education
MS in Software Engineering, DePaul University (Chicago, IL, USA)
I already did, and didn’t see anything novel compared to Meteor or even isomorphic frameworks in other languages. And since it’s new, I bet it doesn’t handle as many edge cases yet, so I don’t trust it. That’s my opinion, take it or leave it. In any case, I’m a Ruby/Java developer. I don’t do much JS these days anyways except inside Opal libraries/frameworks (Ruby compiled to JavaScript in the browser). Cheers.
RailsConf / RubyConf / AgileConf / EclipseCon / EclipseWorld Speaker. OSS Author of Glimmer. MS in SE DePaul (Chicago) and BS in CS McGill (Mtl). Rock Drummer / Snowboarder.
Location
Montreal, QC, Canada
Education
MS in Software Engineering, DePaul University (Chicago, IL, USA)
Saw that too. Developers could already do that before since classes/prototypes are shared in Meteor anyways with a toggle for writing extra code as client only (or server only), enabling one to do extra inheritance on the client (or server) when needed. And, that was back in 2014 or earlier if I remember right.
What you're talking about is very different. Layr doesn't share code across layers, it transports the state of the objects when you call a method. To see what I mean, try to implement the example given in the article with Meteor.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I already did, and didn’t see anything novel compared to Meteor or even isomorphic frameworks in other languages. And since it’s new, I bet it doesn’t handle as many edge cases yet, so I don’t trust it. That’s my opinion, take it or leave it. In any case, I’m a Ruby/Java developer. I don’t do much JS these days anyways except inside Opal libraries/frameworks (Ruby compiled to JavaScript in the browser). Cheers.
Let me give you a hint: cross-layer inheritance.
Saw that too. Developers could already do that before since classes/prototypes are shared in Meteor anyways with a toggle for writing extra code as client only (or server only), enabling one to do extra inheritance on the client (or server) when needed. And, that was back in 2014 or earlier if I remember right.
What you're talking about is very different. Layr doesn't share code across layers, it transports the state of the objects when you call a method. To see what I mean, try to implement the example given in the article with Meteor.