Posts by Carl Fletcher 28 publicly visible posts • joined 21 Jun 2007
Well the main reason is really capacity. We are at the limit of what data can be squeezed in the bandwidth available in densely populated areas, as anyone who uses a 3G phone in central London will know. We need more bandwidth, but importantly we need to use it efficiently, and LTE is much more efficient than 3G.
Still, that's a hard sell for higher prices: "a data connection that actually works!"
It's damn embarrassing that a company like Google can continuously fail to anticipate demand and launch products to immediate sellout. We've had 3 other Nexus phones already, they know how many are going to be needed.
The website didn't work either, slow and errored, and several people i know ordered several accidentally because they didn't get any confirmation that the order succeeded. This is *Google*! They can't build a website that scales??
I did bag one though.
We need LTE because of bandwidth efficiency as much as speed, we have a finite amount of spectrum that is useful for mobiles and an ever-increasing demand. LTE is more efficient than 3G, therefore we need to use that instead.
The problem is in the radio spectrum space, not the backhaul.
The problem for Google and Android is that it's the 3rd party manufacturers need protecting, not Google themselves. So Google jointly owning patents with MS wouldn't stop what's currently happening, which is the hardware manufacturers are being sued for patent infringement.
It does commonly amuse me when people compare different technical things when they blatantly don't know what they're talking about.
Android and iPhone's *default* app behaviour is quite similar, which means that this assumption that every app is multitasking and can cause memory leaks is highly overstated. Normally, when you switch away from an Android app, it is paused (pending removal), it's state is saved and it does no more work. The *difference* is that Android also has the ability to start a long-running fully-fledged service which can do everything a frontend app can do. Most apps don't do this, so would never be able to affect the battery. You have to specifically write your app to be multitasking to have that functionality.
And no, iPhone (<4.0) *doesn't* do multitasking, no matter how you try and redefine it. It's just marginally clever with it's state-restore ability. Try playing music in Spotify and then writing a text message. The music stops.
Got to love the number of people that say that:
"Never used the site, just seemed like a complete waste of time for me"
Um... then you have no right to hold an opinion? It's not a perfect site, but it's bloody useful for some things. It's going to transition from something that's overhyped into just another tool that most people use. No big deal.
I hope the program is a hellofalot more clever than it's reported to be... I can imagine a lot of very annoyed people when it first switches off and loses the document they were working on the previous night. And what's so bad about Hibernate mode exactly? Doesn't it write to disk and switch the computer off completely anyway?
*Sigh*
The theatre business goes way beyond the big name hit shows you know. There is a massive number of smaller productions that can barely make ends meet to feed their cast and crew. I'm not necessarily saying that they require sympathy, people choose their profession and life, but also it's not necessarily a status quo you want to upset. Theatre feeds into the (much bigger and more significant) TV and film industries. For example, The League of Gentlemen started out in fringe theatre, and now they've got multiple exportable tv series and a film to their names.
Just because theatre is not necessarily hugely popular or profitable by itself doesn't mean it's not massively important. Hurt theatre and you cut off the talent supply from television...
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
