673 karma · joined June 27, 2013
This seems pretty unfair. "Name a laptop with 32GB of RAM, except the ones I don't like don't count."
> C'mon, obviously the toolbar has it when running macvim or iTerm (or some other terminal) with vim.
I don't see how that's a foregone conclusion. Moreover I like using the terminal app that comes with the actual machine.
> still the best keyboard and trackpad BY FAR in the market
Trackpad maybe, but Apple's keyboards have gotten tremendously terrible.
Then you can't have been paying much attention.
It's a bridge to far to directly attack people just for working on an open-source project, but the creator of this project did not do that, obviously.
One obvious example is that your one-liner doesn't specify that your code has no warranty so someone can sue you if it doesn't work as advertised.
A beginner can't grasp the motivations behind the design of musical notation, and I don't expect a beginner to grasp the motivations behind the design of any complex system. That does not make the system absurd.
It doesn't actually obscure the relationship between the notes -- it makes them clearer. For example, I see the notes C, E, and G on some sheet music, maybe with some accidentals on some of those notes. I know that I'm therefore supposed to play a C triad. Now, there are multiple kinds of triads, but once I know I'm supposed to play a triad, it's easy to use context to pick out which one I need (major, minor, diminished, augmented -- usually one of the first two). If I were supposed to play a C# major triad, though, and the written notes were (C#-F-G#) as opposed to what they should be (C#-E#-G#) then that's confusing because it looks like I should be playing an arpeggiated sus4 of some kind. So the written nature of scales on the staff engenders an understanding of the relationship between the notes. Basically we write things the way we do so that the people reading the music can more efficiently pattern-match.
> C major is identical to A minor, and I don’t understand why we need both.
They're not identical. C major and A minor have the same notes in their respective scales. But we say that a piece is in the key of C major when it resolves to the a C major chord at the end, and we say a piece is in the key of A minor when it resolves to an A minor chord at the end -- an important concept for reasoning about how a piece is supposed to be performed.
> C minor: C D D# F G G# A# C
Eb, Ab, and Bb, not D#, G#, and A#.
> This has got to be some of the worst jargon and notation for anything, ever.
It's really not. Keep practicing. It makes sense, I promise.
I hear a lot of people -- usually people who have not been studying music for very long -- insist that the system would be more logical if there were no accidentals and there were 12 notes with distinct names and the staff had a bunch more lines on it. I've never bought it. The notation of music isn't arbitrary, it's informed by experience and it works.
It seems to me that while I'm on the GitHub page anyway, it's reasonably convenient to just copy-paste the URL in a file so I can pull in the package and use it. I can't imagine just using a package repo for discovering new packages, that would be tantamount to just pulling whatever random code someone wrote that looks like it might solve my problem.
curl -fsSL https://raw.githubusercontent.com/rgcr/m-cli/master/install..... > install.sh
I really don't think you want people on HN to try to explain de facto segregation and the history of race in American music to you -- you should really look for reading material by academics on these subjects.
This might be true, depending on what type of processing you're doing, and if you have a good garbage collector.
Of course, if you're allowed to use mutable trees, then you should just use a hash table which will be faster both asymptotically and in practice.