The js and go implementations are near parity these days but each has areas where it's more useful. A feature/status matrix is a great idea. I've made a GH issue for it and assigned myself.
Short version: If you're building something that will run in the web browser, js-ipfs and js-libp2p are for you. If you're building something that end-users will install on their machines, you probably want go-ipfs. If you're building a desktop application (ie. an electron app) you will probably end up using js-ipfs client libraries in the end-user UI and run a go-ipfs node as a background process. If you're building something that sometimes runs in browsers and sometimes runs as an installed app (like Slack), you will probably end up using both.