This graph is based on influence relations retrieved from Wikidata, which is the central storage for the structured data of Wikipedia. I'm sure that some relations are debatable and that there are missing relations. That said, just like Wikipedia everyone can help improve Wikidata by adding, editing or removing information and by adding references. Would love to get your feedback und suggestions for improvements.
I created this tool to learn fretboard notes as well as chord and scale shapes. I also wanted to improve my knowledge of music theory so I wrote all code related to theory from scratch instead of using libraries. While the latter is only beneficial for me, I hope that others find this tool useful for making music. I'd love to get your feedback.
One issue I'm aware of is that for non-diatonic scales (e.g. minor pentatonic) the shown triads are not correct. I just leave the triads for the last selected diatonic scale. What would you do? Hide them?
Not every CPU you find in the different Chromebooks is equally suitable to run Linux. Most Chromebooks on the site actually have the CPU model and number listed though.
> people, please don't use discrete color scales for continuous parameters
There are arguments against using continuous scales:
* By using classes (e. g. quantiles) you can reduce the impact of outliers. On a continuous scale an outlier can cause everything else to be perceived as one color.
* Perception of color intensity is not strictly linear.
> There is no reason to store encoding information in an html file.
That's simply wrong. If you use libraries like D3.js, that contain non-ASCII characters in the source code, and you do local development with a server that sends no encoding headers or even without using a server at all, your code won't work.
If your file is in html5, then all browsers will assume a default encoding of utf-8, which is what you should be using anyway - unless you have a very good reason, such as your file contains a majority of kanji or kana.
If you're using something older, the official defaut is iso latin 1, but I believe all modern browsers will try utf-8 first - this is not something I've verified for myself, it works on my setup but I also configured my os to use a default utf-8 encoding, so I can't tell for sure.
I'm also unclear how this relates to d3.js - that's a javascript import, not an html one. Or do you mean inline javascript that uses d3.js?