In the ballpark of $4000 down (inc CA sales tax, vehicle registration, first payment etc), and $120 a month (inc CA sales tax).

Things I've observed in the short term:
  For the most part it feels just like any other golf.
  When you're driving around with not many people around you, it's eerily quiet.
  On the front of quietness - people don't notice you. Expect people to step out in front of you in supermarket car parks.
  Range really suffers going up a hill - on the plus side, you get it all back as you go back down the hill.
  Range seems to be roughly as advertised (if not a little more).
  Charging seems to be substantially slower than advertised, but that's okay, it has basically a whole day to charge at the weekend.

It does? The UK doesn't have a "don't jaywalk" rule, and there don't seem to be any adverse effects.

The problem with "SMT on top" of their current design is that their current design is SMT. They're just marketing it as true 8 cores, not SMT.

The current piledriver design doesn't have 8 separate floating point units, or 8 separate instruction decode units. It has 4 of each. They just have 8 ALUs - 2 to each decode unit. It's ALU/ALU SMT, when Intel has ALU/FP SMT.

There's one other - VW. The eGolf looks basically exactly like a normal golf (with the exception of the front grill being filled in to aid aerodynamics).

And yes, this is exactly the reason that I just leased a new eGolf, and not any of the other electric options.

As someone who arranged the lease on a VW eGolf today, 100 or 200 miles is plenty. As a commuter vehicle that's all you need.

That said, I did still lease it, because 1) the battery will probably be getting crappy in 3 years, and 2) the tech will be *oh so much* better in 3 years time (heck, hopefully I'll be able to lease a model 3 by then).

The i7 4790k is faster than any CPU AMD make, by quite a wide margin. They're trying to sell this as the ultimate graphics crunching box... That needs a faster CPU than they can produce.

No, fuck yeh engineering!

To be fair, the shuttle *does* have rocket motors that propel it. Ofc, it's still incomplete, it lacks the fuel tanks, and enough motors to get it to orbit on its own.

Why is it that slashdot seems to be incapable of seeing the difference between something being in SciFi books, and something being actually designed and implemented by engineers?

Now look up how the two are processed by your body, and alcohol's affect on your blood sugar levels, then reconsider your statement in the context of an article on how substances affect your body.

No, alcohol is basically just sugar too... They have protein, and starches to fall back on... So basically, this leads to the same advice as they've been giving for a good long while. A reasonable amount of meat and fish, preferably white meat, and lots of salads, leafy greens, and veg...

American troll is American. The UK doesn't have a social security number (There's a similar concept, but it's called a National Insurance Number).

In practice, single desktop class machines with 6000+ concurrent users are not typical use cases. Instead, high performance applications are likely to look more like 3D rendering engines.

In practice, when you have 16ms to produce a frame, it really matters that the garbage collector doesn't kick in for 2ms once every second, because that'll push you past your frame window and lead to stuttering and dropped frames.

In practice, it really matters that you can structure your code to make sure no allocations are happening during certain critical operations, because an allocation will potentially need a new page, and the kernel barrier and/or hit locks resulting again, in 1-2ms of unexpected delay, and a dropped frame.

In practice, it really matters too that you have enough control over memory layout to guarantee that certain structures are all going to end up in cache at the same time, and that you're not going to be doing a bunch of pointer indirection fetching memory during time critical rendering code.

In practice, modern garbage collection doesn't allow you to solve any of these problems. That is why real time rendering engines are still written in C++, and will continue to be, and why everyone writing them will continue to be glad that C++ is not garbage collected.

Lack of garbage collection is one of many reasons why C++ produces fast code. The entire point of using C++ is that you want to have control over how, when and where things are allocated and deallocated.