IDEE - Integrated development environment in emacs

Implement an IDE configuration for at least one of the follow languages (and framework), as a separate init, major-mode or minor-mode for emacs.
Make compatible with evil-mode for users more familiar with vim.
Program this in emacs lisp.
Installation of the base IDEE without knowing anything about emacs beyond reading the welcome screen.
Give users a way to group together their own IDE settings for undefined languages or frameworks.

Stakeholders

Too many IDEs to install. Time, space, uniformity across systems.
Developers, especially full stack, use various languages and connect to multiple system in a single project.
Most developers already know emacs or vim.

Developers would like to easily install their IDE on any posix-friendly system.
Users want to use familiar keybindings, whether emacs, vim, etc.
Users would like to only need to install a single IDE, rather than one per language.
Some developers would like to not need to install a JVM when not developing for a JVM.

Select some of the most popular languages:

Include emacs and vim defaults for typical text editing:

Emacs already has some of these, but it lacks straightfoward configuration, specifically per language and framework.

Install using a shell script users call that sets up the emacs init file, adds pertinent documentation to override the emacs welcome screen, and sets whether to use evil-mode or not.
Add keybindings modes for OSX or Windows users.
Target the most popular language(s) first.
Reuse where others have started. See emacswiki.
If not lisp, could also write in another scripting language that generates the .el files.
Option or default run in the terminal outside emacs; the ansi-term has some limitations.
As a dependency or an homage, examine the emacs-ide project for keybindings and window layout.
If reusing the servers design from other implementation, keep a simple codebase. For example, only use a JVM if the target language is java. Or don't mix virtual machines with interpreters.