4 ms·
the problem with this is it's opinions of the creator, presented as imperial fact - as if it's actually representative. This is dangerous, because people who a
by meesterdude 10y ago
the problem with this is it's opinions of the creator, presented as imperial fact - as if it's actually representative.
This is dangerous, because people who are easily mislead will see this and become java developers - or hire only .net developers, because they saw that graph.
I've browsed around - every one of these graphs is completely irrational, tells nothing substantive, or are misleading at the least. There are some truths scattered about, but by and large it's largely nonsense.
Graphs tell a story - and every one of those stories is either entirely made up, or has some pretty disputable results.
there IS a story to tell, but it takes more than a graph to tell it. There's a lot of "it depends"
I don't mean to gutpunch the author. I strongly disagree with this project - but commend the effort. the design is clear and straightforward, and it's another project shipped. That's certainly worth something.
edit:
from the related writeup:
> What makes this visualisation so attractive, is that it provides you with a
starting point for understanding and exploring a certain market and it’s key technologies.
> That information can help you decide whether to either invest your time and money into an emerging technology, or wait for the hype to pass.
this is exactly the kind of takeaways you should not be making from these graphs.
- gph 10y agoYep, just another person using data visualization techniques to describe their personal opinion while giving them the air of empirical authenticity. It's unfortunate really, the same as a media outlet using a misleading graph or junk data science in general. Undermines the trust in a still nascent field.
- fudged71 10y agoIt would have been better to host an industry survey first and then plot results based on it.
- meesterdude 10y agoThis is a great idea! I really like this. But the audience needs to be clear, and the method of gathering unbiased. Maybe I would say, something like "you would use PHP when _____" or "you would reach for flexbox when _______" as a survey methodology. Because that's kinda how it is for a lot of things. The give & take needs to be captured. Maybe some way of check boxing priorities. Like, I care about maintainable code, or cheap developers, or high concurrency, or good track records. All that would be really useful in helping establish a direction for a developer and a company researching directions.
- prefect42 10y agoYou've just defined the Internet.