For example, V11 was huge on Machine Learning and AI.now it barely gets a mention or extra development. And it's reflective of the fact that whatever Stephen's pet interests are at a particular point in time will get attention in a release. Secondly, this is the first major release that is a bit 'ho-hum' for a while.

Brenton Bostick at Wolfram has done some truly first class work in closing this gap though. There is no first-class support for daily-driver editing (vscode, emacs etc etc) for large-scale projects (other than an ancient eclipse package). As much as they want to drive adoption by coming up with (what they think are) 'cool' sounding initiatives, they will never get devs to break from their core workflows and tools to do things the Wolfram way. This comes from the big man himself, no doubt. Firstly, they are very stubborn on condoning a community to coalesce around the language other than through 'official' Wolfram channels. There are some brilliantly innovative things across the language and, once you really get into the weeds of how to write efficient functional code, some of the things you can do are incredible. Truly, few things allow as rapid prototyping with such efficacy for so few lines across so many domains in a unified interface. I've enjoyed developing in the language professionally for many years.

Wolfram mathematica 10 home edition