Messages - TheQwerty [ switch to compact view ]

Pages: [1] 2 3 4 5 6 ... 17next
Living Room / Re: Stallman on Android
« on: September 21, 2011, 07:37 AM »
Google said it withheld the 3.0 source code because it was buggy…
This is not true.

Google told Engadget:
Android 3.0, Honeycomb, was designed from the ground up for devices with larger screen sizes and improves on Android favorites such as widgets, multi-tasking, browsing, notifications and customization. While we're excited to offer these new features to Android tablets, we have more work to do before we can deliver them to other device types including phones. Until then, we've decided not to release Honeycomb to open source. We're committed to providing Android as an open platform across many device types and will publish the source as soon as it's ready.

And in a separate blog post explaining Google's role in Android development Andy Rubin said:
Finally, we continue to be an open source platform and will continue releasing source code when it is ready. As I write this the Android team is still hard at work to bring all the new Honeycomb features to phones. As soon as this work is completed, we’ll publish the code. This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types.
(All emphasis is my own.)

I understand the tech blogs not being able to read between the lines here (lord knows how easy they think it is to develop software), but I'm disappointed that after all this time the view from software developers hasn't gotten out or at least that Google hasn't explained it better.

The official repository, at least before was hacked, always contained the released source for Android and could be built for phones.  Picking up on the emphasis yet? - Android must run on phones.

Froyo (2.2) was intended only for phones and after its release Google created two internal branches:
Gingerbread (2.3) continued to be improvements for phones, and as such was released per usual.
Honeycomb (3.*) contained the changes to officially extend Android to tablets.

Google probably broke the build or compatibility/regression tests for phones in Honeycomb and if they were to commit these changes the official repository would no longer work for phones.

I get the feeling that they intended to merge Gingerbread into Honeycomb and release it, but due to whatever delays, Honeycomb won't be officially released now. Instead Ice Cream Sandwich (?.?) will merge Honeycomb, Gingerbread, and likely the Google TV branch into a single base.

Now we can focus on the real frustration with Google's "open" model for Android: they are essentially the only developers and they do their work in private. This would be a non-issue if all their branches were public, however, I feel there are valid reasons they aren't:
1. Google keeps a competitive edge without revealing their current & future plans.
2. Google can develop quicker without the many pull requests from the community (take it or leave it but at some point coordinating community efforts becomes more difficult than doing it yourself).
3. It removes a lot of speculation that they'd otherwise need to respond to.
4. It prevents companies from releasing products utilizing pre-production code, which is extremely important when many of these companies have shown an inability to release timely/any updates.

Which leaves the problem of making deals with companies allowing them to release products using code that won't be committed to public for months. Not sure how I feel about this since I'm not familiar with how difficult it would be to get similar access by a smaller company.

TL;DR: My opinion is that Google decided to withhold Honeycomb rather than commit code to the repository which wouldn't work on phones. 

The real frustration with their "open" model is their use of private branches but their possible reasoning seems valid.

Sorry for the long post, just getting tired of what I see as a logical decision continually being described as malice.

Meh... I really don't understand why the entire Internet seems to be fawning over this demo.

It's great that booting Windows may be quicker, but this doesn't seem like much of an improvement over current competition.

I have a Samsung Series 5 Chromebook, it boots in less than 10 seconds from cold.
My MacBook Pro with SSD boots quick enough as well - I've never bothered to time it but I'm always surprised by how quick it seems.

They also both have incredibly low powered sleep states which they can remain in for days without killing the battery and wake from instantaneously (at least to me).  This renders the longer cold boot times moot.

Again, it's fantastic seeing Windows boot up as quickly - though until our IT gives us anything other than XP and trims their 20 minutes of drive decrypting, start-up scripts, and updating I'm not sure I care.

But my biggest complaint is the video itself... It's a worthless demonstration.
We have no idea what the machine's specs are; they strongly imply it's SSD but no other info.
Taking out one battery proves nothing.
Not showing us the shutdown sequence means we don't know whether the laptop is actually booting up fresh or waking from hibernation. For all we know it's a virtual machine!

I watch that and cannot believe they'd waste time filming something so pointless...
And why the heck doesn't Microsoft have any tables?!?

Part of the problem is many developers seem to think the answer to making profitable apps is still in selling the app itself.

I think there's more money in ads and in-app purchases and if they used either of those then Amazon giving away their app for free would have been a fantastic opportunity for them.

Mobile apps are the razors and printers of the software world.

Living Room / Re: Android tablets to rival iPad
« on: July 26, 2011, 11:48 AM »
… the 10.1 is not available (at least not in Europe).
Should be available in the UK pretty soon, so it's getting closer.  ;)

Well, at least it isn't because of a security problem!

I actually think that makes it worse.  How can one trust their security code if they're having this much of a problem detecting how much space a user is using vs what they're allotted?

Pages: [1] 2 3 4 5 6 ... 17next
Go to full version