Google?s Privacy Principles

Great video. Better principles.

?

The Danger of Understanding How Things Work

When I was 16 years old, I started programming on a Commodore 64; I was learning MOS 6510 machine code, interrupt programming and all kinds of crazy low level stuff. In the process I learned a lot of things about how operating systems work - too much for my own good. For 25 years, these learnings has hunted me, because they ruined my abilities to think in many ways. Because I actually understand what is going on one level down, it is difficult to abstract from that knowledge. It seems that because I know the computer is organized in the way it is, I tend to also think that way. When I think of a problem that I need to solve, I tend to jump straight to thinking how is this possible in terms of what I want the computer to ultimately do to solve this. Whereas this kind of thinking can be good from a performance point of view - and I have used this knowledge to that purpose at many occasions - it ruins the resulting program in terms of understandability and maintainability.

?

- Actor Thinking - Java to the Limit

The life of Page 2.0

The performance roadmap / Stoyan?s phpied.com

Firefox 3.5 introduces a wealth of new features which represent a huge step forward for developers and the introduction of important HTML5 functionality in the #2 browser.Here are some highlights:Implemention of the W3C standard Geolocation API.HTML5 audio and video tags.Downloadable fonts support.Improved CSS support, including text-shadow and moving to the standard opacity property.Native

Firefox 3.5 Release Candidate 1 is here.At the time of this posting, I was still getting Beta 4 as the download. Here are the RC1 download links:Firefox 3.5 RC1 MacFirefox 3.5 RC1 WindowsFirefox 3.5 RC1 LinuxI've been trying to run various iterations of 3.5 for some time with mixed results. The last iteration, Firefox 3.5 Preview, had issues with my places database and filled my hard drive with

http://www.google.com/intl/en/landing/chrome/beta/Seems that they've moved the tabs to the bottoom of the browser window to throw off the Safari UI team. Drawing from Safari's extraodinary tab innovation, they made it so only a 3 pixel by 3 pixel square in the top left corner is active for dragging tabs around. For the coup de grâce, completely eschewing process isolation, if a tab's process dies