Nope. I'm only tangentially aware of this issue because this second analysis came out this last week and has been making the rounds.

I wouldn't be so sure that programming wasn't the source of the problem. There's been a lot of work to understand the ECU on the Camry and it is beginning to look like some severe bugs lurk within: http://www.viva64.com/en/a/0083/

If you're only looking at some data, you're probably not very good at turning data into information.

comment to undo mod

Is this the fault of the technology, as the premise of this article claims?

And I learned all that on an old Intel 80386 long before touching my first microcontroller. Beyond that, 80386 architecture supports virtual memory, something the developer should be keenly aware of and isn't available on microcontrollers.

You mean like the backup generators that failed during the tsunami, and subsequent meltdown that was caused by the failure?

Then you're likely a waste of time and detriment to your team.

I have had conversations with some of my friends who work on the peta-scale clusters and thought much the same as you. But, it turns out, when you're working with that level of system, you're probably addressing some small part of a much, much larger problem that has been largely solved. The existing code that performs 99.9% of your task is written in Fortran and actively developed by a very successful team of researchers. Attempting to rewrite the working, debugged, code so you can work in your favorite language today is not only impossible, but would likely get you removed from the team.

Compilers often cannot make optimizations in C/C++ and similar languages because of how flexible the languages are to the user's needs. Fortran, on the other hand, is more restrictive and the compiler can make guarantees about aliasing and alignment that permit things like autovectorization. This really is a part of the core language, not just the result of monumental resources put at the issue.

I'm not 100% sure on that. Languages like Go have brought in a lot of the same things, like language-level concurrency. However, Fortran has really been designed to address the problems that are solved on supercomputers first and general language second. This makes it far easier to focus on the task at hand instead of working around limitations in the language.

It's still true. Fortran uses these intrinsics as well, furthermore the way Fortran handles variables is stronger than C/C++, which permits the compiler to perform more aggressive optimizations. Fortran also has convenient syntax for performing common mathematical operations on datasets. Yes, you can replicate this in C++ with operator overloading, but Fortran puts this in at the core language permitting the compiler writers to target these specific operations for optimization.

Lots of existing code is in Fortran and is easiest interfaced in Fortran. In addition Fortran 2008 included things like concurrency in the language that C++ only got in 2011 as a part of the standard library.

The theme of this project is more about "my language (C++) the one true language" than reality.

Thin clients did happen, but they didn't catch on. In fact, one of the main Xorg developers, Keith Packard, worked on some in the 80s. Sun Microsystems created the SunRay product line that provided a thin client environment to their SunOS/Solaris and Linux platforms, although the protocol was proprietary and not X, likely due to the same reasons Wayland was created. On a side note, Keith's presentations on why X sucks are some of the best and worth viewing to understand why Wayland is so important.

When I was using a thin client, it was a great experience when you used a very simple environment and no animation, such as an XTerm in TWM. The experience quickly deteriorated when you tried to do many on screen changes and lots of interactivity, which is common for people simply surfing the web on most pages such as facebook. This was compounded when you had some 16 clients on a single host server.

When does the NSA go to court? Their job is intelligence, with some direction and restraint, not to bring people to justice. The problem is that there is no penalty for choosing their own direction and violating their restraints.

Next time someone says they were "burned" by something, I expect to a photo of the entire person converted to ashes. Seriously.

That's worth a mod point.... if I had one.