Hacker Newsnew | comments | show | ask | jobs | submit | enf's comments login

I think the point is that the standard clefs would be better aligned if there were 6 lines instead of 5, so both bass and treble could be EGBDFA. It would put the low C one below the bass clef and the high C one above the treble clef, instead of two below and two above but only one in between.


Yes, that was my general thought -- (added:) but that still would have two octaves different, where a note between staff lines in one octave is on a staff line in the other.

Also when you go above or below the two clefs and draw ledger lines for those notes, you're losing the background pattern once again -- you start having to count notes. With this proposed notation you'd draw another background octave (or enough of it for the notes used).


Lateral recording was a patent workaround. Thomas Edison had patented vertical recording and was not interested in licensing it to anyone else, so Berliner used the noisier, but available, lateral technique.


Fuck patents.


The character that is now underscore in ASCII-1967 and in the present really was a left-arrow in ASCII-1963, so that's why it's written that way.


What they said in 1976 was that they wanted to be "able to hire ten programmers and deluge the hobby market with good software." So more than BASIC, but without the notion that the computer software market would grow to encompass everyone.


The letter containing that statement is a key to understanding Microsoft's goals and their success (in particular the key innovation that people should pay for software). If you haven't read it, I recommend taking a look: http://www.lettersofnote.com/2009/10/most-of-you-steal-your-...


Reading that letter for the first time in years (and having worked on a commercial startup for the first time since)...

My main question is, how could Bill Gates afford the $40,000 of computer time? That's quite a lot of capital at the time.


Because like the (vast) majority of very successful people he started from a position of financial independence and social connections that absolutely are far beyond the norm.

Becoming very financially successful is very much more about what family you were born into and fortune than it is about skill or talent, although the latter certainly still matter.


I thought that they wrote the BASIC interpreter using the machines in Harvard's computer lab.


Yes, they wrote an assembler/linker/simulator on old Harv-10. I was there bugging him late at night, asking why he was wasting his time on silly hobbyist machines when we had the whole Arpanet at our fingertips. (All 20-30 machines at that point.) ;/)

Even though lots of folks were using the -10 for commercial projects on the side, Harvard made him give all the Altair money back to avoid disciplinary action. Wasn't really fair.

So, yeah, some of us were blind at the time. In my defense, I did help Carl Helmers get Byte Magazine off the ground a year later or so, along with my high school buddy Dan Fylstra who went on to create VisiCorp to commercialize the original VisiCalc.


Wake up.

Brush my teeth.

Feed the cat.

Read twitter and glance at email while I sit on the toilet.


Take a shower.

Wake Steph up if it's a day when she didn't leave before I got up.

Get dressed.

Start some water boiling.

Clean out the coffee pot and grind some new coffee.

Read other things while I wait for the water to boil.

Make eggs and toast and coffee.

Eat breakfast.

Maybe practice a song on the piano if I have a few minutes.

Leave Steph's mom her pills and newspaper.

Start walking to BART.


Would you consider the Beatles' "I'm Looking Through You" to be a counterexample? Its bridge is performed twice.


Tweets contain a lot of metadata too though. In practice a tweet is really about 3K, not 140 bytes.


Yes, taking the example in the API docs [1] it gives me 3K of JSON, which can be gzipā€™d down to 1K.

[1]: https://dev.twitter.com/rest/reference/get/statuses/show/%3A...


By Bob Bemer, later the "father of ASCII"


The problem with making the opposing red end sooner ("oncoming traffic has longer green," as the signs say) is that the opposing permissive left turns that haven't cleared by the end of the yellow are then caught in the intersection with their signal red and yours still green. The problem is called the "yellow trap" (http://en.wikipedia.org/wiki/Yellow_trap), and some states, including California, outlaw the practice because it is too dangerous.

I'm completely with you about wanting everything demand-actuated to be very responsive, though. Traffic signals are all engineering with no user interface design at all.


The primary author of this document is Peter Koonce, who is a pretty serious bicycle guy. You might be interested in his blog: http://koonceportland.blogspot.com/



Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact