Essentially the result of some internal prototyping, Scripted is something of a response to programmers shying away from using a traditional IDE approach and instead opting for what might be described as a lighter weight editor (such as vim, Sublime, or textmate).
This phenomenon (if it can be described as such) is thought to be because programmers don't want to have to learn how to use a new interface, when they are already comfortable and familiar with a particular set of tools.
Bloggers on SpringSource suggest that although there is this willingness to give up the IDE, developers are also giving up those benefits they have become used to such as great content assist, fast navigation, and early error indication.
According to SpringSource, "Scripted offers something lightweight and fast, also supporting key IDE facilities developers can't live without — facilities like content assist and understanding of common module systems. Those are the key focus of Scripted. We are seeing a rise in the popularity of cloud IDEs and the notion of cloud workspaces. Developers connect to some remote system to do their development work and typically these tools (e.g. the Cloud9 IDE and eXo Cloud IDE) offer a browser-based editing experience. The user's workspace sits on the remote system. This kind of setup can work well for some teams, although in our experience we've found there is still some need for an offline development mode as developers are not yet Internet-connected 100% of the time. Also, it can be hard to get them to give up 'full control' and host their files remotely. In following the browser-based editing model and hosting the server locally, Scripted offers something that can meet developers needs now, but that will also enable the use of cloud workspaces in the future by simply deploying the server remotely."