Liquidfun – 2D physics engine for games
github.com
github.com
For applications on Google Play that integrate this tool,
usage is tracked. This tracking is done automatically using
the embedded version string (b2_liquidFunVersionString),
and helps us continue to optimize it.
Is this tracking functionality restricted to libraries by Google employees? Seems like it would be useful for all third-party library developers to see how their libraries are being used and can be improved. "For applications on Google Play that integrate this tool, usage is tracked."
Imagine if every open source library did that."each end user consents to the collection, storage, and use by QCE and its affiliates and service providers of Statistics from the Software and the transfer of Statistics between QCE and its affiliates and service providers (which may be in the United States or in other countries), in each case for the purposes of (a) facilitating the provision of new products, updates, enhancements and other services, (b) improving the Software, and other products, services and technologies, and (c) providing new products, services or technologies to You and customers of QCE and its affiliates;"
To be fair, they're giving away a great SDK for free that they've put a lot of effort into, so they can demand what they like from the license. Google can too - you don't have to use the free stuff they're giving away.
I use to be the "Data Protection Expert" at a firm a few years ago, but really all that happened was they sent me on a course and I read the rules. Never had to actually deal with a case.
It's easy to remove, and they only track which apps use it to gauge how popular it is. Hardly evil.
https://groups.google.com/forum/#!topic/getglimpse-dev/KA95n...
A big part of the decision is opt-out vs. opt-in, and how it would even be possible to make opt-in return meaningful results in a library. Also, one of the main problems was managing the expectations of the users of the library, many of whom would only install it through a packaging system which provides little means of documenting that tracking is included and enabled by default.
Here is the initial thread sharing a user's surprise:
https://groups.google.com/forum/#!topic/getglimpse-dev/7WgpX...
If someone decides to attempt something but there's already a similar project, why do so many think they should abandon their own to contribute to the other?
They can always contribute down the road.
If everyone collaborated on a few such projects, we'd have a few really great Eiffel towers scattered around.
If everyone started their own, we'd have a million piles of metal all over, and very few towers.
But if I wanted to attempt to build my own Eiffel Tower in my backyard, why is it bad that I wish to do so? Maybe I just want to do it to see if I can accomplish it?
According to wiki.answers, it took 300 people just over two years to build the Eiffel Tower.
Now compare that to Linux, or Gimp, or any other large OSS project and tell me the scale is still off. Or were you claiming that I was off in the other direction? In which case... I might agree with you. ;-)
> But if I wanted to attempt to build my own Eiffel Tower in my backyard, why is it bad that I wish to do so? Maybe I just want to do it to see if I can accomplish it?
It depends entirely on your motive and goal. If your goal is to build it yourself, if your motive is just "see if I can build this with my own power" then there is nothing at all bad. I applaud that. If your goal is to make the best software to fill a certain gap, if it's to make the world a better place with the highest change/effort ratio, then I would argue that adding your knowledge & power to an already existing project is the better way.
Sometimes it is easier to work within an existing project and sometimes it is easier to just fork to meet your own needs, unimpeded by the pace of the original project's maintainers... neither choice (to fork or not to fork) is correct for all situations.
Until I make mine...
Google tries with Google Code now, but GitHub has probably much more traction. So, you may be right. I'm just not sure if they would do it, because the monetization is different. Or will we see AdSense inside GitHub pages for open repositories ;)
Probably does not make sense to them, most GitHub users are programmers who surf the web with ads disabled.
Now I really hope they don't acquire Github. No website I know of has improved in such a consistently good way. Pure UI improvements, awesome new features and no feeling of feature creep on the user side (I don't feel overwhelmed by Github's features at all, I just want to try them all!).
Google does a decent job on their apps but I honestly think Github is a much higher quality shop: do one thing and do it extremely well.
With all that said, how much Google uses Github has little to do with acquisitions. They also use Twitter and you won't see them acquiring that.
Awesome phrase that I shall steal for myself. Like, "the team wanted to use Git but management had their head stuck all the way up SVN's trunk."
You're saying this because you haven't heard about or used atom.io ;)
But atom.io is not part of Github. Sure, it's made by them, but when I talk about Github I mean the website.
Edit: here's a video showing the technique: http://vimeo.com/4391370
- OE-CAKE[1]
- Phun/Algodoo[2]
Which may give some examples of what could be done with this.
[1]http://www.teq.com/blog/2010/03/oe-cake-physics-simulator/