US network companies don't want a phone that won't break, and work too well. Customers won't pay for new phones so often.
I'm pretty sure the carriers would be just fine if you didn't keep replacing your phone subsidised out of their pockets. They make a profit on the service, not the handset.
And, Windows 8 tablets will have the advantage of being able to run standard Windows programs if they want to (.NET apps should work even without recompiling).
Really? Even if the tablet is ARM based?
Yes. ARM based Windows 8 tablets should be able to run.NET applications without modification and native applications shouldn't need much more than a recompile.
So if you're an existing Windows developer, moving to Windows Phone 7 is piece of cake.
And if you're an existing Java developer, moving to Android is a piece of cake.
And if you're a competent developer, moving to any modern platform is a piece of cake.
Have you noticed that even Apple, the company which is most of the heavy lifting on developing LLVM/Clang and OpenCL, isn't switching to AMD CPUs? What does that tell you about what they feel about the importance of CPU performance, even when they have the best shipping OpenCL software stack in existence?
It tells me that AMD are having manufacturing issues and can't make the volumes required for Apple's demand. Or at least that's one possible explanation.
Crossfire generally doesn't scale well enough to make 3 way crossfire worthwhile when you have 2 mid-high end cards and one slower GPU. Also, the fastest discrete GPU that supports the hybrid crossfire right now is the 6670 I believe.
The difference is that this is a playable game with a positive PR spin, whereas I assume the fakes that RIAA et al use are just blobs of pseudorandom data.
Or following your own logic, Motorola is going to drop support for any non-Android phone any day now, which means it's a perfectly stable Android company.
That one is believable since Google is buying Motorola's phone division.
i really doubt you'd be able to recompile a c++ app targeted at winforms on x86 to run on arm
Considering winforms is a.NET technology, I wouldn't expect a native C++ application to use it. A few years ago I was working on an application that had native Win32 and WinCE ARM builds, and there wasn't too much difficulty in producing separate builds from the same codebase - most of the difficulty was in slightly differing APIs. A native ARM Windows 8 should have the same APIs as the x86 one so a recompile should mostly be enough, as long as no endianness issues come into play.
I'd forgotten all about TelstraClear cable. When I moved from NZ to Australia a couple years ago (yes, I'm one of those traitors) I had been using naked ADSL through Xnet - you don't need to pay the landline charges but it's not that much cheaper.
Slashdot Mirror
In what way does one benefit from owning a stock if that stock doesn't increase in value?
Dividends. I thought that had been covered already in this thread.
In fact, most people I know never use more than 30 GB total unless they have (a) an insane amount of music or (b) a reasonable amount of videos.
Or more than 2 modern AAA video games installed.
Or "penisland"
US network companies don't want a phone that won't break, and work too well. Customers won't pay for new phones so often.
I'm pretty sure the carriers would be just fine if you didn't keep replacing your phone subsidised out of their pockets. They make a profit on the service, not the handset.
Do you have a source for your claim that ARM will only support Metro? The developer preview SDK has ARM libraries for a fair chunk of the Win32 APIs.
Darwin is.
And, Windows 8 tablets will have the advantage of being able to run standard Windows programs if they want to (.NET apps should work even without recompiling).
Really? Even if the tablet is ARM based?
Yes. ARM based Windows 8 tablets should be able to run .NET applications without modification and native applications shouldn't need much more than a recompile.
So if you're an existing Windows developer, moving to Windows Phone 7 is piece of cake.
And if you're an existing Java developer, moving to Android is a piece of cake.
And if you're a competent developer, moving to any modern platform is a piece of cake.
Huh? The AMD Bulldozer chip doesn't do any graphics by itself. This isn't one of their APUs.
Have you noticed that even Apple, the company which is most of the heavy lifting on developing LLVM/Clang and OpenCL, isn't switching to AMD CPUs? What does that tell you about what they feel about the importance of CPU performance, even when they have the best shipping OpenCL software stack in existence?
It tells me that AMD are having manufacturing issues and can't make the volumes required for Apple's demand. Or at least that's one possible explanation.
They already have "Mall Cop"
You'd make them learn Java, PHP and Ruby. Java is on fire right now, for example.
<bad_joke>Only because Oracle keeps trying to kill Java with fire.</bad_joke>
If you had a broken clock, it would still be right twice a day.
Assuming it's not a digital clock...
None of Microsoft's own products are written in .NET.
Visual Studio is.
Crossfire generally doesn't scale well enough to make 3 way crossfire worthwhile when you have 2 mid-high end cards and one slower GPU. Also, the fastest discrete GPU that supports the hybrid crossfire right now is the 6670 I believe.
PS: I'm a Llano owner (A4-3400).
Then the applet has normal user privileges and the attacker wants to escalate to root. This is a way to escalate...
You can even compile multiple targets at the same time and include them all in the same .apk file in the same fashion as Apples Universal Binaries.
The difference is that this is a playable game with a positive PR spin, whereas I assume the fakes that RIAA et al use are just blobs of pseudorandom data.
With an x86 port of Android, it won't need to be emulated on x86 platforms - it could just run it in a sandbox.
I guess in a very loose way it's kind of based on Gentoo (using ebuilds), but it's more of a from-scratch kind of thing.
I take it you haven't heard of the Android NDK. You can compile native code - not everything has to run in the virtual machine environment.
Or following your own logic, Motorola is going to drop support for any non-Android phone any day now, which means it's a perfectly stable Android company.
That one is believable since Google is buying Motorola's phone division.
i really doubt you'd be able to recompile a c++ app targeted at winforms on x86 to run on arm
Considering winforms is a .NET technology, I wouldn't expect a native C++ application to use it. A few years ago I was working on an application that had native Win32 and WinCE ARM builds, and there wasn't too much difficulty in producing separate builds from the same codebase - most of the difficulty was in slightly differing APIs. A native ARM Windows 8 should have the same APIs as the x86 one so a recompile should mostly be enough, as long as no endianness issues come into play.
Windows 8 hasn't been confirmed as the final release name.
Oh wait, there is no personal replicator? I guess then the analogy is flawed....
I'm pretty sure the keys are single use, so the "it's not stealing because it's only a copy" style argument doesn't work in this case.
I'd forgotten all about TelstraClear cable. When I moved from NZ to Australia a couple years ago (yes, I'm one of those traitors) I had been using naked ADSL through Xnet - you don't need to pay the landline charges but it's not that much cheaper.