Skip to content
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

Future development after Atom's sunset #273

Closed
mitiemann opened this issue Jan 9, 2024 · 1 comment · Fixed by #274
Closed

Future development after Atom's sunset #273

mitiemann opened this issue Jan 9, 2024 · 1 comment · Fixed by #274
Assignees

Comments

@mitiemann
Copy link
Contributor

While one could still technically install atom, it has been archived and development has stopped in favor of VSCode. To me, this begs how the future development of the grammar should be organized.

In particular, the contribution guide is written with development in Atom in mind. However, the more time has passed since Atom's sunset, the less likely it will be that someone will install an old, unmaintained editor only to extend the grammar. To me, this would imply that a sustainable solution would include a setup that has VSCode as its primary development environment.

I could help updating the README, etc., but I'm not familiar enough with the VSCode extension ecosystem or the Github Actions in place such that I could update these myself. I can, however, act as a guinea pig to test a novel description.

@pfitzseb pfitzseb self-assigned this Jan 10, 2024
@pfitzseb
Copy link
Collaborator

Yeah, that's very reasonable :) I'll take a stab at updating the readme and ping you on the PR that does that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants