HN user
email: krevis@snoize.com
Apple doesn't track bugs.
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.
I’m super excited to see how this experiment goes.
Yes, must be him all right.
The guidelines say nothing about any particular programming languages.
In some circumstance, when you're healthy, you could comparison shop.
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!)
About that category issue: you know about the -all_load and -force_load linker flags, right?
c.f. the "Important" box in http://developer.apple.com/library/mac/#qa/qa1490/_index.htm...
Engineers at Amazon. Seriously.
This made me laugh. The words "Apple II" and "graphics chipset" don't belong in the same sentence! The Apple II graphics were a fantastic, and fantastically weird, low-hardware hack.
http://en.wikipedia.org/wiki/Apple_II_graphics#Video_output_...
Uh, no. The last MBP update was in October 2011. The specs page on Apple's site still shows the same specs. What makes you think anything has changed?
How soon people forget! OS X had a software-based compositor until 10.2 -- that's when "Quartz Extreme" was introduced. Pretty sure the OpenGL path was planned the whole time, but the GL drivers were not nearly stable enough to use for such a crucial piece of the system.
In practice, CGLayer is not some pixie dust that magically makes your drawing fast. It helps only in a specific instance: when you are drawing repeated instances of the same content, into the same context. Otherwise, it ends up being extra complication for no benefit.
(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.)
That's a bit oversimplified. The ACT approach is that goals can be useful things, in moderation, when they're serving your values. But if you get too caught up in the outcome associated with the goal -- whether you succeed or fail, whether anyone recognizes or not -- then you're likely to have problems.
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.)
No idea why this reminded you of DO -- as you say, it's a totally different thing.
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:
Keynote is $20 on the app store. How much is your time worth?
Just remember: the Galois extension of a Galois extension is not necessarily Galois.
(Never took number theory myself, but that was the one thing I learned from those who did.)
Not true. You can get Opera for iOS: http://itunes.apple.com/us/app/opera-mini-web-browser/id3637...
The problem is: Most people don't do that, especially new computer users. (Or, these days, people who are used to web apps, which don't use command-S.)
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?
Not necessarily; you can special-order a 15" MBP with a 1680 x 1050 display.
Apple just introduced a new monospaced typeface in 10.6, Menlo. (It's the default in Terminal and Xcode.) Seems unlikely they'd want to bother changing it again so soon.
Inertia. 20 years ago, at the start of college, I got a free checking account at a smallish local bank. Which got bought by a bigger regional bank, which got bought by another bank, which merged into BofA. I had no particular reason to switch until BofA started charging ridiculous fees.
Am I just in the wrong program at the wrong school at the wrong time?
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.
The name for this concept is "lifestream". Lots of projects have attempted it, but nothing has really taken off yet AFAIK. http://en.wikipedia.org/wiki/Lifestreaming
Not Woz, Bill Atkinson.
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."
It hasn't always been that way. The Powerbook G3 series (and before?) had a similar logo, but oriented in the other direction.
What happens when the user moves the cursor outside the window, and then clicks? Or moves the cursor into a hot corner of the screen, activating something like a screen saver?
Deltas are necessary but are only part of the solution.
But: BeOS couldn't print. End of story.
(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.)
Some banks have. In the mid-90s, Bank of America used to take a photo, and put it on their debit and credit cards -- in fact, my (much newer) cards still have that same photo on them.
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.
It's hard to keep good developers, unless you let them work on something brand-new once in a while.
As always, the last word on this topic:
"Should array indices start at 0 or 1? My compromise of 0.5 was rejected without, I thought, proper consideration." -- Stan Kelly-Bootle
What do you mean "eventually"? The iPad has worked with Bluetooth keyboards since day one.
Doesn't match my experience when I worked there. We had a pretty typical setup: a few phone screens + one in-person all day interview round. I have to imagine he was interviewing around a bunch of different widely-spaced groups or something?