Scraping the bottom of the barrel. Obama care has been a huge success, and you're still whining about a web-site that took too long to get right. A web site that was produced by private sector contractors that failed.
Well, it's possible. But if they did that they'd need to keep the existing car shipping, and it wouldn't make any sense to rebrand it, so it'd probably be a Beats type arrangement.
I suspect that rather than wanting to adopt an existing design and approach, they want to start a car design from first principles.
Big project, necessarily long time scales. But that's the nature of cars. There's no hurry, the market is not going anywhere.
You're assuming the nature of the bug. And when writing an operating system you can almost always fix the real bug, or get it fixed, not simply guard a known bug.
And you don't know you need to guard it on input unless you have a breaking test case.
The argument that it's an unlikely case to have written misses out that tests are not just random, but explore edge cases.
What makes you imagine Musk can make an electric car company from scratch and Apple can't? Musk is rich, but even so he nearly ran out of money, what with Tesla And SpaceX. He got so near to the brink at one stage he was going to have to pull out of one - but won some space contracts just in time.
As well as the design chops and the desirable brand, Apple has effectively limitless amounts of money to throw at making a car.
Yes, buying Tesla is an option, but there have been car related hires at Apple going on for some time now - if they were going to buy Tesla, you'd expect it to be before the hires.
For the car buying public it is better that they compete. There will be more innovation, quicker that way.
As far as I can see the new String type used by Swift does it right. Although when using existing Cocoa APIs it's get bridged to NSString anyway, so we're not out of the woods yet.
You guys that are talking about sanitizing the input don't understand the bug. There is absolutely nothing wrong with the input. This is not injection of escape codes. It's valid text in a different language, and changing at at input would constitute a second defect. The problem is connected to the eliding algorithm.
And in fact the argument where in the code the problem lies is not that helpful anyway. The bigger problem is that there wasn't a test case for it.
That's what I mean when I say "The hiding of scrollbars". It's not an issue for now because you can turn that off. It's just not a good direction IMHO.
Beg to differ all you like, having lived in one of those countries most of my life and another of them for a number of years, I'm not impressed.
Certainly it affects all those things. The drivers get a decent wage, the schedules and routes mean they run all day, and often all night, when purely commercial operations would not operate outside busy hours and routes, and unlike the unlicensed systems you mention, they tend to have stops with electronic countdowns to when the busses are due.
In Britain they partially "deregulated" the busses in the 1980s, and the services got worse and more expensive.
As I said, your opinion is prejudice, not reality.
That's your prejudice, not reality. Neither government, subsidy, not monopoly affects the speed of a bus. Congestion does. And dedicated lanes speed them up again.
Duh! I'm not talking about a phone call. I'm talking about an app on the passenger side, and an app on the drivers side that calculates a fare. The legal barrier is the means of calculating the fare. (phone app vs sealed, approved, serviced meter of a specific type.)
Invest in bubbles, and you ask for the consequences. I certainly hope that the utility of a city's transport system isn't dictated by such considerations.
Slashdot Mirror
The scientific method is obviously alien to you.
Exactly. An anecdote that's not even of a proper side by side test, of two phones doing the same thing is completely useless.
No indeed you can't win with anecdotes of observances against specs and independent tests.
You're no better than a global warming denier who's seen snow in march.
It's not surprising you don't understand anecdotes are not data.
Evidence was posted. So your your attitude is equally ignorant.
In other words "la la la. I'm not listening."
In both specs and independent usage tests the iPhone 6 Plus outlasts the battery of the Nexus 6.
http://www.trustedreviews.com/...
Scraping the bottom of the barrel. Obama care has been a huge success, and you're still whining about a web-site that took too long to get right. A web site that was produced by private sector contractors that failed.
and I mean actually run, not register to be woken up by certain events as on iOS
Thats why iPhone outlasts Android phones, for a given size.
Well, it's possible. But if they did that they'd need to keep the existing car shipping, and it wouldn't make any sense to rebrand it, so it'd probably be a Beats type arrangement.
I suspect that rather than wanting to adopt an existing design and approach, they want to start a car design from first principles.
Big project, necessarily long time scales. But that's the nature of cars. There's no hurry, the market is not going anywhere.
You demonstrate exactly what I'm talking about.
You're assuming the nature of the bug. And when writing an operating system you can almost always fix the real bug, or get it fixed, not simply guard a known bug.
And you don't know you need to guard it on input unless you have a breaking test case.
The argument that it's an unlikely case to have written misses out that tests are not just random, but explore edge cases.
There's nothing wrong with "infotainment" as long as it's audio. People have been listening to car radios without problems for many decades.
What makes you imagine Musk can make an electric car company from scratch and Apple can't? Musk is rich, but even so he nearly ran out of money, what with Tesla And SpaceX. He got so near to the brink at one stage he was going to have to pull out of one - but won some space contracts just in time.
As well as the design chops and the desirable brand, Apple has effectively limitless amounts of money to throw at making a car.
Yes, buying Tesla is an option, but there have been car related hires at Apple going on for some time now - if they were going to buy Tesla, you'd expect it to be before the hires.
For the car buying public it is better that they compete. There will be more innovation, quicker that way.
Maybe it's the way you speak.
As far as I can see the new String type used by Swift does it right.
Although when using existing Cocoa APIs it's get bridged to NSString anyway, so we're not out of the woods yet.
You guys that are talking about sanitizing the input don't understand the bug. There is absolutely nothing wrong with the input. This is not injection of escape codes. It's valid text in a different language, and changing at at input would constitute a second defect. The problem is connected to the eliding algorithm.
And in fact the argument where in the code the problem lies is not that helpful anyway. The bigger problem is that there wasn't a test case for it.
You're an idiot.
That's what I mean when I say "The hiding of scrollbars". It's not an issue for now because you can turn that off. It's just not a good direction IMHO.
Beg to differ all you like, having lived in one of those countries most of my life and another of them for a number of years, I'm not impressed.
Certainly it affects all those things. The drivers get a decent wage, the schedules and routes mean they run all day, and often all night, when purely commercial operations would not operate outside busy hours and routes, and unlike the unlicensed systems you mention, they tend to have stops with electronic countdowns to when the busses are due.
In Britain they partially "deregulated" the busses in the 1980s, and the services got worse and more expensive.
As I said, your opinion is prejudice, not reality.
Convenient, yes. Cheaper, depends. But don't dismiss the importance of having the price quoted before the journey - that's a BIG attraction.
I'm afraid you've committed a classic systems analysis mistake - letting your preconceived idea of a solution affect your requirements (or use cases).
Again, it's got fuck all to do with the cost of licenses. Uber uses drivers with badges where the law already allows for their technology to be used.
That's your prejudice, not reality. Neither government, subsidy, not monopoly affects the speed of a bus. Congestion does. And dedicated lanes speed them up again.
Oh, I certainly don't want to click on them. They're just useful for context. The very thin ones are fine.
Duh! I'm not talking about a phone call. I'm talking about an app on the passenger side, and an app on the drivers side that calculates a fare. The legal barrier is the means of calculating the fare. (phone app vs sealed, approved, serviced meter of a specific type.)
It's not about the USA but a country where proper public transport is much needed, and these mini-bus taxis are filling in for the lack of it.
Invest in bubbles, and you ask for the consequences. I certainly hope that the utility of a city's transport system isn't dictated by such considerations.