The interfaces we are supplied with and must use are pretty poor; and their documentation has mistakes too.
The interfaces don’t seem to make much logical sense, and I’m just getting a little annoyed.
An example mistake in the documentation for an interfaces function signature, where one parameter called ID is an integer: // ID: The node ID to search for (null if nodeName is provided) …As if an Java integer can be null.
If when either name or ID is used the other is null, surely an enum would be best suited to specify which is used, and then some data Object which would be a String for name or an Integer for ID.
Another example using the same functions, one of the parameters has an ArrayList<Node> type. I understand that a Set<Node> would be more applicable, but I can’t change it because they require their own interfaces to be used. They should at least be more generic and allow any kind of Collection<Node>.
“He was always putting his theories to the test and that was the great thing about Richard. Whenever you’d ask him a question and he couldn’t think of an answer he’d always say “Well, what experiment can we do to figure it out?”. I remember once for instance we were making spaghetti, that was our favorite thing to eat together… …but if you take a spaghetti stick and you break it, it turns out that instead of breaking in half it will break in 3 pieces. So I said “Richard, why is this true? Why does it break in 3 pieces?”. So we ended up spending the next two hours coming up with all these crazy theories about why spaghetti breaks into 3 pieces. In fact we ended up doing all these experiments like breaking it under water because we thought it might dampen the sound and we had some theory of breaking it at all kinds of different distances or putting it on a table and breaking it off the edge. So we ended up at the end of a few hours with all this broken spaghetti all over the kitchen and no real good theory as to why spaghetti breaks in three pieces.”—W. Daniel Hillis, entrepreneur, author, inventor and associate of Richard Feynman. (via 14-billion-years-later)
If an element has an auto margin, it is centred when the element has a width. Should the element be positioned absolutely, it is only centred if the attributes left and right are specified (top and bottom for vertical alignment). The following should centre the element both vertically and horizontally:
Little computer history lesson - this dude co-invented Unix and the C programming language. It just came out in the last few hours that he passed away last weekend.
He was 70. Ritchie was definitely one of the largest contributors to computing as we know it; you could certainly make a strong case that Steve Jobs may not have been as successful as he was without this guy’s work. Derivatives of Unix serve as the backend to your iWhatever devices (and computers running OS X), your Android devices, power a majority of the websites you visit on a daily basis (including this one) and so much more. C is used as a programming language in a ton of embedded systems — basically, computers you don’t even know you’re using.
Requiescat in pace, dmr
It’s just not fair that Steve gets a huge sendoff and this guy gets nothing.