8 ms·

Developing using twitter open source and api is essentially asking to to robbed by them if anything you make is successful.

hurrycane 11y ago
Why is that? Finagle, Mesos and Aurora look like solid open source projects from Twitter.
- fernandotakai 11y ago
  I started looking at finagle, finatra and scrooge. i love all three projects. but at the same time, the documentation is really really bad. if you have the same requirement as twitter, nice -- but if you detour even a little bit, you are going to have a shitty time (for example, for thrift, i wanted to use buffered codec instead of framed and there was not a single document explaining how to do it. i spent ~2h perusing unit tests to find a way which i don't know if it's correct or not).
  - deleted 11y ago
    [deleted]
- SEJeff 11y ago
  Aurora is from Twitter, but Mesos is not. They hired some of the team that developed Mesos while in academia, but still. Mesos is external of Twitter. Disclaimer: I use both Mesos and Aurora.
- hurrycane 11y ago
  Also forgot to mention scalding.
- d_t_w 11y ago
  Don't forget Netty..
  - allengeorge 11y ago
    netty is not a twitter project. At various times the major committers have been employed by JBoss/RedHat, Apple, etc. etc.
at-fates-hands 11y ago
Not sure why you're getting downvoted. Twitter has a long and sketchy track record with developers. Exhibit A is TwitPic: http://www.digitaltrends.com/social-media/twitters-war-on-third-party-developers-continues/ http://www.digitaltrends.com/social-media/twitters-war-on-th... But what about services that Twitter replicates? The latest applications victimized by Twitter’s in-house team are photo-sharing platforms like TwitPic and YFrog Back in May, we first heard that Twitter planned to launch its own image posting tool. Up until that point, third party apps were giving Twitter that function. Now that Twitter’s own photo tool has launched, it’s virtually declaring war on the developers who were responsible for creating what has been a very popular aspect of the site. But you're right, if you take time to develop an app using their API, it might just get their attention and then they'll develop their own version and then cut you completely out.
- joefkelley 11y ago
  The crucial difference here is between using a totally open-sourced technology like Storm (or Heron, if they release it) and being a consumer of a public API with a proprietary implementation, or making use of their platform/users/data. Twitter can absolutely block you from their API. Or come out with a competing product that integrates with their own systems better than your product does. But if you're using Storm (or Scalding or whatever), there's really nothing they can do to screw with that.
- saryant 11y ago
  GP was downvoted for failing to differentiate between relying on Twitter's API and their open source software. The two really can't be compared.
ohitsdom 11y ago
What does this have to do with Heron?
briandear 11y ago
Twitter Bootstrap anyone?

hurrycane 11y ago

Why is that? Finagle, Mesos and Aurora look like solid open source projects from Twitter.

fernandotakai 11y ago
I started looking at finagle, finatra and scrooge. i love all three projects. but at the same time, the documentation is really really bad. if you have the same requirement as twitter, nice -- but if you detour even a little bit, you are going to have a shitty time (for example, for thrift, i wanted to use buffered codec instead of framed and there was not a single document explaining how to do it. i spent ~2h perusing unit tests to find a way which i don't know if it's correct or not).
- deleted 11y ago
  [deleted]
SEJeff 11y ago
Aurora is from Twitter, but Mesos is not. They hired some of the team that developed Mesos while in academia, but still. Mesos is external of Twitter. Disclaimer: I use both Mesos and Aurora.
hurrycane 11y ago
Also forgot to mention scalding.
d_t_w 11y ago
Don't forget Netty..
- allengeorge 11y ago
  netty is not a twitter project. At various times the major committers have been employed by JBoss/RedHat, Apple, etc. etc.

at-fates-hands 11y ago

Not sure why you're getting downvoted. Twitter has a long and sketchy track record with developers. Exhibit A is TwitPic: http://www.digitaltrends.com/social-media/twitters-war-on-third-party-developers-continues/ http://www.digitaltrends.com/social-media/twitters-war-on-th... But what about services that Twitter replicates? The latest applications victimized by Twitter’s in-house team are photo-sharing platforms like TwitPic and YFrog Back in May, we first heard that Twitter planned to launch its own image posting tool. Up until that point, third party apps were giving Twitter that function. Now that Twitter’s own photo tool has launched, it’s virtually declaring war on the developers who were responsible for creating what has been a very popular aspect of the site. But you're right, if you take time to develop an app using their API, it might just get their attention and then they'll develop their own version and then cut you completely out.

joefkelley 11y ago
The crucial difference here is between using a totally open-sourced technology like Storm (or Heron, if they release it) and being a consumer of a public API with a proprietary implementation, or making use of their platform/users/data. Twitter can absolutely block you from their API. Or come out with a competing product that integrates with their own systems better than your product does. But if you're using Storm (or Scalding or whatever), there's really nothing they can do to screw with that.
saryant 11y ago
GP was downvoted for failing to differentiate between relying on Twitter's API and their open source software. The two really can't be compared.

ohitsdom 11y ago

What does this have to do with Heron?

briandear 11y ago

Twitter Bootstrap anyone?