throw0u1t

Sure!

If I'm completely honest I am quite happy for people to identify however they like. I have no preference or agenda whatsoever. It's not something I give a huge amount of thought to really.

It depends. If we're talking about someone's "sex" then I'd say their gentials. If we're talking about their gender then I think it could quite easily mean to be how they personally identify.

I would love to, I'm not sure we will have the Model 3 in the U.K for quite some time still. I'll give it a go when they're available and hopefully report back on a future article!

Of course, ICE powertrains have lots of moving parts, but the comparison that EV cars are simple is just not an accurate representation of EV cars.

There are fewer moving parts, I agree. The architecture itself is simpler too, I agree. But the individual components are still massively complex and expensive. High density Lithion-ion is very complex, and also requires a number of supplementary systems to manage power, heat, cooling and monitor the array.

I'd like to refute the point about brakes. A lot of it is based on the driver, not just the vehicle.

I've driven a manual all my life. I don't really enjoy automatics, and I've got to the point now where I've pretty much perfected rev matching and heel and toe so I can engine brake most of the time with minimal wear on my clutch and shock to my drive train.

To be perfectly honest, I don't think I wear my brakes any faster than if I drove an electric car. I'd love to do an experiment to see if this was the case, it sounds like as lot of fun!

However, I concede that most drivers are nowhere near as interested in the technicalities of driving and teaching learner drivers to rev match and heel and toe is probably too complex at that stage in their driving careers.

As far as I understand the current state of EVs, EVs have eliminated the engine and it's ancillaries.

However, EVs still have CV joints, differentials (dependent on the car, Tesla runs an open differential), independent suspension - all of which must be much stronger since electric motors produce far more torque than ICEs and also have the added weight penalty.

I'm concerned like this a quite a blanket statement. Are all EVs that much simpler? There are simple EV drivetrains and there are complex EV drivetrains. Not all EV drivetrains are the same.

This also applies to ICE. Most ICE drivetrains that do not have forced induction tend to be quite simple. Forced induction makes the drivetrain much more complex and puts a lot more strain on the drivetrain, and is one of the reasons why Toyota has stayed away from forced induction.

Is the drive train in a Tesla Model X P100d much simpler than that in a 1.5 NA Yaris? I'm not sure, and would love to be proved incorrect on this.

I would presume electric drive trains are quite complex.

You'd have independent electric motors on at least 2, perhaps all 4 wheels. You have to redesign entire platforms to fit batteries, ensure the batteries and the drivetrain have adequate cooling, ensure that the electric motors have a certain amount of longevity, and so on.

I don't understand why you're being downvoted, this sounds a like perfectly reasonable comment.

Toyota have traditionally built their reputation of quality by conservativly adopting new technology, especially when it comes to drivetrains.

I'm not aware of any Toyota vehicles sold in the U.K that have a turbocharger, except the Supra which shares the drivetrain, suspension, platform and some interior with the BMW Z4.

Heck, their Yaris GRMN uses the 1.8 supercharged engine that Toyota have been selling to Lotus for years.

I wonder how Toyota plan to transfer this to electric vehicles given how new the technology still is.

Does Steve need an ad to remind him that he likes the BMW 3 series? No doubt one of the first steps he took after his promotion was look up the prices, or finance offers on BMW 3 series, perhaps create a spec and then talk to his partner about it if he has o e.

The thing is if there is something I want to buy, or own at some point in my life, I don't tend to forget about it or need some reminder from a targeted ad. If it's something I really want I'll usually think about it daily.

On the other hand, there could be something that I need, and have never searched for, that I have forgotten about such as going out and buying more toilet roll.

It could slice on bytes and return a slice of bytes since the String type is a wrapper over Vec<u8>.

TIL! I'm still learning Rust so it's good to learn this now! Thanks!

One thing I don't like about Rust is how taking a slice of a string can cause a runtime panic if the start or end of the slice ends up intersecting a multi-byte UTF-8 char.

I would prefer it if this feature didn't exist at all rather than cause runtime panics.

https://play.rust-lang.org/?gist=e02ce5e9aacfee3a2b4917d5624...

I treat my phones the same, and I thought "I'll never drop this", until you do.

Both times I've dropped the phone getting in or out of the car. First time it landed face first on the garage floor and shattered the screen and the second time it landed on its side and just scratched the case a little.

Hard to know what will happen when you drop your phone.

That may be so, but the fact is that I can't buy a new 64GB iPhone 7.

The trouble with a glass back is that it can still shatter when dropped even if it has a case on it.

I don't want a 7 because it comes in either 32GB or 256GB, no 64GB or 128GB.

I don't want an 8 because I don't want a phone with a glass back.

iPhone SE was perfect. Metal all round, small, affordable, powerful.

But I don't want an iPhone 7 or an 8. And it makes no sense that Apple sell both the 7 and the 8.

Apple should make a phone like the SE which is made for the low-mid market, not just discount its old models.

What algorithm questions did they ask?

You're talking about the Drop trait?

I'm learning Rust coming from Go. It looks cool, but it also concerns me how most data structures in the stdlib use unsafe blocks to defeat the borrow checker. This is not the point of Rust, I would have thought?!

The article is a complete puff piece. There is no substance to it whatsoever.

It depends on the home. I use 2.4GHz and disable 5GHz because it causes a lot of issues.

The latest issue I have is where the phone I'm writing this on keeps switching from 2.4 to 5GHz when in the bedroom. However, when it switches from 2.4 to 5 it becomes unusuable due to the poor SNR ratio. I wish I could pin it to 2.4GHz, instead I keep having to wait for it to drop the connection and renegotiate on 2.4GHz.

You'll need to explain it more than that.

How was the Apple Airport slow? What kind of diagnostics did you do? What does the Google WiFi do different that makes it work so much better?

I know people like to hate on errors as values as in Go, but I think exceptions are worse when it comes to unexpected side effects and this is a prime example!

I spent the last year living 30 minutes walk from work in Central London.

Neither the 4 mile walk through congested, diesel-fumed London or the small, expensive flat with single glazed windows did make me happier.

I now live 30 miles outside London and take a 30 minute train to work. It is much cheaper, much more pleasant (I stand on the train most of the time) and I get to hear the birds and smell the fresh air when I wake up or go outside.