Comment Re:Shrinkage (Score 1) 60
Why should we all eventually get back to singularity?
Why should we all eventually get back to singularity?
I don't use ubuntu, but for me, my Arch setup with awesomewm lasts almost 1.5 times as long as windows. YMMV.
I think it's more likely that compiz which comes with ubuntu is the culprit here.
What the hell? SCO really was pining for the fjords?
1) Battery life lasts up to 2 days on my G1, after I upgraded the radio firmware, perhaps you should try this.
2) Headphone jack is annoying, but it's not a power jack - it's just USB, and there are numerous other phones that do this.
3) My experience with the camera has been good. My anecdotal evidence has just as much weight as your anecdotal evidence.
4) I've dropped my phone on concrete from 6 feet height and it's been *fine*, not even scratched.
5) The display is actually around the same size as the iPhone, but the clunkier design does admittedly make it feel smaller.
These days, Linux/gcc on ARM are getting alot more attention. I don't think it's fair to say linux is highly optimized for x86 anymore.
Right, so you're going to make a machine-code emitting JIT emit code that works on two different architectures without porting? wow! i'd love to see that.
UNSW's ISP is AARNet which is run by... UNSW.
I agree that Mao did help to drag China into the modern age (kicking and screaming albeit) but it was Xiaoping after Mao's death and Zhou Enlai beforehand who really set China up as a superpower.
In my opinion Xiaoping and Enlai achieved more amazing feats (against biao and jiang qing and the others in the gang of four clique no less) than Mao did.
Mao also made gigantic economic mistakes such as the great leap forward which led to the deaths of millions of chinese via starvation due to economic mismanagement and an irrational desire to buy nuclear weapons at huge costs to the chinese people.
Still, Mao's role in the original revolution, removing the corrupt kuomintang and unifying, modernising china should not be discounted.
Alternatively, simply be so *awesome* that you escape capture and destroy the entire universe.
Firstly, debian already ported most of Linux software to ARM, software availability is not an issue anyway.
Secondly, x86_64 is an extension on x86. Linux32 is just a set of 32-bit libraries compiled against a 64-bit kernel, that allows you to run 32-bit apps, using features of the processor specifically designed to do this. ARM is a completely different architecture and such an approach is simply impossible. The only way to run other x86 applications on ARM are via virtualization, which frankly would be unusably slow on a netbook.
Exactly. Debian already distributes an ARM version of their entire distribution.
Debian has a complete ARM distribution including all of those things you describe. It wouldn't be hard for Ubuntu to shift their distribution efforts to ARM. In fact, it's just changing a few lines in a shell script.
The porting to Qt isn't really necessary, recent versions of chrome have heavily abstracted the UI so switching to a different platform is a matter of changing a compile flag.
Microsoft struck a deal with a Japanese software company and ensured that Windows had perfectly localized versions available in the Japanese market. It took off rapidly and the Japanese market is still more MS dominated than most of the rest of the world.
Europe did have numerous home-grown systems but they were all gradually eclipsed by the cheap and extensible IBM PC which naturally had MS-DOS so Microsoft got a foothold.
The program is formally proven to be correct, where "correct" is defined to mean conforms exactly to the specification.
The specification may not be useful, but it does exactly what the specification says it does.
If I have a detailed specification for an entire operating environment (which this is not) and it is all formally proven to conform to said specification, then I would happily use it over something that had been used alot and didn't crash often. If it doesn't do what I want, then that means my specification was inaccurate.
I think such an application is perfectly justified, but then again I teach postgraduate students how to write haskell in haskell.
It is easier to write an incorrect program than understand a correct one.