> 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.
Because every single statement from phone manufacturers have indicated that it was the carriers that demanded this be put on the handsets
Aww. Poor vulnerable and naive billion dollar phone manufacturers! </sarcasm>
How does that exonerate the phone manufacturers? At the very least they should have disclosed this to the people they sold phones to.
Even at that why is the rage not directed at the carriers? In addition, I doubt the carriers can make such modifications without the active participation of the phone manufacturers.
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.
Please pass on my remarks to the design team - I'm very impressed with their work, and I do wish that they continue their excellent designs.
I truly wish that Nokia had gone behind the N9 with everything it deserves. I feel it's the first time that Apple has actually been challenged in design, in integrity towards an ideal, in making something that exemplifies that internal drive.
After seeing the WP7, even knowing it was coming, I know that their lovely design work was cheapened by that release. It's still good design, but it lost something tangible and wonderful, that sense of being something different and better. By shipping WP7, it became something that exists secondary to another goal, instead of a goal unto itself. Cheapened, as though a device that exists not symbiotically with the software designed to run on it, but any random garbage that can be sold with it.
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).
I'm a tab junkie. Everything not within the same domain typically goes into a new tab. I know what you mean though. You would have gone nuts at that HTML5 history game
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.
Thanks, I had seen Jekyll but this looks like Jekyll plus sensible defaults for a website with all the bells and whistles. My personal site has no bells, and I can't whistle too well. :-)
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.
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 ;)
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.