393 karma · joined July 1, 2010
However, times have changed. The kind of games i'm interested in are ubiquitous in nature. I want to interact with it on the console, the iPhone, the PC, and on the web. I want to write tools that are cross platform. The browser is the ultimate cross platform.
You must bear in mind that this is open source. Oracle does not own this. It doesn't appear to be aware of this.
There are several licenses written that say "you may not use our name to promote your version of the software" or something like that. MIT is not one of them.
Oracle is welcome to fork it and give it a tougher license. Dont expect it will see many commits after that tho.
You've hit the nail on the head with regard to my complaint.
>package hudson;
You might own the trademark Oracle, but you just licensed the use of it to everyone.
http://code.google.com/p/memcached/wiki/FAQ#What_is_the_maxi...
3. Third-party apps that are exclusive to Android.
And followed it up with this:
"At this point, I’m guessing, Android fans are ready to exclaim that the fact that Android supports things like home screen replacements (or other system-level tools, such as touchscreen keyboard replacements) — and that iOS does not — is precisely why they prefer Android, and/or consider iOS to be an unacceptable toy, or what have you. But, again, that’s not the argument I’m making. I’m talking about third-party developer exclusives — and the only ones Android has are ones that Apple doesn’t want."
And yet you provided:
4 system enhancements (keyboard, media player, homescreen, email labeller)
4 apps available on the iOS
1 possibly genuinely killer app, but that falls into the geeky automation category
Creation is never to be sniffed at.
Building main executable... src/types.cpp: In member function 'TypeStatus::operator uintptr_t() const': src/types.cpp:1514: error: cast from 'Type*' to 'unsigned int' loses precision
At least, thats the response I get around here from people.
Yes, we all know that what we need is another platform to target. Get a clue Nokia. Its all about apps now, and this is the priority for app developers:
* iOS
* Android
* WP7
* The fluff in my navel
* Nokia Qt
Pretend all you want, but this is the order my clients budget for.
But to assume the argument has merit, lets follow it to its natural conclusions: since when was SQL a low level language?! SQL servers are vastly more complicated than Rails.
Another assumption the author makes is that, for any programmer, SQL is the constant, and time spent learning Rails is wasted if one has to switch to Django. This just shows the limited world view of the author. For many, Rails is the constant, and SQL, Couch, or Mongo are the choices.
To stick with the tool analogy, C is the giant processing equipment that skilled operators used to print my photos in an hour (http://bit.ly/aCoA0K), while Rails is the little Canon Selphy sitting on my desk. Both produce identical results. One of them does it a lot faster, for a lot less money, and a lot less failures and maintenance.