What other ones are as thin as the new iPhones, flat (because having a curve like the HTC one is better engineering as it gives added strength) and made of aluminium?
It's funny you should mention the HTC One. Consumer reports did proper scientific stress testing of a number of phones inluding both iPhone 6s and the HTC One. ANd both the iPhones outperformed the HTC One.
Would you have the decency to admit you were taken in by a myth, or are you going to go quiet now?
"All the phones we tested showed themselves to be pretty tough. The iPhone 6 Plus, the more robust of the new iPhones in our testing, started to deform when we reached 90 pounds of force, and came apart with 110 pounds of force. With those numbers, it slightly outperformed the HTC One (which is largely regarded as a sturdy, solid phone), as well as the smaller iPhone 6, yet underperformed some other smart phones." http://www.consumerreports.org...
It also cannot challenge C for several reasons, including the fact that it's very slow at working with native types such as integers because it tries too hard to be safe.
What a stupid thing to say.
First of all because you are repeating things you heard whilst Swift was in beta. It got a lot faster. Comments were made based on non-optimised compilations.
Secondly, for most purposes being correct is far more important than being faster. We've had decades of experience of the bugs and security vulnerabilities that Cs unchecked nature gives.
Thirdly if you don't want the checks you just switch them off in the compiler options. The norm of course being to have more checks in debug builds than release builds.
And Fourthly, having a way to express more invariants to a compiler, such as whether or not a pointer can be nil, results in FASTER code because better optimisations can be done. e.g. For correct C code you very often need to write manual checks on whether a supplied pointer is nil. In Swift this is not normally necessary for the programmer nor the compiler to do.
If you have a link to some benchmarks of the released version of Swift vs C, with appropriate optimisations, then we can see if there's any truth in it for v1.0 of Swift. And even then we don't know how much faster Swift will get in future releases. It certainly isn't impossible for it to be faster than C. Your assumption is wrong.
I'd bet the majority of budding iOS developers start their first project using Interface Builder. It works pretty well if you don't stray too far from the Apple "look". But once you want to do something novel, you start spending more and more time working around IB than with it.
That's much less true with XCode 6. On the one hand it's now very easy to incorporate your own custom controls in IB, such that you can actually see what you're going to get. And on the other hand dealing with constraints and size classes in code rather than IB is no fun at all.
And god forbid you want to collaborate with other developers via version control. Having to manually 3-way merge a couple thousand lines of XML causes IB to quickly lose its shine...
Yes,that's definitely one to avoid. Perhaps better to stick with xibs rather than storyboards when an app is being worked on by a team. Shouldn't be too difficult to arrange to only have a single coder working on a particular view at a time. (In closed source environments.)
Interface Builder generates a bunch of boilerplate obj-c code for you.
You know not what you speak of.
Interface Builder doesn't generate any Obj-C code. Interface builder creates XML.XIB files which are compiled into object stores with a.NIB extension. Those objects are Obj-C runtime objects. But there is no boilerplate code that creates them. The application simply asks for a nib file and all the objects within it are created.
As such Obj-C exposes LESS of the "plumbing of the GUI" than the languages you mention whose visual designers DO generate boilerplate code.
"Look, all you need to do is get an Android phone from HTC for it's curved back. Then get an Android phone from Sony because their cameras are so good. Then get a Galaxy Note from Samsung for the largest screen. Then get a Nexus from Google to get a decent software experience. Finally, get a phone from Hauwei because theyâ(TM)re cheap. Then mash them all together and youâ(TM)ve got one phone thatâ(TM)s better than the iPhone!
"Thatâ(TM)ll work, right? Well, unless you mash them all together and get the worst of each one. Just mash carefully."
The audio part is inexplicable. I can see the concern for whether a valet takes the car for a joy-ride, or whether they did actually polish the cup holder. But what he/she talks about is entirely irrelevant to the job. It can only be peeping tom levels of nosiness for the owner to even have any curiosity about it.
What I want is a camera that starts recording the exterior if your car gets bumped in a parking lot and the alarm is set.
Perhaps RMS's one worthwhile point is that the complete OS should be called GNU/Linux. Thus removing the (sometimes cherry-picking) distinction between the kernel alone and the rest that usually bundled to make a complete OS.
Well if we also have examples of the 5S being bent, and yet it hasn't proven to be a significant problem over the year, there is no reason to assume this one is.
ANY phone will either bent or break. It simply depends on how much stress you put on it.
The 5C is only a year old, not 2. And there's a financial compensation for that year - a significant price reduction. It's now free with a contract.
-If an Android manufacturer has this issue with a model of their phone then users can just choose a different Android manufacturer or model.
It appears to only have happened to iPhone 6 Plus phones. So there's still the choice of iPhone 6, 5S and 5C if you want to avoid the problem. The 6 Plus was probably not the best choice for anyone who keeps their phone in their jeans pocket. Better for cargo pants or a a purse.
Your name is one of the elements where they track you across the internet, building an ever bigger picture. For sure your real name doesn't identify you, but put it together with a few more attributes, and it becomes pretty good as a unique ID. Classic big data technique.
THIS is why Google wanted your real name. It had nothing to do with cyber bullying.
Samsung phones don't get the same news coverage that Apple phones do. A new iPhone and any surrounding issues make it onto mainstream news sites and chat shows.
All large, thin phones bend. A plastic one is more likely to bend back than an aluminium one. But it depends also on the internals and how flexible or brittle they are.
Some people have bent their iPhones, some people have bent their keys. Looking at the video of someone bending an iPhone 6 Plus deliberately in their hands, the pressure needed is about the same as it would take to bend a key.
I'd actually say there are very few people who've never bent a key. It doesn't happen often but it does happen. And it's a precursor to the key snapping in the lock, which plenty of people have also experienced.
You can make excuses all you like - other models and manufacturers DO NOT have this problem, to anywhere near the same extent.
You don't know what the extent is. You just have a small number of examples, and this being Apple anything that happens is news. Other phones do bend, and if they don't bend, they break.
The summary mentions locks and keys as also being hackable. Also combination locks, face recognition, mag stripes, signatures, DRM, many forms of encryption, passwords, captchas, PINs, ATMs Online banking, credit cards. In fact there is precious little security that isn't hackable.
Of course this isn't going to stop people here ragging on TouchID.
If you watched the video on your own link, you'd know that the person did it with an already broken phone, and did it in the knowledge that he may well break the microwave as well. This was not someone who fell for the prank. There is no sign of anyone that really fell for it.
The gullible people are the ones who believe the story that people fell for it.
Dumb phones last a week or more, smartphones last about a day. That's expectation. When they become more energy efficient, the manufacturer's use that to make them thinner in preference to extending the battery life much.
For suer if you don't feel the need for mobile apps or web browsing, there's something to be said for dumb phones. HOWEVER, the Nokia 2610 is one of the worst phones ever made. It has a tinted plastic cover over the screen that is so dark it's virtually impossible to see the screen whilst you are outdoors. If you're going to make the case for dumb phones don't make it with an 8 year old phone that's one of the worst ever made. Go to a phone store and replace it with a $10 pre-paid and you've got a better phone.
Indeed. Also, with analyst reports the first question should always be, who paid the analyst. This analyst has much of the traditional automobile industry as customers. But not Tesla. Telling customers what they want to hear is good business for analysts.
Slashdot Mirror
What other ones are as thin as the new iPhones, flat (because having a curve like the HTC one is better engineering as it gives added strength) and made of aluminium?
It's funny you should mention the HTC One. Consumer reports did proper scientific stress testing of a number of phones inluding both iPhone 6s and the HTC One. ANd both the iPhones outperformed the HTC One.
Would you have the decency to admit you were taken in by a myth, or are you going to go quiet now?
"All the phones we tested showed themselves to be pretty tough. The iPhone 6 Plus, the more robust of the new iPhones in our testing, started to deform when we reached 90 pounds of force, and came apart with 110 pounds of force. With those numbers, it slightly outperformed the HTC One (which is largely regarded as a sturdy, solid phone), as well as the smaller iPhone 6, yet underperformed some other smart phones."
http://www.consumerreports.org...
It also cannot challenge C for several reasons, including the fact that it's very slow at working with native types such as integers because it tries too hard to be safe.
What a stupid thing to say.
First of all because you are repeating things you heard whilst Swift was in beta. It got a lot faster. Comments were made based on non-optimised compilations.
Secondly, for most purposes being correct is far more important than being faster. We've had decades of experience of the bugs and security vulnerabilities that Cs unchecked nature gives.
Thirdly if you don't want the checks you just switch them off in the compiler options. The norm of course being to have more checks in debug builds than release builds.
And Fourthly, having a way to express more invariants to a compiler, such as whether or not a pointer can be nil, results in FASTER code because better optimisations can be done. e.g. For correct C code you very often need to write manual checks on whether a supplied pointer is nil. In Swift this is not normally necessary for the programmer nor the compiler to do.
If you have a link to some benchmarks of the released version of Swift vs C, with appropriate optimisations, then we can see if there's any truth in it for v1.0 of Swift. And even then we don't know how much faster Swift will get in future releases. It certainly isn't impossible for it to be faster than C. Your assumption is wrong.
I'd bet the majority of budding iOS developers start their first project using Interface Builder. It works pretty well if you don't stray too far from the Apple "look". But once you want to do something novel, you start spending more and more time working around IB than with it.
That's much less true with XCode 6. On the one hand it's now very easy to incorporate your own custom controls in IB, such that you can actually see what you're going to get. And on the other hand dealing with constraints and size classes in code rather than IB is no fun at all.
And god forbid you want to collaborate with other developers via version control. Having to manually 3-way merge a couple thousand lines of XML causes IB to quickly lose its shine...
Yes,that's definitely one to avoid. Perhaps better to stick with xibs rather than storyboards when an app is being worked on by a team. Shouldn't be too difficult to arrange to only have a single coder working on a particular view at a time. (In closed source environments.)
Interface Builder generates a bunch of boilerplate obj-c code for you.
You know not what you speak of.
Interface Builder doesn't generate any Obj-C code. Interface builder creates XML .XIB files which are compiled into object stores with a .NIB extension. Those objects are Obj-C runtime objects. But there is no boilerplate code that creates them. The application simply asks for a nib file and all the objects within it are created.
As such Obj-C exposes LESS of the "plumbing of the GUI" than the languages you mention whose visual designers DO generate boilerplate code.
"Look, all you need to do is get an Android phone from HTC for it's curved back. Then get an Android phone from Sony because their cameras are so good. Then get a Galaxy Note from Samsung for the largest screen. Then get a Nexus from Google to get a decent software experience. Finally, get a phone from Hauwei because theyâ(TM)re cheap. Then mash them all together and youâ(TM)ve got one phone thatâ(TM)s better than the iPhone!
"Thatâ(TM)ll work, right? Well, unless you mash them all together and get the worst of each one. Just mash carefully."
Nope, wrong. It's your house. You can put all the cameras you want inside of it. There are no restrictions.
Absolutely false. Laws vary by juridiction but there are few places where you can spy on people with cameras in your own bathroom for example.
http://www.safetybasement.com/...
The audio part is inexplicable. I can see the concern for whether a valet takes the car for a joy-ride, or whether they did actually polish the cup holder. But what he/she talks about is entirely irrelevant to the job. It can only be peeping tom levels of nosiness for the owner to even have any curiosity about it.
What I want is a camera that starts recording the exterior if your car gets bumped in a parking lot and the alarm is set.
Already exists. Though you'd need a few angles to cover all the places you might get bumped.
https://www.youtube.com/watch?...
Except the new ones are much larger and significantly thinner, obviously making the possibility of deformation far more likely.
An observation that applies to all "phablets".
The hardware is from the 5, which is 3 years old.
Same mistake. The iPhone 5 is 2 years old.
Perhaps RMS's one worthwhile point is that the complete OS should be called GNU/Linux. Thus removing the (sometimes cherry-picking) distinction between the kernel alone and the rest that usually bundled to make a complete OS.
"Preempting..."
Is that like admitting you're making a strawman argument before you've actually made it?
So what you're saying is they've been using the excuse "You're holding it wrong" for 20 years?
Versions affected go all the way back to BASH 1.14.0
which dates from 1994. So that's 20 years.
http://web.nvd.nist.gov/view/v...
The "With many eyes all bugs are shallow" myth is busted again.
Well if we also have examples of the 5S being bent, and yet it hasn't proven to be a significant problem over the year, there is no reason to assume this one is.
ANY phone will either bent or break. It simply depends on how much stress you put on it.
The 5C is only a year old, not 2. And there's a financial compensation for that year - a significant price reduction. It's now free with a contract.
-If an Android manufacturer has this issue with a model of their phone then users can just choose a different Android manufacturer or model.
It appears to only have happened to iPhone 6 Plus phones. So there's still the choice of iPhone 6, 5S and 5C if you want to avoid the problem. The 6 Plus was probably not the best choice for anyone who keeps their phone in their jeans pocket. Better for cargo pants or a a purse.
Your name is one of the elements where they track you across the internet, building an ever bigger picture. For sure your real name doesn't identify you, but put it together with a few more attributes, and it becomes pretty good as a unique ID. Classic big data technique.
THIS is why Google wanted your real name. It had nothing to do with cyber bullying.
Jony Ive always designs using Aluminium rather than Aluminum.
Samsung phones don't get the same news coverage that Apple phones do. A new iPhone and any surrounding issues make it onto mainstream news sites and chat shows.
All large, thin phones bend. A plastic one is more likely to bend back than an aluminium one. But it depends also on the internals and how flexible or brittle they are.
P.S. My keys are metal. They don't bend.
Some people have bent their iPhones, some people have bent their keys. Looking at the video of someone bending an iPhone 6 Plus deliberately in their hands, the pressure needed is about the same as it would take to bend a key.
I'd actually say there are very few people who've never bent a key. It doesn't happen often but it does happen. And it's a precursor to the key snapping in the lock, which plenty of people have also experienced.
You can make excuses all you like - other models and manufacturers DO NOT have this problem, to anywhere near the same extent.
You don't know what the extent is. You just have a small number of examples, and this being Apple anything that happens is news. Other phones do bend, and if they don't bend, they break.
http://www.cultofmac.com/29740...
The summary mentions locks and keys as also being hackable. Also combination locks, face recognition, mag stripes, signatures, DRM, many forms of encryption, passwords, captchas, PINs, ATMs Online banking, credit cards. In fact there is precious little security that isn't hackable.
Of course this isn't going to stop people here ragging on TouchID.
If you watched the video on your own link, you'd know that the person did it with an already broken phone, and did it in the knowledge that he may well break the microwave as well. This was not someone who fell for the prank. There is no sign of anyone that really fell for it.
The gullible people are the ones who believe the story that people fell for it.
Ironically, you're the one who's blindly believing something you read on the internet.
Dumb phones last a week or more, smartphones last about a day. That's expectation. When they become more energy efficient, the manufacturer's use that to make them thinner in preference to extending the battery life much.
For suer if you don't feel the need for mobile apps or web browsing, there's something to be said for dumb phones. HOWEVER, the Nokia 2610 is one of the worst phones ever made. It has a tinted plastic cover over the screen that is so dark it's virtually impossible to see the screen whilst you are outdoors. If you're going to make the case for dumb phones don't make it with an 8 year old phone that's one of the worst ever made. Go to a phone store and replace it with a $10 pre-paid and you've got a better phone.
Also the largest distiller of Vodka and brewer of Irish Stout. And they're all the same company. So much for national drinks.
Rather that than being run by nazis.
Indeed. Also, with analyst reports the first question should always be, who paid the analyst. This analyst has much of the traditional automobile industry as customers. But not Tesla. Telling customers what they want to hear is good business for analysts.