See http://blog.macsales.com/21641... for an example of a properly designed SSD.

kext signing is a GoodThing for security. Making the system less secure so that lazy implementors are protected isn't a good trade off.

Apple *should* have provided a better upgrade experience so that users wouldn't be surprised, or end up with unbootable systems. Users that don't want to have kext protection CAN turn it off see http://www.cindori.org/trim-en...

To me this is akin to Apple's desupport of WPS ages ago. It took everyone else a while to figure out that WPS was a major security hole (indeed, its still there for most consumers).

For those who care: https://archive.org/details/Is...

Will be interesting to see if HBO does better than the BBC ;>

A nit but faithful emulation is all about tiny details (potentially even emulating chip errata)

Nothing in the article explained the OS licensing issues. If the point is to keep critical apps running making sure it's legal isn't a nit

APL and J are useful for doing the sort of ad hoc big data analysis that R is also popular for.

The speed (or lack thereof) of your terminal isn't really the issue, its being able to think in matrix/vector transformations. A skill which is actually more important today than 40 years ago.

"...access to a mainframe system"....

Well, there is more than one kind of mainframe, and they aren't much alike. But let's assume you really mean IBM zSeries. You have several options:

1) Take a course. Many schools have IBM sponsored classes with access provided.
2) Find a copy of the "Hercules" emulate http://www.hercules-390.org/
3) Sign up for ANY university class to become a "student" and apply to IBM http://www-03.ibm.com/systems/...

Also note the growing popularity of Linux on zSeries systems, so your Linux skills can be directly applied.

Removed from modern versions of COBOL, the traditional "MOVE CORRESPONDING" was unique. Given two records with differing layouts, MOVE CORRESPONDING would shuffled the values based on the names (putting in default values where needed, or tossing aside unneeded ones).

90% of accidents (or more, depending on the study) are due to human error. So the DMV insistence on putting the humans back into the drivers seat is actually counterproductive. "there's no question when it comes down to the safety of those on the road." ... the question is are the other humans on the road more or less safe with the google vehicle operators able to override the computer?

While I'm not interested in being an early adopter of this or most automotive technologies, there are lots of questions when it comes to safety. It is a pity that government hardly ever uses science or logic in the decision making.

The "article" is just a pointer to the bugtracker entry which is good but lacks any clues as to measured performance.

LTO has been a win in commercial workflows for many years. Obviously it can be an obstacle for debugging (when entire call trees are eliminated or collapsed single stepping in the debugger is problematic) and if build times become excessive the results may not be worth the cost.

But in the end the real payoff is runtime. Without impressive speed ups for user critical to acceptability operations it is just air guitar!

Compare and contrast SysV init vs Solaris SMF. Not that systemd is SMF but there are real Enterprise class problems with the more traditional model. And systemd developers aren't the first to notice them.

I haven't looked closely enough to have an informed opinion about how good the systemd solution is, but SMF on Solaris is vastly better than the situation in older SunOS system I've dealt with over the years

If it can be employed in surgery (putting aside the current implant requirement) it would be a surgical boon (might not be so good for anesthesiologists ;>)

"dumping an expensive delivery channel"....

Aside from the $CDN potential fines, just how is email *expensive"?

Given that methane is known to have a larger immediate effect one would have thought that a multimillion dollar mission would carry more than one instrument to nail down which of the many green house gases are having the most impact ... rather than assuming the models are right and that it's the CO2

"...decide it's an error.."

No, it is an "optimizing" compiler not a "correcting" compiler. The optimizer can detect that no language defined semantic will be changed by removing the code, so it does. As others have noted, "volatile" is the fix for this particular coding / compiler blunder. However ill-defined, it is *not an error*.

As for the folks commenting that only C can run in small embedded processors that's hogwash. Huge mainframes of the early ages had smaller memory sizes and ran FORTRAN (now Fortran, but then it was all caps), COBOL, PL/I (and .8 for IBM internals), Algol and other languages. Most made entire classes of C blunders impossible, and there is no fundamental reason why we couldn't go back to safer languages for embedded programming (and good reasons why we ought to; not that I expect we shall).

The gyos add complexity, and dropping a third wheel doesn't save that much space. See Riley's classic http://www.amazon.com/Alternat... or just search for some of his existing designs.

As a previous owner of a Sparrow, I wish these guys luck. Unfortunately, I need a three seater ...my trusty (actual) motorcycle sits idle since I've too often got to worry about hauling two kids these days.

http://panko.shidler.hawaii.ed... there's academic work going back years "indicting" spreadsheets. Not that anyone pays attention... inside academic circles or outside.