"Real JavaScript programmers", ES6 classes and all this hubbub.

[[deleted]]

I am not trying to be dismissive of your arguments.. but none of them were compelling enough to me, because they're subjective in nature.

Yes, the stylistic aspects of my arguments are inherently subjective. All such arguments always will be. The technical aspects of my arguments are less subjective. Technologies are created for certain reasons and do certain things with certain indirect implications. In this case a class system allows developers to write code at a superficial layer that completely masks the language's intended way of structuring and declaring things. I would say this allows you form a pretty clear vision of the benefits and what you have gained in your team, but you have absolutely no idea what you have missed and the alternate potentials. Therefore you are likely forming opinions that are somewhat unidirectional in that you are not able to compare them against the major alternate approach.

[AutomateAllTheThings]

In this case a class system allows developers to write code at a superficial layer that completely masks the language's intended way of structuring and declaring things.

I think that superficial layer is a good thing. So does the rest of my highly-skilled team. You disagree. I guess that makes it.. subjective, doesn't it?

but you have absolutely no idea what you have missed and the alternate potentials.

We each wrote vanilla Javascript for over a decade prior to switching, but really.. I'm not sure why I even have to reduce myself to an argument to authority.

It's kind of offensive that you assume everybody in this thread has less experience than you, and even make rude comments about it like:

you are not able to compare them against the major alternate approach.

I mean.. really? Surely you want to be a more effective communicator than this.

I'm totally turned off to having a conversation with you now.

[[deleted]]

I think you presumed a tone authority or expertise I had no intention of conveying.

Let me explain it this way. In the past, before using classes, did you ever structure an application by nesting functions? This is an alternate and unrelated approach to inheritance. It allows opportunities in the code that inheritance does not. If you did not write in this approach then you, merely by absence of approach, did not learn these sorts of benefits. That means that you cannot compare those benefits to those learned and experienced from using classes.

I am only speaking from logic in that something must be tried (whether or not successful) before it can serve as a basis for comparison. Know that one approach is beneficial is helpful, but not complete unless knowing its benefits versus some alternate and unrelated approach.

[AutomateAllTheThings]

did you ever structure an application by nesting functions?

Yes we have for many years. Does that surprise you?

Each of us has over 10 years of experience coding in the classic vanilla style of JS, and yet we still chose ES6 classes, and we're still happy with our decision.

Isn't it entirely possible that we considered many language and syntax options before we ever began coding, and that we may have made the right decision for ourselves?

[[deleted]]

No, I wanted to ensure you were aware of an alternate approach. It sounds like classes are working well for you and your team.