Consider moving some languages (code coloring) out of core #12248
Description
Wednesday Feb 27, 2013 at 01:27 GMT
Originally opened as adobe/brackets#2969
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.