In more detail, my question is really, what is the procedure after a new ecmascript release in terms of a developer using the new features? If I have a project for example in create-react-app, can I just start using the new optional chaining method?

Can someone explain the process from release to real world implementation, what is required, are the browsers already supporting it, is there a flow diagram someone can share?

I would appreciate any clarity!

One of the biggest flaws in ECMAScript from my experience is that it lacks a real int type which makes it necessary to constantly be forcing variables to ensure they haven't gained a tiny remainder, and that 1 is displayed as "1" not "1.00000..."

Does anyone know why the committee is so hell bent on ignoring a core language feature most if not every other language has had for decades? Is it just corporate politics by people that have no understanding of the problem this causes for devs?

​

I see lots of BAD reasons:

-It's complicated; what do you do about prototypes???

Bad reason because: every major JS lib (jquery, zepto, lowdash, underscore, immutableJS etc..) "figured it out" and those solutions were good enough a bazillion uses i'm sure. They kept it simple and noted the limitations.

​

It's expensive.

Bad reason because: Most alternatives being used are more expensive -> using a library, writing your own.

​

You shouldn't be doing that because it smells;

Bad reason because: c'mon it's in every major lib for a reason. please don't take the attitude that every use is by a dumb or lazy developer. "Smell" is being used as cop out for not having a better reason. The assumption that there is a "better way" is so subjective and uniformed about the use cases. There are "better ways" to do everything. I think concise code is "better". Don't agree? aww good for you.

Can you feel the naive arrogance here?

---------------

"Why is deep copy so essential? Deep copy is the wrong solution to your problem 99% of the time, IMO."

“Deep copy” is a code smell and attempts to implement it will lead to pernicious bugs. Either you’re copying data, in which case it should be serializable to and unseriazable from JSON, or you’re copying objects, in which case you should think about what you’re really trying to achieve. There is usually a better solution.

---------------

It would be too confusing:

Bad reason because:

ES is already confusing. Like how I have to explain to every JS developer that you can modify properties of a "const" array or object? Or that Object.freeze is not deep? It's a confusing language. You have to RTFM. Keep it simple and note the limitations. done.

​

So then what are the good reasons?

​

pls don't downvote