# JavaScript concepts applying to JSX posts

Many posts are tagged with as well as and sometimes , but then those latter tags are often removed by others.

While I understand that is not syntactically valid , isn't it the case that many of the same concepts of the latter apply to the former? As such, does not apply?

For instance, if a question with has a bunch of code where variables are declared with let, an answer might include advice to use const wherever it makes sense. But if somebody looking to answer such a question sees that was removed from the question then that person might be apt to skip the question because he/she wants to work towards badge progress on that tag.

Perhaps this is akin to where doesn’t apply- if so, just say so.

• Are you suggesting something in particular should be done? I am not sure I understand what this post is suggesting, or asking.... – rolfl Aug 23 '18 at 1:21
• If you want to add all tags that even remotely apply to a question, most questions would get more than the 5 tags allowed and tags would lose their value. While I see what you're getting at, I'm fairly sure we should leave it as-is. – Mast Aug 23 '18 at 6:10
• JSX should always be tagged if used in the code. There's a huge difference between, for example, React code with and without JSX. How I see it is if the question can still be accurately described without a certain tag, remove that tag. – Adam Aug 23 '18 at 20:43

The entire JavaScript ecosystem is a mess, because you have languages built on-top of other languages, with subsets of those languages it's a mess.

As we know JavaScript is a language, but it is also a subset of the ECMAScript language specification. ECMAScript also has other compliant languages, such as ActionScript and JScript. ECMAScript also has a couple of different versions, at the time of writing, 1, 2, 3, 3.1, 5, 6 (2015), 7 (2016), 8 (2017), 9 (2018) and next (Beta).

And so it's valid to say you have ES2 compatible ActionScript. Assuming it exists. Just like you can say you have ES9 JavaScript.

But it doesn't stop there, JSX and TypeScript build on-top of JavaScript and ES6. But they also add more to the language. But JSX can work with TypeScript, and so following your suggestion we should tag all JSX TypeScript questions with, , leaving one tag for any information that isn't about the language. And with so many libraries in JavaScript you need those tags!

You also have languages like CoffeeScript that transpile to JavaScript, but don't extend it or ECMAScript. And "isn't it the case that many of the same concepts of the latter apply to the former?" So this should include the JavaScript language tag too? Should we include ECMAScript too?

As we can only have 5 tags, we have to be a little bit sparing in how we use them. I suggest following the Python tags. All Python questions are tagged with , if it works in one version then you include or . Things like IronPython and Jython are different versions of Python and so would be the sole language tag. But can also include the version tag. is ok.

But if the question includes all the language tags, and any other tags that would make sense then I see no harm in having the following tags . If the person is doing a programming challenge then it's more than ok to change the tags to . But if you just remove the tags for the sake of it, then I don't see it as an improvement. As the tags aren't wrong, and it just reduces the discoverability of the question.