If you have to recall 300,000 cars and you have got "dozens of service stations", what impact do you think a recall would have on those service stations? I count 71 in the USA. Each one has to deal with 4,225 recalls on average. How long do you think it's going to take? How much is it going to cost? Don't forget to include parts and labour. The Tesla of today would not be able to cope with such a vast recall.
Of course, the model 3 isn't due to appear for more than two years, so Tesla has some time to expand its support network. It also does not have to "get as many Model 3s manufactured and out on the road as soon as humanly possible" [from TFS]. Just because you have 300,000 preorders for a car, it doesn't mean you need to satisfy all of the orders on day one. As long as the growth and production are carefully managed, a recall for something like a seat hinge is not going bring the company down. A recall for a faulty battery that needs replacing might, but that is probably already true today.
I think it's a really bad idea to let developers act as the admins in any environment with production systems in it. Developers tens to be really keen to get the admin stuff done quickly and get back to the exciting development work so they take short cuts which can lead to disaster.
I followed the debate about removing them on Swift-Evolution and at the time I was meh. However, I'm finding that I miss them. Maybe it's just muscle memory, however, I wish I had objected at the time.
There are a lot of breaking changes being proposed for Swift 3. While I don't think breaking changes should be banned because such a rule can stifle language development (see Java for example), I don't think the core team sets the bar high enough and I think they will get a bit of a shock at the backlash following the release of Swift 3.
I'm having difficulty believing Apple will be less possessive of it than Oracle is of Java.
Swift is already open source and while the core developer team (Apple employees) retains a firm grip on the language's direction, they have a process whereby anybody can propose new features for the language.
Half right. The content is the shit but his users live in a house with a toilet that connects to the sewer via a round pipe of a certain diameter and has done for years.
The sewer company has just sent him a letter saying they are going to change the shape of the connecting pipe to square and if Maciej's users want to keep using the toilet, they need to put a new one with a square outlet in at their own expense. Furthermore, they reserve the right to change the shape again and/or vary the dimensions at a moment's notice.
I've no idea how much money, if any, Pinboard is paying to IFTTT to use the EPI (Effluent Plumbers' Interface), but if it is $0 I have to ask why Pinboard expects anything else. "Hey, we're changing the EPI you use for free, so you'll need to change your client code. No we won't be subsidising you're dev work". If it is $>0, there should be a contract and if it doesn't specify how to deal with EPI changes, somebody's lawyer needs to be fired.
I think Mercurial is superior to git. However, the Apple Xcode tool chain doesn't support it, so I've been forced reluctantly to use git.
We also use git at work on a project where we share code with a large customer. I have to say, the much hyped merging abilities of git are actually pretty poor.
MM/DD is equivalent hours:minutes, so it makes perfect sense.
Nope.
MM/DD is equivalent to minutes:seconds MM/DD/YYYY is equivalent to minutes:seconds:hours. In fact, the example gives the lie to the "it's the same way we say it" argument because people often say "it's 25 minutes past four" and yet nobody is seriously suggesting putting minutes before hours in written times.
Ah, but they had a different calendar for each year, so the first thing to do is make sure you have the calendar for the right year, which means the year should come first.
Anyway, we are not talking about how people say dates but how they should be written down in numerical form. The best way is to put the largest unit first, then the next biggest and so on (e.g. ISO format). The second best way is to reverse the order. The way the USA does it is just insane, which is why most of the World does something different.
NB if we extend the format to include the time of day, the rest of the World is nearly as bonkers as the USA since they use one convention for the date and the opposite convention for the time. And don't get me started on where the am or pm should go if you are using the 12 hour clock.
Slashdot Mirror
If you have to recall 300,000 cars and you have got "dozens of service stations", what impact do you think a recall would have on those service stations? I count 71 in the USA. Each one has to deal with 4,225 recalls on average. How long do you think it's going to take? How much is it going to cost? Don't forget to include parts and labour. The Tesla of today would not be able to cope with such a vast recall.
Of course, the model 3 isn't due to appear for more than two years, so Tesla has some time to expand its support network. It also does not have to "get as many Model 3s manufactured and out on the road as soon as humanly possible" [from TFS]. Just because you have 300,000 preorders for a car, it doesn't mean you need to satisfy all of the orders on day one. As long as the growth and production are carefully managed, a recall for something like a seat hinge is not going bring the company down. A recall for a faulty battery that needs replacing might, but that is probably already true today.
I think it's a really bad idea to let developers act as the admins in any environment with production systems in it. Developers tens to be really keen to get the admin stuff done quickly and get back to the exciting development work so they take short cuts which can lead to disaster.
Google+ didn't take off because everybody was already on Facebook. That's the one and only reason for its failure.
How are you going to pay for the servers?
Yes, for what its worth, I think Apple has the balance about right.
It's removing four actually. x++, x--, ++x, --x
I followed the debate about removing them on Swift-Evolution and at the time I was meh. However, I'm finding that I miss them. Maybe it's just muscle memory, however, I wish I had objected at the time.
There are a lot of breaking changes being proposed for Swift 3. While I don't think breaking changes should be banned because such a rule can stifle language development (see Java for example), I don't think the core team sets the bar high enough and I think they will get a bit of a shock at the backlash following the release of Swift 3.
I'm having difficulty believing Apple will be less possessive of it than Oracle is of Java.
Swift is already open source and while the core developer team (Apple employees) retains a firm grip on the language's direction, they have a process whereby anybody can propose new features for the language.
https://github.com/apple/swift...
He never said that religion is the only realm where this occurs. He's just making a joke out of a fairly obvious example.
0 to 60 in six seconds? Is that not more?
Although, if you continually do 0-60 in six seconds, the alleged 215 mile range will probably be fiction.
And we also apologise for the environmental destruction caused by the lithium battery industry.
Nobody used Safari on Windows. It was nowhere near as good as Chrome even though (at the time) it used the same rendering engine.
Half right. The content is the shit but his users live in a house with a toilet that connects to the sewer via a round pipe of a certain diameter and has done for years.
The sewer company has just sent him a letter saying they are going to change the shape of the connecting pipe to square and if Maciej's users want to keep using the toilet, they need to put a new one with a square outlet in at their own expense. Furthermore, they reserve the right to change the shape again and/or vary the dimensions at a moment's notice.
I've no idea how much money, if any, Pinboard is paying to IFTTT to use the EPI (Effluent Plumbers' Interface), but if it is $0 I have to ask why Pinboard expects anything else. "Hey, we're changing the EPI you use for free, so you'll need to change your client code. No we won't be subsidising you're dev work". If it is $>0, there should be a contract and if it doesn't specify how to deal with EPI changes, somebody's lawyer needs to be fired.
Source Safe was the only ironically named source code control system.
I think Mercurial is superior to git. However, the Apple Xcode tool chain doesn't support it, so I've been forced reluctantly to use git.
We also use git at work on a project where we share code with a large customer. I have to say, the much hyped merging abilities of git are actually pretty poor.
I'd rather remove my testicles with a rusty hacksaw than ever use CVS again.
The main thing I took away from the video is that I get really annoyed by people pronouncing the word "gnome" with a hard G.
No it didn't work fine on PCs, it worked tolerably, which is not the same thing.
Except some are saying pi is not quite fully random
It's not random at all. I calculated the first few digits a hundred times yesterday and each time the sequence started out 3 1 4 1 5 9 2.
And perhaps to g-d it is an integer. After all she gave us an infinity of counting numbers. What was held back? Smile.
The infinity of counting numbers is too small to count all the real numbers.
MM/DD is equivalent hours:minutes, so it makes perfect sense.
Nope.
MM/DD is equivalent to minutes:seconds MM/DD/YYYY is equivalent to minutes:seconds:hours. In fact, the example gives the lie to the "it's the same way we say it" argument because people often say "it's 25 minutes past four" and yet nobody is seriously suggesting putting minutes before hours in written times.
Ah, but they had a different calendar for each year, so the first thing to do is make sure you have the calendar for the right year, which means the year should come first.
Anyway, we are not talking about how people say dates but how they should be written down in numerical form. The best way is to put the largest unit first, then the next biggest and so on (e.g. ISO format). The second best way is to reverse the order. The way the USA does it is just insane, which is why most of the World does something different.
NB if we extend the format to include the time of day, the rest of the World is nearly as bonkers as the USA since they use one convention for the date and the opposite convention for the time. And don't get me started on where the am or pm should go if you are using the 12 hour clock.
31st April? That's as fictional as 3rd Dodecember.
Since pi cannot be expressed as a fraction, we should just take the best approximation, which is 22nd July.
Unless you are gay, or you disagree with Putin on anything.
No it's one point twenty-one jiggawatts. Sheesh. (1.21 is pronounced one point two one)
I was thinking of Newtons.