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.
Don't know if they are the best, but I used zazzle.com and redbubble.com. One argument for zazzle is, that you create a product once and it is available in all countries where zazzle is present, e. g. UK, Germany, Spain etc.
It is really impressive how fast NPM grows, last year in July I created two network graphs to visualize NPM dependencies. There were about 35000 packages a year and 2 months ago, that number almost tripled. The top 3 packages (underscore, async, request) in terms of number of dependent packages kept their positions.
You find the graphs and some more info at the following URLs:
I've never used a .desktop file for atom and had no problems launching it until a recent update from the master repo. Guess I'll try installing the PPA package to see if that works.
You're certainly right that looking at a single factor like median income doesn't say anything about whether I'd want to live and work in a country or not. There is more to it, but it is largely determined by my personal preference, which differs from those of other people.
I think it is extremely hard to come up with a measurement for quality of life, but there are attempts to do it, e. g. the OECD Better Life Index http://www.oecdbetterlifeindex.org/
But then too many factors can be overwhelming and hard to visualize. While the flower like shapes in the OECD example look nice, I find it hard to draw any conclusions from them.
How would you measure quality of life? This income data is hopefully based on hard facts and not some kind of perception of the world.
The median income is often closer to what most people actually earn than the mean for example. I'm pretty sure the data people at Bloomberg had good reasons to chose these figures.
In most countries with data, including the US, Canada and the majority of European countries, software engineers earn more than the average person. In India and Pakistan the difference is particularly striking.