Re: [ELPA] New package: ob-haxe

[ian martins]

> > I may be missing the main issue, but suspect the problem with keeping
> > all languages in flymake is that users don't want to install flymake
> > implementations for languages they don't use and maintainers don't
> > want to maintain code they aren't familiar with.
>
> Not only that.  Typically, the code that provides flymake support for
> a given language will need to know something about that language and
> some of that info is also needed in the major-mode (e.g. the name of the
> compiler), so the two will usually want to share some
> defconst/defcustom, but you can't have flymake *depend* on all those
> major modes, so you typically end up with duplication.

That makes sense. Where there is shared code or variables it makes
sense to keep the implementations together.  For the ob-haxe and
haxe-mode case the implementations are independent of each other.  I
guess if haxe had a flymake integration it would want to share the
compiler name variable with ob-haxe, though.

> > Both of these problems would apply to major modes that include
> > everything related to that language.
>
> I think part of the reason why the tradeoffs are different is that the
> number of "infrastructure" packages (font-lock, imenu, flymake, company,
> eglot, org-babel, smie, ...) tends to be much smaller and grow much less
> frequently than the number of languages.

That's a good point.

> Nobody is forcing them to be merged.  I'm just saying that history tells
> us that they tend to merge that way, and that it's usually a good thing
> both for the users and for technical reasons.  So we may as well
> consciously move in that direction whenever convenient.
> ...
> Good.  Then I think it would be good to try and work with the
> major-mode's maintainer and merge the two packages.

I am not yet convinced of it, smaller packages and dependencies seem
neater and more flexible to me.  But as you say, history tells us that
is what tends to happen, so maybe it will be.

Do you think it would be better to merge the packages or just add a
dependency from haxe-mode to ob-haxe? Does it make a difference?

> In the mean time, I'll do the initial addition of `ob-haxe` to GNU ELPA.

Thank you.