Consider moving some languages (code coloring) out of core

[peterflynn]

In #2844 it was pointed out that some of the languages Brackets has syntax highlighting for out of the box are quite uncommon for modern web developers. Now that it's possible to do so, we could consider moving some languages out into extensions that we don't ship by default.

That only seems worth doing if it has benefits, e.g. improved startup time. We should try removing a bunch of languages from core and timing warm/cold startups to see if it has much effect.

If we do want to remove languages, we'd have to decide three things:

• Which languages to remove
• Where to host the extensions (and are they officially supported by the Brackets team? probably wouldn't be much work)
• What granularity -- one extension per language? Or try to bundle up related language "packs"?

Once we've decided that, the implementation is pretty trivial -- basically a starter bug.

[peterflynn]

Languages we could consider moving out of core: C, C++, C#, Java, Clojure, Lua, SQL, Haxe.

[peterflynn]

There's also some risk here: users might think Brackets flat-out can't support a given language if they open a file and see no highlighting out of the box. (We have that risk already for non-core filetypes, but we'd be adding to it by removing stuff from core). There were two suggestions for dealing with that:

• @DennisKehrig suggested we could have some sort of auto-discovery mechanism built into our future extension registry -- our server would know if any extension exists to support a given file extension and could inform the user if so.
• @gruehle suggseted a simpler idea -- one we could implement now. On first open of an unknown file extension, we just pop a dialog telling the user that an extension may be available and linking to the extensions page.

[peterflynn]

I just assigned it to you :-) Maybe Peter forgot you were part of the repo's org?

[DennisKehrig]

Yay ^^

[pthiess]

Dennis' name didn't show up in my list of names, now it does, I love it -:) Thanks for adding him, Peter!

[njx]

Reviewing - I have a counterproposal: actually keep all the languages in core (and maybe add all the ones we have in codemirror), but just lazy-load the modes, so they aren't loaded until a file that uses that language is open.

To me, low pri

[nanito2757]

how to change the language to ide?
to the spanish. thks