41–50 of 83 posts
> A minimalist real-time framework for tomorrow’s apps > Feathers has adapters for 15+ data sources and 4 different ORMs out of the box. More than any other real-time framework! Huh?
All my code is bloated and messy, tbh.
The term "real-time" means that you can guarantee certain timing constraints. It can only work on a substrate (OS) that supports real-time processing. So I am sure that "real-time" is not what this package is offering.
My guess is that they are pulling that from Socket.IO's use of the same "real time" term. Which I suppose is to denote that it's not ajax polling (though I understand that Socket.IO does poll in some situations...)
> A minimalist real-time framework for tomorrow’s apps > Feathers has adapters for 15+ data sources and 4 different ORMs out of the box. More than any other real-time framework! Huh?
> A minimalist real-time framework for tomorrow’s apps > Feathers has adapters for 15+ data sources and 4 different ORMs out of the box. More than any other real-time framework! Huh?
Out of the box maybe the wrong way to describe it. You install additional plugins for the different data sources support.
From a glance what makes this appealing to me is the fact that there's less magic than with Meteor, which means I can use my own build process, and I can use any compile to js language.
> A minimalist real-time framework for tomorrow’s apps > Feathers has adapters for 15+ data sources and 4 different ORMs out of the box. More than any other real-time framework! Huh?
for those wondering the difference between this and Meteor. Here is the blurb Feather vs Meteor http://docs.feathersjs.com/why/vs/meteor.html
Earlier quoted context omitted.
Disclosure, I'm one of the creators of Feathers. You are right Feathers is MIT and so is Meteor. They both do real-time, albeit a bit differently, so we like to consider Meteor an alternative to Feathers and vice-versa. We are trying to be as transparent as possible and because we don't currently have any formal support from anyone except for the contributor's time and energy, we rely heavily on the community and nee…
What happens when the connection between the server and a client is broken? Will Feathers automatically (and invisibly) restore it?
Earlier quoted context omitted.
Disclosure, I'm one of the creators of Feathers. You are right Feathers is MIT and so is Meteor. They both do real-time, albeit a bit differently, so we like to consider Meteor an alternative to Feathers and vice-versa. We are trying to be as transparent as possible and because we don't currently have any formal support from anyone except for the contributor's time and energy, we rely heavily on the community and nee…
Except, claiming you guys are "Real Time" just because you offer a basic websockets implementation and positioning your offering as anything that compares to Meteor is a sham. You don't have real time. You have web sockets that anyone can trivially hook up with NPM. You're undermining Meteor's exhaustive real time functionality when you say that. You are also tricking would-be users who don't know any better. They wi…
As a counter-point, I have built "real time" web apps and Feathers was exactly what I'm looking for and matches my mental model for what that word means.