use amd chips. they're a fraction of the price of intel chips, and there's really no difference in performance.

It's not just opening the source on a product, it's also ensuring that the product is not 'defective by design' (in Stallman's own words). I.e. the vendor should not restrict the ability of somebody to modify and reinstall new software on a device with an openly available build and install system. One particular aspect of 'defective by design' is the concept of e-fuses that literally burn the jtag circuits of mobile phones for production runs. Now, whether or not the end-user actually gets the chip documentation required to modify their software in a meaningful way, is another story alltogether.

Please tell me I'm not the only one who sees this.

What if someone else uses your cellular phone, or worse, someone uses your cellular phone while you aren't aware of it? That's practically like giving anyone free access to your account.

I think the facebook geniuses are confusing the one-time-pass with the one-time-pad ... particularly in this case, they are two very different things, specifically because the pad is requires that the key be exchanged *securely*.

Improve Octave. Specifically, for ARM. Remember that open-source does not necessarily mean architecture independent. Practically all software is written with the perception that the compiler optimizes any poorly written C / C++ code and that the target is a PC. While this is good for x86, relying on hardware instruction rescheduling to make code more 'efficient', it's pretty awful for anything else. Having done a lot of work with ARM / NEON optimizations myself, I can tell you first-hand that gcc does not do a great job of optimizing C code at all. This is going to become increasingly important as ARM outpaces x86, so please do everyone a favour, and write the code correctly the first time. There are several books about why this is so important, e.g. this one, but you'll probably find that its easier to just dive right in. Look at the Android source code, that's always a good example. uClibc / uClibc++ are also good examples.

&& >= 60 km/h.

lol ... oh man, Gosling's patent basically describes every digital circuit in existence, some of which existed before he was even born.

Oh wait... no, sorry. I misread the title of this article and thought that it said "Microsoft Apologizes for Page-Turn Animation Patent".

Schya... and maybe monkeys will fly out of my ass.

that's about as much time as I waste reading this website every day too!

I felt the quake in Montreal today, while working at home with my girlfriend. Although no dishes in our 3rd story apartment fell from the shelves and no structural damage to the building was immediately visible, it did serve as a good exercise about what to do in the event of a larger quake.

My girlfriend suggested that we stand in the middle of the building close to no visible exits. In spite of my immediate instinct to run down the stairs that we were directly beside, i went with her, which probably would have been a bad call, if the quake had been any larger in magnitude. In other words, if the building had collapsed we probably would have been trapped under debris.

The moral of the story is, that its sometimes a much wiser decision to exactly the opposite of what your girlfriend wants, even if it means that you won't be getting any for a few days.

Although nobody likes a rat (nobody who is ratted-out, in any case), Micron should actually get some respect for being the whistle-blower in this situation. A little honesty can really go a long way - especially if that is the way toward 400 million in, e.g. deficit-reductions.

Other examples of where Octave has much better potential than Matlab are:

1) Calling matlab-like matrix functions from another programming language.
2) Using Octave on an architecture other than x86.
3) Using Octave on mobile devices.

Thank Jobs for that!

I would probably install Linux on it.