When one is an arrogant self-absorbed prick who thinks impeeding traffic is their personally-granted-god-given right, they cause other arrogant self-absorbed pricks to follow too close, pass improperly or try and "make up time" - so collectively all such pricks create the situation for all motorists...

Unlike the 60's (when the speed limits were set) - your car won't just explode when you cross 70mph.

Since they have lights, cameras, radios, and friends with tools that can turn $1000 Z rated tires into litter... possibly more effectively then you'd wan't to risk...

So Netflix has a policy to stop side-channel sales and distribution? You mean you can't reach a new audience through Netflix and tell them to use a competing distribution channel?

When is the last time you saw a commercial for CNN on Fox News?! You havent?? - CRY FOWL!

Never under-estimate the stupidity of consumers... I mean, we will probably end up with tassimo style 3d printers that you put in a pod of plastic and end up with forks/straws etc... not because it was a good idea or that tassimo machines make better/easier/cheaper coffees then a real espresso maker... but because consumers are stupid.

Not to rain on your parade, but wit is best served dry.

Feeding the appetite for war, of course. We can't do too many things at once and a country at war with someone/something will be united instead of at war with itself.

To be fair, it seems many group Canada and the U.S. together or often just call us all "the west"

I have always been anal about not touching the bulb... and I have gone through at least 5 silverstar ultra bulbs in 5 years. After my last spare goes, I'll try some other bulb manufacturer.

Is that really the floppy driver's source code?!
Is this the display driver detection source code?!

Driver of the screen
impliment vesa if is seen
else just bitch and scream

I think what the guy means by no "huge development community" is no geeks with interest in doing it, just because. ARM is different then x86 and I would assume to make a good port on ARM, there would be a lot of specific x86 hacks that need to be revisited

And re: "massive software repository": The people who are interested in rasberry pi need to be interested in it for a particular prupose... since debian has a huge software repository, there are likely many more users who will be interested in the well established linux that fits their purpose vs the port of beos with few apps

So what I interpreted from that is there is no want to do it...
That and porting your own OS is a lot different then porting a community written OS that is made to be binary compatible with another closed source OS to another architecture.

The concept of file ownership/permissions != DRM... file ownership/permissions are supposed to be a way to stop you from getting owned - the concept and implemnentation it's a simple method of sandboxing dumb users or poorly writen applications from writing to places it should not be able to. Every modern operating system does this.

I think you miss the point that he is making, with any process/application to be able to write to any other process or application, it creates a completely untrusted environment where you cannot expect the system to be in any state when you cannot completely control it's inputs. Combine that with many alternatives available that are more secure/sane by design, there aren't many uses for it...

Sure maybe it can go in a stand alone video editor... but why would you when you can put linux on that same machine and connect it to the internet/render farm and not have to worry about it getting pwned in a javascript buffer overflow

In the 90's (with the exception of monochrome displays) I don't think your monitor ever cared about the colour depth vs. resolution. It was your graphics card that cared. Your graphics card only had a limited amount of memory so maybe it could not store 24bits of colour information*786432 pixels changing/refreshing 60+ times a second. Your monitor cared only about how fast and accurately it could scan horizontally and vertically across it's shadow mask. Your monitor would have only certain clocks it could lock onto (modes) where it could excite the right red, green and blue phosphorus dots and a certain power of the electron gun(meaning cheap displays would get darker at high resolutions, or you had to modify the brightness dial when changing resolutions) - but the monitor itself could always display 24-bit colour if it could display any 256 colours. Even in 256 colour mode, many applications took advantage of modifying the colour pallet (when supported by the graphics driver) to reproduce any single colour multiple times. Applications would also use dithering to reproduce colors beyond the 256 colour or 16-bit pallet (which was most effective at high resolution). The monitors, being analog, did not care about the colour depth - they just had an analog electron gun that would excite from dark to full bright... sure, some had poor gammut or contrast... but they would still produce the picture regardless of your display mode at the resolutions it supported.

Ha, you think app stores are about saving bandwidth and they will be replaced by HTML5? What kool-aid have you been into? :)

Yeah you and me both. I owned everything from the 8-bit sound blaster (that had the proprietary CDROM interface) to the high end Audigies but that all went to shit with the SB Live and Audigy

I actually thought about giving Creative one more try and bought an Audigy 2 ZS, but it and it's drivers sucked. I traded it in (paid a hefty restocking fee) and paid extra the Asus Xonar STX.

They HAD me as a loyal customer, but now I own nothing of theirs.

Surely you jest - every motherboad I had from that era I have replaced capacitors on, then binned because it was still too slow.