Max on Nostr: It’s also an interesting decision when “public”/“private”/“protected” ...

It’s also an interesting decision when “public”/“private”/“protected” have been reserved keywords since ES3 (because of ES4). On the one hand I understand wanting to keep class syntax and object initializer syntax close. On the other hand I’m still not sure for instance # prefixed names are that much of an improvement over a “private” keyword, even in object initializers. { private thing: true } doesn’t seem terrible. { #thing: true } starts to feel like perl/Ruby prefixes.