It's even worse for the Honda CRX.
1,004 karma · joined November 6, 2012
It's even worse for the Honda CRX.
Higher the costs, more incentive (or mandatory) for users to buy insurance and also more profits to insurance companies.
https://www.boost.org/doc/libs/1_68_0/libs/iostreams/doc/cla...
This honestly depends on the tires. A lot of performance tires lose grip very gradually. Don't know what tires the Model 3 comes with, but with a good set it shouldn't be an issue.
> As a counter-example Mazda have always engineered some body-roll into the Miata / MX-5 so that it's fun and communicative in corners.
I daily drive an MX-5 and the body roll drives me nuts. If you ever drive a modded Miata or an S2000/BRZ or a Porsche Cayman it'll be very apparent how their lack of body roll gives superior driving dynamics while still being very compliant. Not saying Miata is a boat, but it's overly wallow-y for a car of that size.
> "This car is a joy to drive on Angeles Crest Highway, and I don't say that lightly. Angeles Crest is a famously demanding road that winds up into the San Gabriel Mountains north of Los Angeles. You need brakes, power and a taut, balanced chassis to do it right. The Model 3 has it all. Body roll is minimal, the brakes don't complain, the steering is gratifyingly precise, and there are gobs of instant torque on tap. Plus, the regenerative braking function means you use the actual brake pedal less often.
> "It's a new kind of fun to lift off the throttle ahead of a corner and realize you've already scrubbed enough speed without even touching the pedal. After my drive, a friend of mine asked me how the Model 3 compares to the current BMW 3 Series, and I told him I'd rather have the Tesla. He laughed. I wasn't kidding."
In an ideal world SB827 makes sense, but it was rejected. So I'm glad CA is trying something more pragmatic instead of waiting for a 'perfect' solution. Even if something similar to SB827 is passed in the future - worse case, we'll end up a bunch of rooftop solar installations. That's not so terrible.
Wow. That's very sleazy.
But, I tried working in Nim without GC and out turned out to be a bigger hassle than I expected it to be. GC was supposed to be ref counted and now they're doing memory regions? There is also a -gc:stack which I'm not sure if it works the way like in C++. Then there is the pointer free paradigm. Don't get me wrong, I'm very optimistic about Nim and would be great if it really replaces C. But I feel like it's doing too many things at once.
I personally feel like Nim dev team should stop adding new features every release and work on releasing a solid 1.0.
In the end, I came to the conclusion that it's far more productive (for me atleast) just to stick with plain C and using a 'helper' library like Apache Portable Runtime library.
I'm not sure if I understand, but almost all mainstream compilers treat 'C' as a first class citizen. Even MSVC, notorious for only supporting C89 finally caught up and now supports most of C11.
I think what replaces C should be something like Nim, which compiles to C and also has great C interop. C++ is definitely not it.