31–37 of 37 posts
Hey everyone, one of the founders here! We've written a blog post that pretty much sums up our vision on real time infrastructures and our drive for this product. Have a look: http://blog.telepat.io
Hey everyone, one of the founders here! We've written a blog post that pretty much sums up our vision on real time infrastructures and our drive for this product. Have a look: http://blog.telepat.io
I would love to have a way to use your system with Lua ..
Earlier quoted context omitted.
They make a comparison in their Docs. http://docs.telepat.io/#comparison
Thanks! EDIT: looks like the comparison is Derby only - racer is a bit more flexible IMO
I think your comparison with Meteor is not fair. You are not obliged to use Meteor in back and front, you can have a meteor backend and load a DDP client in about any language. And as I'm doing one right now you can have a only front application talking to a rest server. So it's more flexible than what you tell in your comparison. Also I might not be fair because I'm a Meteor addict :D
I think your comparison with Meteor is not fair. You are not obliged to use Meteor in back and front, you can have a meteor backend and load a DDP client in about any language. And as I'm doing one right now you can have a only front application talking to a rest server. So it's more flexible than what you tell in your comparison. Also I might not be fair because I'm a Meteor addict :D
Thanks, we'll revisit this and check our comparison, we haven't used Meteor extensively so far, so we might have missed stuff. The reason we have that comparison section is that we get asked about this quite a lot, so we wanted to have a public statement on what we think the main differences are from similar products.
* Meteor is a solution for both frontend and backend development, while Telepat focuses on backend functionality.
- You can use it for just the backend if you want. This statement is true, but just noting that you don't have to use both sides.
* When using Meteor in the backend, you also need to use it in your frontend app. Telepat lets you use any frontend framework.
- You don't have to use it with just Meteor's front end (which is I think what you meant). It has integrations with other front end frameworks and you could use it with just about any front end framework as long as you add some boilerplate to communicate with the client-side store and DDP.
* Meteor is a solution for creating webapps, and running on mobile devices works only via webviews. Telepat enables native clients and native functionality for mobile or embedded.
- Not true actually. They make it the easiest to get mobile apps out with Cordova and webviews, but there are various libraries out there like the ObjectiveC-DDP or meteor-ios library that integrates natively with iOS applications.
* Telepat allows using adapters for 3rd party databases, messaging queues and push transports.
- You can do this with Meteor as well and integrate NPM packages.
I hope that helps shed some light on the comparison.
The platform looks great though. I'll definitely have to take a look at it sometime soon.