Tesla model S & X generally gets good reviews but one issue that constantly comes out is build quality, fit and finish. Lines that don't line up, seals that don't seal etc. I was watching one review of an S last week where the reviewer said the interior quality didn't measure up to other vehicles in the same price bracket.
I'm fully expecting the same to be true for the model 3. More so because it's built to a reduced price, production is so aggressive and they won't delay even if they discover minor / cosmetic flaws. The people who are down the list will probably benefit because the flaws will be rectified in due course. The people at the front will be the ones complaining about them.
Things like volume, air con temperature, wipers, hazard lights etc. really should be physical dials, stalks & buttons. As you say there is no tactile feedback to a screen and "buttons" can be in different places depending on what mode the screen is in. It lacks the same muscle memory as a physical thing.
Maybe that's just a nuisance in a tablet or a phone, but when someone is supposed to be driving, distractions can be fatal. So it costs a few bucks to add a knob or a dial. Big deal.
I didn't say explicitly say type declarations. I'm referring to anything the compiler is remotely capable of catching that prevents a runtime error. Even the likes of Javascript, Ruby and Python have compilers that turn source code into some binary format and generate syntactical errors.
It's just that (for example) Javascript's compiler can't tell that the function / variable / field doesn't exist because those things can spring into existence at runtime. Therefore a whole raft of problems that simply don't exist in other languages can exist in Javascript.
Nor does JS care if that value is the right type, the wrong type, the right value in the wrong type (e.g. number inside a string), undefined, null or being coerced incorrectly because it has no information to go on. The reason that Typescript has caught on is because it adds a layer of additional checks and syntactic niceties that stop bad things happening to JS at runtime.
And yes some languages do have strong typing but some also have type inference. C++, Go, Swift, Rust et al. The compiler infers a type upon assignment and enforces it thereafter without cluttering the code with type declarations.
I'm also sure typing does get in the way sometimes and there is benefit to dynamic / ad hoc objects too. But not enough to argue that we should toss out strong compile time checks for the sake of those. If a language sees merit in supporting ad hoc objects it can declare an any or variant type and make allowances for it in the parser without compromising other checks.
The more you catch at compile time, the less there is to bite you on the ass at runtime. Cheaper in terms of development effort too to fix bugs before customer reports them.
Source code doesn't help unless you have a surefire way to guarantee that the binary you're running was built exactly from that source code. And if the binary has dependencies on other libraries then the same applies to them. And the compiler toolchain. And if the binary executes html content or scripts, potentially fetched from the web then even that doesn't prevent potential abuse.
"As far as I can tell", you're not thinking this through in the slightest. Apple use USB C in other produces so it isn't an excuse. Nor is USB C an excuse for why they never supported USB Micro or Mini at respective times in the past. Given that the cable is proprietary at one end and plugs into USB 1, 2 or 3 at the other, there is no technical reason for this.
The proprietary adapter is and always has been purely to maintain a stranglehold over 3rd party peripherals and to force phone owners to buy and own an assortment of dongles, adapters and leads as well as proprietary computer software to use their phone in ways that other phones support by default.
It's not about "unnecessarily changing ports". It's about unnecessarily using proprietary ports. It's purely and solely about imposing control and leverage over 3rd party peripheral makers and in turn forcing them to be proprietary.
If they're not including a charger, and I'll take your word that they're not, then the ONLY reason they're doing it is to bilk more money out of people by charging for one separately.
This is human nature 101. Put a broken feature into a car called autopilot and all it takes is for the car to screw up at a moment that the human is distracted for a catastrophic failure. Tesla even encouraged inattentiveness by allowing the human to take his/her hands off the wheel for extended periods of time. Even the modified requirements are too lax.
None of this should have come as a surprise to Tesla or anyone who thought about this for a moment. Driver boredom and inattentiveness is an obvious consequence of sitting someone behind a wheel while the car seems to do everything (except not crash into a semi). The car has to monitor and force attentiveness and if the human doesn't give it then the car needs to "punish" them by disengaging those systems.
You redistribute the winner's excess to the other candidates and if there is no outright winner then you go to #2, #3 etc on the eliminated candidate until there are none left but yes I just paraphrased incorrectly.
It's a painfully slow system to be sure. In some cases it takes all weekend to figure out who won.
Ireland has paper ballots however the nature of the voting mechanism can have a huge impact on the time taken to count votes. Basically there are two or three seats up in every constituency and voters have to list their preferred candidates in order of preference - 1, 2, 3, 4 etc. as many as they like. First all the 1 preferences get counted up and if candidates pass a % threshold then they become elected, but if they don't then all the ballots are dumped back out and then the nr 2 preference is counted, then number 3 and number 4 and number 5 etc.
It takes days sometimes to figure out who got elected which is why Ireland looked at e-voting solutions about 15 years ago. Unfortunately they ordered a bunch e-voting machines which had no paper trail and the whole lot was withdrawn and is sitting in a warehouse somewhere. E-voting machines can work but only if they print a paper ballot and there are sufficient audit checks and balances to prevent tampering and any recount is via the paper ballot.
Those added batteries are equivalent to an extra passenger in your car. Work it out for yourself. I reckon it'd be at least 8-10 miles on a full charge.
And your second point makes little practical sense since the implication is that unlocking and using that additional 15kwh battery would make the battery wear out faster.
Even if it were true once that the battery was sold "below cost", it still makes no sense to the owner. I wonder how many extra miles Tesla owners would get off a full charge if they weren't hauling around effectively the dead weight around for those crippled batteries.
Most phone operators have Android phones from €50 contract free and up. Something upwards of €100+ tends to be a day-to-day usable device. Cheaper devices tend to not have much storage on them.
The biggest problem for Android by far is that many manufacturers including Samsung and Huawei are compelled to fill their phones with crapware and replace the perfectly functional default launchers, diallers etc. with their own crappier equivalents. In some cases they even double up the normal apps with their own for no good reason. Then the mobile operators want their turn stinking up the phone by adding even more crapware.
Therefore, if I were looking for a cheap handset I'd first look for one which can be flashed with a custom firmware to remove all this garbage.
Thanks for your pointless retort idiot. Actually there is code in ReactOS that I wrote and was pulled in to that project not that it makes any difference to the point I was making.
Even Blackberry did this in the playbook and that's getting on a bit. Swipe from the edges, the screen turned into sliding set of cards and you could flip to another app or flick one away to close it.
And if all things were equal that might be a compelling selling point. But ReactOS isn't remotely close to a polished production ready system and at the pace it's going at it probably never will be.
Besides, ReactOS aims to be a drop-in replacement for Windows (circa Windows 2000/XP), so all that spyware, malware, adware and crippleware? Yup it's going to run on ReactOS just fine. It won't even have to worry about UAP, ASLR or all the rest either. For that matter, ReactOS might pose threats of its own.
Here are some clues that a movie is being made for Chinese consumption - it's apolitical, it doesn't cover subjects banned in China cinema such as supernatural/ghosts, it contains gratuitous / redundant scenes set in China or Hong Kong, it contains nonsensical Chinese product placement, extraneous Chinese actors and sympathetic Chinese representation.
An egregious example would be garbage like the Transformers series which has Chinese product placement throughout, Americas using Chinese banks for ATMs, battles set in China but it affects many blockbusters to one degree or another.
I feel cheated when I watch a bad movie. Cheated of time, opportunity, and money. So my policy these days is I'll wait for reviews. If a movie is THAT GOOD then consensus will confirm it and I will think about going. And if it isn't, then that's money / time I can use on other things.
Hollywood is lazy and formulaic and they WILL churn out shit given half a chance. The likes of Rotten Tomatoes should be used to fight against that model. Wait for reviews and be extremely wary of movie that have a) review embargoes that run all the way up to release date, and/or b) a few suspiciously glowing reviews even though there is a general release embargo. Either speak of a movie which is going to be total garbage.
Personally I think RT need to start fighting back because studios are gaming the system. e.g. Do not permit any review score, or any review link to appear until the general embargo is lifted.
Is that dealerships are allowed to remotely monitor and disable vehicles in this manner. It is anti-consumer in the extreme. If they're so terrified that people will default on payments they shouldn't be providing credit in the first place to those people.
Slashdot Mirror
I'm fully expecting the same to be true for the model 3. More so because it's built to a reduced price, production is so aggressive and they won't delay even if they discover minor / cosmetic flaws. The people who are down the list will probably benefit because the flaws will be rectified in due course. The people at the front will be the ones complaining about them.
Maybe that's just a nuisance in a tablet or a phone, but when someone is supposed to be driving, distractions can be fatal. So it costs a few bucks to add a knob or a dial. Big deal.
Futurists are never wrong (or pill popping kooks) so it's good to hear their reassuring words.
It's just that (for example) Javascript's compiler can't tell that the function / variable / field doesn't exist because those things can spring into existence at runtime. Therefore a whole raft of problems that simply don't exist in other languages can exist in Javascript.
Nor does JS care if that value is the right type, the wrong type, the right value in the wrong type (e.g. number inside a string), undefined, null or being coerced incorrectly because it has no information to go on. The reason that Typescript has caught on is because it adds a layer of additional checks and syntactic niceties that stop bad things happening to JS at runtime.
And yes some languages do have strong typing but some also have type inference. C++, Go, Swift, Rust et al. The compiler infers a type upon assignment and enforces it thereafter without cluttering the code with type declarations.
I'm also sure typing does get in the way sometimes and there is benefit to dynamic / ad hoc objects too. But not enough to argue that we should toss out strong compile time checks for the sake of those. If a language sees merit in supporting ad hoc objects it can declare an any or variant type and make allowances for it in the parser without compromising other checks.
The more you catch at compile time, the less there is to bite you on the ass at runtime. Cheaper in terms of development effort too to fix bugs before customer reports them.
Source code doesn't help unless you have a surefire way to guarantee that the binary you're running was built exactly from that source code. And if the binary has dependencies on other libraries then the same applies to them. And the compiler toolchain. And if the binary executes html content or scripts, potentially fetched from the web then even that doesn't prevent potential abuse.
The power draw required to charge one bus let alone a fleet would be insane.
The proprietary adapter is and always has been purely to maintain a stranglehold over 3rd party peripherals and to force phone owners to buy and own an assortment of dongles, adapters and leads as well as proprietary computer software to use their phone in ways that other phones support by default.
Yeah sure. Apple is so magnanimous that way.
So if I drop a stupid amount of money on a phone it can be one which packs a CPU way in excess of anything required of it. Great.
It's not about "unnecessarily changing ports". It's about unnecessarily using proprietary ports. It's purely and solely about imposing control and leverage over 3rd party peripheral makers and in turn forcing them to be proprietary.
If they're not including a charger, and I'll take your word that they're not, then the ONLY reason they're doing it is to bilk more money out of people by charging for one separately.
None of this should have come as a surprise to Tesla or anyone who thought about this for a moment. Driver boredom and inattentiveness is an obvious consequence of sitting someone behind a wheel while the car seems to do everything (except not crash into a semi). The car has to monitor and force attentiveness and if the human doesn't give it then the car needs to "punish" them by disengaging those systems.
It's a painfully slow system to be sure. In some cases it takes all weekend to figure out who won.
It takes days sometimes to figure out who got elected which is why Ireland looked at e-voting solutions about 15 years ago. Unfortunately they ordered a bunch e-voting machines which had no paper trail and the whole lot was withdrawn and is sitting in a warehouse somewhere. E-voting machines can work but only if they print a paper ballot and there are sufficient audit checks and balances to prevent tampering and any recount is via the paper ballot.
And your second point makes little practical sense since the implication is that unlocking and using that additional 15kwh battery would make the battery wear out faster.
Even if it were true once that the battery was sold "below cost", it still makes no sense to the owner. I wonder how many extra miles Tesla owners would get off a full charge if they weren't hauling around effectively the dead weight around for those crippled batteries.
The biggest problem for Android by far is that many manufacturers including Samsung and Huawei are compelled to fill their phones with crapware and replace the perfectly functional default launchers, diallers etc. with their own crappier equivalents. In some cases they even double up the normal apps with their own for no good reason. Then the mobile operators want their turn stinking up the phone by adding even more crapware.
Therefore, if I were looking for a cheap handset I'd first look for one which can be flashed with a custom firmware to remove all this garbage.
Thanks for your pointless retort idiot. Actually there is code in ReactOS that I wrote and was pulled in to that project not that it makes any difference to the point I was making.
Even Blackberry did this in the playbook and that's getting on a bit. Swipe from the edges, the screen turned into sliding set of cards and you could flip to another app or flick one away to close it.
Besides, ReactOS aims to be a drop-in replacement for Windows (circa Windows 2000/XP), so all that spyware, malware, adware and crippleware? Yup it's going to run on ReactOS just fine. It won't even have to worry about UAP, ASLR or all the rest either. For that matter, ReactOS might pose threats of its own.
An egregious example would be garbage like the Transformers series which has Chinese product placement throughout, Americas using Chinese banks for ATMs, battles set in China but it affects many blockbusters to one degree or another.
Hollywood is lazy and formulaic and they WILL churn out shit given half a chance. The likes of Rotten Tomatoes should be used to fight against that model. Wait for reviews and be extremely wary of movie that have a) review embargoes that run all the way up to release date, and/or b) a few suspiciously glowing reviews even though there is a general release embargo. Either speak of a movie which is going to be total garbage.
Personally I think RT need to start fighting back because studios are gaming the system. e.g. Do not permit any review score, or any review link to appear until the general embargo is lifted.
Uber was tracking you when you weren't riding / hailing one of their cars. Then they got found out.
Is that dealerships are allowed to remotely monitor and disable vehicles in this manner. It is anti-consumer in the extreme. If they're so terrified that people will default on payments they shouldn't be providing credit in the first place to those people.