It is foolish to assume WebOS would have been a huge success if only Android didn't exist. I think WebOS is amazing, but Palm was entirely capable of destroying anything they touched. Plus, I actually consider it better for an open source mobile OS to win out over a closed source one.

And MeeGo? Is one open source linux based mobile operating system really that much more evil than the other open source linux based mobile operating system? How do you know the decision to drop MeeGo in favor of a new mobile OS that focuses on HTML5 based application development wouldn't have happened even if Android didn't exist?

Android is not the be-all-end-all. But it is certainly not the mark of the beast simply because it is experiencing success right now. The fact that it is competitive does not preclude the success of other competitive products.

Think of it this way - if they didn't use Android, there is a very good chance they would still have a horrible UI. But it would then be a phone with a horrible UI and no vast library of Apps. That doesn't make what they are doing good. But it's at least a silver lining.

I have to disagree because I really like the user experience on Stack Overflow. I value one concrete success over many anecdotal failures.

I think Android requires 64 bit. I think Chromium highly suggests 64 bit and it won't work with PGO. And those optimizations are where the FF devs are hitting the wall.

I'm surprised FF could still build with PGO on 32bit Windows with the 3gb switch. It seems like the project is large enough and complicated enough that it should have had problems with this a while ago. I can only guess they've modularized the code quite a bit already to try and fight it.

At least they can still use this toolchain on 64bit Windows and get 4gb of address space there. It should buy them some time. Hopefully, they'll get some breathing room and hold out until 64bit browsers for Windows are more common. The 64bit FF nightlies seem very quick and stable to me. I am looking forward to an official release of them. And, maybe after that, Windows will get 64bit Chrome and Opera as well.

That, and no official releases of 64bit Firefox, Chrome, (Safari?) or Opera for Windows. So it's really a team effort to keep 64bit browsing off Windows.

In this case, Big Brother is invited. The monitoring software they describe seems perfectly acceptable to me. If I was vying for a freelance position where I work at home and the condition was my work would be periodically checked, I would be fine with it. As long as all the expectations and the ways the data would be collected are presented up front, it seems completely reasonable.

And having different standards in this case makes sense. This isn't monitoring full-time employees that you've rigorously hired and who will be reviewed by HR regularly and that have a real stake in keeping the position. This is for freelance, hourly workers that could be located anywhere in the world.

I'm kind of excited about what this will mean for Nintendo as a whole as well. There might be brilliant people waiting in the ranks to try their hand at his job. This will make it possible for them to step up and try it out while Miyamoto is still on staff to guide their development (or save their butts).

And this way you can do crazy things like require a person authenticate themselves before they can see the picture vs someplace like Facebook where every picture is publicly accessible.

Is the story that SQL Injection and XSS are still a problem or that Veracode just recently took a "zero tolerance" stance on SQL Injection and XSS in the applications they test?

It doesn't seem like they really suffer from including other things. The browser is good and fast. And, on my older Linux boxes where I never bother to upgrade RAM, I use the lowram option to only load the core browser functionality at startup. I don't think bundling a few helpers is really all that serious an issue.

And selling the engine for other things. Adobe used (uses?) Opera for Creative Suite. I think it powers the help system or some part of the menu system in that. I would imagine there are other similar uses that I've just never heard of.

I think it is a bit different then that since, as they mention, both diamonds are both vibrating and not vibrating simultaneously. It isn't the case that one is vibrating and the other is not vibrating and you just don't know yet because you haven't measured. They are both in both states until you measure. The entanglement means that when you measure one and collapse the superposition of simultaneously vibrating and not vibrating to determine which state it is in, the other diamond will be in the opposite state. So you are collapsing the superposition of one of the diamonds without actually measuring it.

Indeed. I got really set in my ways as far as keeping a huge inbox. Although, the more I see organizations move away from e-mail, the more I think I may be doing things wrong. I have about 20 gigs stored. My company uses Exchange and Outlook. Even with the improved searching in newer versions, it is a headache. And I believe the article when it mentions how little e-mail is actually useful. If I had the time I could probably trim at least 30% of my archive.

I apologize for not being clearer for you. I don't think of filed hard copies as e-mails. When I think of saving an e-mail, I think of it being an electronic record. I didn't think hardcopies would really be an interesting part of a conversation about e-mail retention policy since once it is printed and filed it would follow the companies policies regarding hardcopy records and not electronic records.

That's fine. I'm more interested in conversation than convincing people of something. If you work for a law firm that does things differently than the ones I've worked with I'd be interested to hear how they do it because what I've been exposed to has seemed a bit odd and fascinating to me.