Fortran/Watfor/Watfiv for doing actual math efficiently
Then COBOL because business contracting
Then PL/I because IBM wanted it to be (yet it never really was)
Then IBM assembly language, so that knowing LM 14,12,12(13) ; BR 14 would remain in my brain as long as it sits inside my head
RCS is a dead end technology.
Nah, I still find use for it when other version control systems are impractical. It's very lean, for one thing.
I believe Google's next messaging app, due next month is called "SourceSafe"
Thank goodness file permission masks have evolved past octal in the ensuing years. Oh, wait.
While Ming-Chi Kuo has a very good track record over the years on most things Apple, I'm not sure that gives him any inside track on predicting the behavior of Samsung customers when presented with an unprecedented situation. Unless he has sales channel data supporting this, its just a more informed estimate.
Until people actually buy their replacements, and we get sales data somehow to reflect this, we are still in the land of speculation, however well intentioned.
And the numbers may well be different for behavior after the first and second recalls (yeah, who knew we needed those sort of terms).
Hopefully someone on the Apple call next week will ask for some data from Apple about this in the context of sales in the current quarter.
Until Apple says something backed by actual data, or someone manages a survey of behavior (Verizon/ATT/etc) does, its all just guesses.
$30 for a movie in a format few people can tell the difference, across bandwidth few people have, to watch some lonely set of movies few people want to see?
How can this not be a success?
Which of course will be confused with NetCVS and FreeCVS
Let's organize this thing and take all the fun out of it.
