You can already do this on android and iphone as well with encrypted containers like Good ( http://www.good.com/ ).

The point of virtualising is that it means the OS is COMPLETELY seperate. If you want to upgrade to android 5.3.2 aka "footlong hotdog" (they ran out of dessert names), but your company is still on 4.6.1, you can. If your company image can only send packets via VPN and disallows app installation, you can still do what you want with YOUR image.

Blackberry's seperation is just at the app layer.

Only once, and it was when I fried the mobo (long story short, I ran what I thought was digital audio into the digital audio header for the motherboard... it turned out it was a 5v fan lead.)

This is in 20 years of building PCs.

I'd guess that the cost savings in having the chips integrated would have more than paid for that single motherboard replacement. In addition, I've ruined more than one AMD chip (the old thunderbird athlons) bending pins while plugging it in, which would have me ahead in spend were they 1:1 and soldered.

I agree, I've built PCs for ages and never upgraded a CPU, despite planning to.

The thing I can see this effecting, though, is diversity of price.

Right now you can spend $75-$350 on a motherboard, and $75-1000 on a processor. There are X motherboards, and Y compatible processors, for X * Y price/feature/etc points.

When USB3 came out is when I upgraded, so I got a low-to-mid spec motherboard (only cared about USB3, don't need dual video card capability etc) and then a mid-high spec processor (fastest i5 that wasn't the enthousiast factory unlocked ones).

With this change I won't have that choice. It'll be buy one of two models of this motherboard with processor A and B. OEMs won't make hundreds of combinations, and vendor's wouldn't stock them if they did.

As for your AMD systems:
-you CAN upgrade, but you haven't. He wasn't saying that you can't, but that no one winds up doing so.
-Why would you do so while still running DDR2?
-the top phenom II will run in a degraded mode due to lack of power from an AM2+ motherboard

I've always built my own PCs, and had the intention of upgrading my processor later. I've never done so. Right now I have an i5 ~3ghz system I built 14 month ago. I got the i5 with plans in a year or so to upgrade it to an i7. I haven't done so yet, nor will I likely do so, just as you haven't upgraded your Athlon64 systems.

And I've changed motherboards plenty of times and had windows reactivate, so I'm not sure what you're on about there.

They know they're doing it wrong, that's the point of the video!

Many people think that you can use deep frying as a short cut if you forgot to thaw your turkey.

People are stupid, news at 11!

People liking the things you don't like are always shills, obviously.

The ".pdf" on the end of the link didn't mark it well enough for you?

And what browsers in common use don't easily show PDFs?

Which games?

The biggest issue you'll run into is anything that was natively 16 bit (or used 16 bit libraries) if you're running 64bit.

For older dos games from the 80s/early 90s I advise virtualbox (you're already comparing to "wine" on linux).

No one is saying windows 8 is bad for gaming.

They are saying:
-They run an app store where they charge companies to post apps. Windows 8 comes with an app store which MS charges companies to post apps. This is a revenue loss for them if any companies choose the MS app store.

-The MS app store won't allow many/most of the types of apps they sell, meaning even if they wanted to "play nice" and sell games on both stores they couldn't.

-They fear that this is the beginning of an app lockdown, where ONLY "MS store" apps are allowed.

Due to all of the enhancements made to lower the memory and processor footprint of windows 8 most games will likely benchmark faster/better in windows 8 than in windows 7.

Not everyone has unlimited data plans, and not all areas have 100% coverage on the way to/from work (including tunnels/sparse areas/etc).

Old thread now, hopefully you'll take a look at your "replies" later :)

Two reasons:

1. To do ANYTHING useful in ASP (classic), you have to use an activeX object. DB calls/etc all go through activeX. The syntax for doing this is messy, and the objects don't always act the same as built in ASP functions (the same complaint PHP has), especially when they require c++ type structures like callbacks and output parameters.

Most people writing asp classic had no idea about what activeX is, how it works, and what you need to do with objects you create/etc.

2. It was very difficult to do code seperation in ASP. I never saw any full fledged templating systems, and doing even two layered coding (with a UI layer and business layer) was difficult at best. One place I worked at actually wrote their business logic in C++, called via activeX in asp, to enforce seperation. You couldn't really create your own business layer in pure asp.

ASP.NET isn't perfect (but it evolved nicely) but it fixed both of those issues.

At the time JSP was an EXCELLENT alternative. JSP gave you the same toolkit/language to write your business logic and presentation logic in while still letting you keep them seperate.

A more experienced tradesman knows the right tool for the job and doesn't attempt to halfass using the wrong one.

PHP is the right tool for getting a website up and running quickly without having to have a godo handle on programming.

PHP is the wrong tool for most other problems, and you can find your problem changing, hence many experienced developers avoid it.

When PHP was first launched, the major competitor was PERL. PHP let you have a simple html-looking file, and then put c-looking code inside of it, without crazy cgi shenanigans/templating libraries/etc. It was great for that reason, and I used it (other alternative was ASP classic... yuck). It was around RIGHT when the idea of the dynamic web was becoming popular, and so it's got a large footprint.

The software will work, you'll just need a breakout cable (which you already need anyways) which swaps the pins into the correct place for whatever interface board you'er using.

But simply detecting the RPI revision would be easy as well.

What's good about the pi:

-easy to use GPIO libraries were available day 1 (this is lacking on a LOT of the ARM SoC implementations)

-they worked pre-release with the XBMC to ensure that a "functioning" media center was available day 1

-tiny, cheap, powerful "enough" (you'll find better bang for buck, but not generally "cheaper")

-HDMI and ethernet onboard. Many don't come with either, requiring an adapter card

It's not perfect, but it is in a bit of a "sweet spot" for hobbiests who need a bit of power and a bit of easy.

You didn't buy it from the rasp pi foundation, you bought it from RS/Farnell/etc.

It's like blaming MS because your pre-ordered xbox at best buy didn't come in time while gamestop/etc still has tons.