jufo's comments

jufo | 13 years ago | on: The computer that put Neil Armstrong on the moon (1960)

I worked for Decca Navigator in the 1970s. They had two ladies (not particularly little or old) who made read-only program memories for the Decca Omnitrac civil aircraft navigation computers. These had core arrays with the sense line hand-woven through the cores, going through a core or bypassing it depending on whether that bit should read as a 0 or a 1. They worked from printed charts referred to as 'knitting patterns'.

jufo | 13 years ago | on: Vim as you IDE

It's a great article. Assuming English isn't your first language, I think @insertnickname is being unfair.

jufo | 13 years ago | on: Apple charges $199 (54% more) for battery replacement on Retina MacBook Pro

I have a six-year-old 15" MacBook Pro, which is now on its third battery. A year or so ago the original 120GB hard drive started making ticking sounds, and I replaced it with a 500GB drive (not SSD - at today's prices I would have gone for a 256GB SSD). It's still a perfectly capable machine - a bit constrained by being limited to 3GB of RAM, but otherwise fine.

jufo | 14 years ago | on: How One Missing `var` Ruined our Launch

This is a lesson we all have to learn. At least in Node it is easy to pick up with a tool like JSLint. In Java, you typically have some classes which have to be thread-safe (having no per-request state) and others which are instantiated per request. Developers have to be aware of the distinction, and to code accordingly. I fell into this trap when submitting a change to JBoss back in 2000; Rickard Oberg picked it up within hours (the diffs of all committed changes went out to everyone on the developer mailing list). I'm grateful to him for that, and I've done the same kind of review for many others since then.

jufo | 14 years ago | on: Node.js cures cancer

The nice thing about node (or any other event-based platform) is that memoizing the Fibonacci function is trivial, whereas in a multi-threaded implementation it would be tricky and error-prone.
page 2