Probably from experience: Consistent use of stl memory classes (shared_ptr and unique_ptr) and containers (mostly std::vector) make it very hard to shoot yourself in the foot. Adhere to "Raw pointers don't transfer livetime from function to function" if you use raw pointers. These things are really easily spotted by code-review.

Well, they are moving in that direction with QML. For many apps, a native UI makes perfect sense. Not only if the UI is very demanding, but also when the UI is very simple: staying in one programming language keeps things simple.

One could consider buying a smaller car, and only renting when you need to haul something. For most pick-up truck owners, that gives a cheaper, more comfortable ride.

Indeed he didn't. The whole thread was about native vs. non-native code, where C is just an example of native code.

C++ is another example, closely related to C, with all the relevant properties. for example, you don't pay (performance) for abstractions/features you don't use. (exceptions, garbage collection, virtual function calls/inheritance)

In C++ it'd come down to a lambda function and std::swap, I don't see how that's less 'elegant'.

Does it really segfault that often, that that's part of the 'experience'. That's quite bad. Last time I tried enlightenment (486dx, with 24MB ram), at least it was fairly stable.

Just saying...

The way most pocket books are printed is at least as wastefull as an E-book. Those pocketbooks will only last a few decades at best, given the cheap paper they're made of.

Wouldn't that be cheating?

I'm not so sure if you have ever seen the Chinese way of designing; fiddle with it until it seems to work. Search for Huawei's security problems and you'll get the drift. Hardware design is really not done better.

Don't assume conspiracy if incompetence can explain it. The latter is far more likely.

Use RAII consistently, and use containers (from stl or otherwise) which have asserts() on bounds-checking. Bonus points for a tiny unit-test (which can therefore run at the end of every compilation). You'll be amazed at how stable, maintainable, easy to debug and performant your code will be.
Do the hardcore pointer handling only where the profiler tells you that it matters and there's no way java even gets close in performance

Mmm, makes sense, but I'm just wondering whether the gun-powder was really needed for the revenge-scene. Wouldn't the pressure cooker by itself have been enough ?

Just wondering thought, why would you make your own soap ?

For the current generation/standards at most some power efficiency. More processing power might allow better coding schemes, better beamforming (=less interference), smaller circuits (since less has to be done in parallel). So in the end it'll mostly come down to power efficiency. http://slashdot.org/comments.pl?sid=4025309&cid=44410675#