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

What namespace? #2

Open
CanadaHonk opened this issue Jan 22, 2024 · 4 comments
Open

What namespace? #2

CanadaHonk opened this issue Jan 22, 2024 · 4 comments
Labels
agenda+ Should be discussed next meeting spec

Comments

@CanadaHonk
Copy link
Member

CanadaHonk commented Jan 22, 2024

Node has process for most APIs discussed here (and more), Deno has its own-named Deno. CLI/etc seems obvious but needs (a lot of?) bikeshedding. Separate discussion for whether to use process: #4

@lleyton
Copy link

lleyton commented Feb 9, 2024

Hm.. personally process would be ideal, but that's already ruled out. I think something like sys or system could work.

@aapoalas
Copy link

aapoalas commented Feb 9, 2024

I've seen at least one TC39 proposal that seemed to be adding System.method functions so I wonder if that was in the cards for ECMAScript in general at some point? https://tc39.es/proposal-error-stacks/ If it was and still is then system is probably right out.

CLI looks a bit out of place compared to process, window, document, navigator but it's definitely not bad at all. runtime feels ... not right.

@ljharb
Copy link
Member

ljharb commented Feb 9, 2024

No, it's not. System is not going to happen.

@CanadaHonk CanadaHonk added the agenda+ Should be discussed next meeting label Mar 7, 2024
@pi0
Copy link

pi0 commented Mar 7, 2024

sys looks like a clean, self-describing, and expandable namespace and seems to work well for python :}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda+ Should be discussed next meeting spec
Projects
None yet
Development

No branches or pull requests

5 participants