Steve Jobs is so accurate and smart. I agree with what he said, nothing is constant but change.
Panta rei...
Steve Jobs Ponders His Legacy In Never-Before-Seen 1994 Video
81–83 of 83 posts
Re: Steve Jobs Ponders His Legacy In Never-Before-Seen 1994 Video
#82Nice metaphor, but is it right? I don't think mountains ever get built by laying down layers of sediment. Sand castles, maybe, but mountains? Those need earth quakes, or at least plate tectonics. In some sense, Jobs was an earth mover who could shake up the earth and make what previously was a sandplain into maybe not a mountain but at least a hill.
If I remember the nerd facts from my junior high family vacation to Banff correctly, I think the Canadian Rockies were formed that way.
I don't think that is true. The rocks of the Canadian Rockies were made that way, and then they were raised by tectonic activity to form mountains.
http://en.wikipedia.org/wiki/Geology_of_the_Rocky_Mountains:
"The rocks making up the mountains were formed before the mountains were raised. [...] The Rocky Mountains took shape during an intense period of plate tectonic activity."
Sediment (from the Latin sedere=to sit") doesn't move up a hill to turn it into a mountain. The wind may blow it up a bit to form dunes, but there is no way it forms anything resembling a mountain. I am not a geologist, though, so educate me.
Re: Steve Jobs Ponders His Legacy In Never-Before-Seen 1994 Video
#83Earlier quoted context omitted.
Okay, I appreciate that Ritchie was a genius and that C was revolutionary and is foundational to modern computing. But seriously, C arrays not having bounds checks has probably caused more security disasters than anything else in the history of computing, with the possible exception of end-users. Was there a good reason for this, and if so, what was it?
C was introduced in 1972, that's a year before I was born (and it had been in development for a couple years prior). The first computer I programmed on ran at 1 mhz and had 64 kilobytes of RAM. Is it really so hard to see why C didn't historically have bounds checking? Bounds checking was pretty controversial in languages even as late as the early 2000s because of the runtime cost.
But FORTRAN had bounds checking, didn't it? Or is that just a modern thing?