Add Omnis

[jasongiss]

Support for the Omnis programming language, used by Omnis Studio.

[joshgoebel]

We're currently in a large discussion about how to handle language submissions:

#2149

Currently the maintainers don't have the time to review or maintain any new languages and related issues - so we've been recommending that they be published as separate packages/repos. To see what that looks like:

https://github.com/highlightjs/highlightjs-robots-txt

Just a heads up.

[jasongiss]

Thanks very much for the pointer, @yyyc514.

That is an interesting read, and I feel for the position you maintainers are in.

I am happy to wait until a decision is made on how best to handle new languages - good luck with that!

[egor-rogov]

@jasongiss are you willing to maintain this language? I can spin up a repo for it.

[joshgoebel]

@jasongiss Any chance you'd be willing to maintain/contribute to other people's grammars (not just your own) on a semi-regular basis - or triage issues or something? I've been pushing for the idea of a "community" repository to keep all (or many) of the languages in (to make this whole process simpler, to make building a single "binary" from many sources simpler, etc.), but it only works if we can find people to maintain it.

Ie, in my imaginary world you'd just submit a PR there, the community would review it and once it was ready it'd be merged into a larger world - and we'd all look out for it - rather than having it locked away in a separate repository.

[jasongiss]

@egor-rogov I would certainly be willing to maintain a repo for the Omnis language.

@yyyc514 I'm very sorry, but I really don't have enough free time at the moment (and probably not the expertise) to be able to commit to helping maintain a "community" repo.
I can put time into maintaining the Omnis language, as I work on the Omnis development team, so I can do that on 'work time'.
I'm happy whether that's in a separate repo, or a community repo (I just wouldn't be able to put much time into other languages).

For our particular use-case, it's nice to be able to build a single JS package with our language embedded (which I guess would be more likely with the community repo?), but happy to go with whatever the official technique becomes.
The main thing for us is just having a central place where the language definition can be found and contributed to.

[joshgoebel]

I can put time into maintaining the Omnis language, as I work on the Omnis development team, so I can do that on 'work time'.

Nice.

For our particular use-case, it's nice to be able to build a single JS package with our language embedded (which I guess would be more likely with the community repo?)

Not sure likely is the right word. I want it to be easy no matter where the cards fall on structure of repositories. Just we aren’t there yet.

It’s not particularly hard now - for a single language - just very manual.

[jasongiss]

Not sure likely is the right word. I want it to be easy no matter where the cards fall on structure of repositories. Just we aren’t there yet.

It’s not particularly hard now - for a single language - just very manual.

I agree - the process currently works well, it just needs a clever solution for adding languages in a maintainable way.

[joshgoebel]

@jasongiss

#2328

[joshgoebel]

Closing this as discussion can now continue on #2328.