It is a simplified API for p5.js, and very quick to get up and running with.
You might also find code.org's Game Lab a useful environment, which is p5.play based, has a sprite editor built in, and has both block based & text based editing support: https://code.org/educate/gamelab
As an aside: it makes me wish there was an easy way to "fork" diagrams like this, and see what others might come up with.
While I appreciate the sentiment, truly fixing these roadmaps is an industry-wide problem. ;-)
A CSS framework like Bootstrap (https://getbootstrap.com) will provide you with some easy to use components.
Your other option is to use something like Laravel or Rails or Express, and just do server-side rendering. A lot of people are still doing this, and it's still well supported.
The advantage of the static site generators is much better performance / lower resource usage, at the cost of flexibility.
This map is vast but it has a lot of important gaps.
Some other things are just inaccurate. e.g: github required for any path. You could use gitlab, bitbucket, gerrit... plenty of good solutions out there.
Joking aside (I'm actually a vimmer ;), is there any use case for aiohttp if you are using django since django now offers channels?
PS, please don't start a flamewar, they are both good.
I disagree on a lot of things, but who cares.
I imagine PRs could fill out more, like e.g. adding Haskell, Erlang etc etc.
The backend could be further broken down into separate parts, each potentially using a different language, in order to give a clearer picture of the options and complexity. 1) web server (request/response), 2) search 3) database/store/access 4) data pipeline/ETL 5) payments
It's pretty messy, as it is.