-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider moving some languages (code coloring) out of core #12248
Comments
Languages we could consider moving out of core: C, C++, C#, Java, Clojure, Lua, SQL, Haxe. |
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: |
I just assigned it to you :-) Maybe Peter forgot you were part of the repo's org? |
Yay ^^ |
Dennis' name didn't show up in my list of names, now it does, I love it -:) Thanks for adding him, Peter! |
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 |
how to change the language to ide? |
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:
Once we've decided that, the implementation is pretty trivial -- basically a starter bug.
The text was updated successfully, but these errors were encountered: