> Can someone please explain why the rage is not directed at phone manufacturers [...]
Because every single statement from phone manufacturers have indicated that it was the carriers that demanded this be put on the handsets (or did it themselves in cases of operator modifications).
The only carrier I've heard say very clearly that they are not using Carrier IQ is Verizon.
I think the guys at Nokia design will be very happy with that comment. Fortunately most of them are still employed with Nokia and working on exciting stuff.
I feel bad for most of the MeeGo devs though. Most of them were laid off or quit in frustration over having their baby flushed down the toilet. Quite a large number of them ended up with Intel to keep working on MeeGo, just to see Intel drop the effort as well. Must be incredibly frustrating.
Disclaimer: I work as a software engineer at Nokia in Australia.
Disclaimer: I work as a software engineer at Nokia.
Australia is very much an English speaking country (although we are at the ass-end of the world), and the N9 is getting a lot of active marketing here [1, 2].
I have also been working on the software for the N9, but most of my development has been on device, either on the N950 or the N9. We always grumble that we don't get enough devices, but these guys must have been frustrated about something else to go that far out.
There were a lot of problems developing for the N9, don't get me wrong, but they were not endemic to MeeGo over Symbian or S40 where I've also worked.
Ticks me off, however, that they litter the browser history with a tons of pages, but make it impossible to use them for anything, i.e. pressing the browser back button doesn't do anything (Chrome 14.0.835.202 on Mac OS X).
Because the profit comes over a shorter period, i.e. shorting stock from the 3rd to the 5th. If they just bought at the lower price after the announcement they would have to wait for a longer period before they would gain the same profit as through shorting the stock.
But you do have to keep on top of whatever security holes there may be in your own code, and fix whatever bugs pop up. Hopefully before a XSS vulnerability is exploited.
There was a long discussion [1], and in the end Gerrit was chosen. I have used Review Board previously, but actually like Gerrit quite a lot now that I'm forced to work with it ;)
At work we have just rolled out Gerrit as the review tool. The setup is simply that you push your commits to Gerrit, then reviewers can comment on and approve (or not) the change in the web tool. Reviewers can also fetch your patch and run it on their own system.
After a change has been approved, it is pushed into the CI system by Gerrit, and if/when it passes that it is pushed into the public repos.
Before that all reviews were done by passing around diff files.
You might say it's slimy, but turning it on its head (and without looking at the new APIs, etc.): Apple realised with Camera+ that there was a need for a physical button for taking a picture, the inclusion in iOS5 of this feature means that all camera apps (presumably) get the ability to use the physical button, rather than the camera apps hacking it in.
Again, I don't know if Apple is opening this up, so I won't describe it as slimy or not.
Someone like Red Pop [1], however, might be worse off though...
Edit: Re-reading the rejection notice from your link [2], it seems clear that Apple won't be able to reject people based on that clause again. At least, using the volume button for camera now seems to be pretty standard (IANAL so YMMV).
[2] »Your application cannot be added to the App Store because it uses iPhone volume buttons in a non-standard way, potentially resulting in user confusion. Changing the behavior of iPhone external hardware buttons is a violation of the iPhone Developer Program License Agreement. Applications must adhere to the iPhone Human Interface Guidelines as outlined in the iPhone Developer Program License Agreement section 3.3.7«
Note that the numbers stated by rmc2 are not the number of public holidays, but the number of vacation days you, as an employee, has a year. Typically this is on top of public holidays. Of course, most European countries, IIRC, do not shift holidays that fall on weekends to the preceding or following work days.
> Some of the available energy is lost as heat and in the internal rearrangement of chemical compounds and other changes in entropy.
So not all of the difference in efficiency is made up in the form of heat. Unfortunately, I don't remember enough biochemistry nor thermodynamics to dive deeper into this, but I think this article is a good starting point for a discussions, which has otherwise just been dismissed with the "a calorie is a calorie" argument.
You should be able to check whether it actually launches safari, e.g. by pressing the home button and the actually launching safari, should look the same as the screen you just left.
Yes, the shit sandwich, as one trainer I had called it. If you have someone who uses the sandwich, each time he says something nice you start bracing yourself for the shit that follows. Personally, I believe you should be up-front about criticism, but be aware of how it will affect the other party. There's lots and lots written about this, so I won't trudge through it again, but keeping non-confrontational language focussing on the thing that is wrong rather than "you did it wrong" is usually better.
Like the previous commenter said, it is difficult, but the shit sandwich is not always the way to go, especially not if giving feedback to me.
The times I've had a multi-leg flight (internationally), it's always been the same plane. The airline still makes everyone get off, bring in new clean blankets and pillows, and ensure that no one left anything behind. Feels a bit annoying when you just go back to the same seat, but I understand why.
Then you will write a very interesting, but somewhat misleading blog post, just like everyone else has written in the past few weeks.
The point is that the database on your phone is a subset of the greater (global) database mapping wifi and cell access points to location. The local database contains timestamps of when your phone downloaded the information. The global database only contains a list of access points and approximate locations of those access points.
That way, when your phone sees an access point it can look up in the database (locally or globally) and see if this access point has been pinpointed, if it has it will be another tool for your device to provide you with a proper location.
In other words: animating the points in your database will show the first time your phone downloaded information about a specific access point, which will give you a trail of your movements (to a certain extent limited by the factors mentioned above).
Just FYI: You are able to play music from your iPhone through iTunes without having any music on your laptop.
Just plug it in, but don't sync it (apart from the initial 1-step sync), open the iPhone in the iTunes sidebar, and you should be able to play your music right away including playlists (some authorisation might be needed). Works very well for me.
Because every single statement from phone manufacturers have indicated that it was the carriers that demanded this be put on the handsets (or did it themselves in cases of operator modifications).
The only carrier I've heard say very clearly that they are not using Carrier IQ is Verizon.