krevis
Couldn't be farther from the truth. Apple's development process revolves around their bug tracker, to an extent that I haven't seen anywhere else. If it isn't in Radar, it didn't happen.
Yes, must be him all right.
Except: you can't. Try to find out how much a major medical procedure will cost you -- if you can find anyone who gives you any numbers at all, you'll be lucky if that's what you actually get charged. (And then try to find out how much your insurance, if you have any, will pay for! And then try to complain when the final bill is different!)
c.f. the "Important" box in http://developer.apple.com/library/mac/#qa/qa1490/_index.htm...
http://en.wikipedia.org/wiki/Apple_II_graphics#Video_output_...
(Note that CGLayer is not related to CALayer or CGTransparencyLayer -- they are absolutely separate things. CALayers are incredibly useful in practice; CGLayer was kind of a dead end.)
For instance: "My company failed. This is a disaster. I'm such a loser." "We beat our sales target by 200%! We're geniuses!" "After months of work, we finally shipped. Now I feel empty and have no enthusiasm for what's next. Why aren't I happy?"
(Of course those are oversimplified too, but you get the idea.)
DO still works in OS X. Frankly, it's a neat hack, but it's prohibitively difficult to build anything robust on top of it:
- Error handling is difficult -- what happens when the other side goes down in the middle of your method call? If you have to add extra exception and timeout handling everywhere, that dwarfs the small convenience of making the dispatch code easy.
- Hard to make it secure.
- It's impossible to interoperate with anything else -- what happens when you want to talk to your DO-based server using Java or Windows or Linux?
See "A Note On Distributed Computing" from 1994 for more caveats on this whole approach:
(Never took number theory myself, but that was the one thing I learned from those who did.)
They don't learn until they've been burned, probably quite badly. If the computer doesn't HAVE to burn them in the first place, why should it?
Yes. Maybe the wrong program, definitely the wrong school. (You have little choice about the time, so forget about it.)
Suggestion: Be the person you want to meet. The only person you can control is yourself, and even that ain't easy. The other students are idiots right now? Well, give them a chance to learn.
The rest is just a chaotic process; maybe you meet people that you click with, maybe you don't, maybe it comes easily, maybe it doesn't. If you get lucky, it probably won't come from a direction you expected, so stay open to all the opportunities you can find. Do what you can to improve your odds, in the meantime.
http://folklore.org/StoryView.py?project=Macintosh&story...
"Smalltalk didn't even have self-repairing windows - you had to click in them to get them to repaint, and programs couldn't draw into partially obscured windows. Bill Atkinson did not know this, so he invented regions as the basis of QuickDraw and the Window Manager so that he could quickly draw in covered windows and repaint portions of windows brought to the front."
Deltas are necessary but are only part of the solution.
(I don't recall the details, but there was little to no printer support; certainly nothing comparable to classic MacOS. For Apple's core market at the time, that was the kiss of death.)
No idea if they still do that. I don't get the impression that it was a huge boost for security. Nobody pays all that much attention to the photo.
"Should array indices start at 0 or 1? My compromise of 0.5 was rejected without, I thought, proper consideration." -- Stan Kelly-Bootle