I wanted to do a develop an application in React. And also a Android Application of the same application using ReactNative.
So should I care learning for ECMAScript?
And if not, Kindly link a book which I can study for Javascript(short introduction+ intermediate level) which will help me building applications.
Please See: this is not my first programming language, I can do programming in C++ and Java(Most of the time).
To make it short: none.
ECMAScript is Javascript. ECMAScript ist just the official name for it.
React and react native utilize Javascript or in other words: react is pure Javascript.
Regarding react/react native there is a exception though: JSX It's invented to sugarcoat the react methods to manipulate the VDOM and makes it more convinient. But that's a part of react/react native (and for some part vue.js likewise) and has nothing to do with the language Javascript itself.
Have you done web development at all?
I'd just go through React tutorials and learn that way. Use create-react-app as boilerplate and go from there. As you start learning React, you'll start learning important Javascript concepts as well.
You mentioned that you wanted to build an app that consumes the NASA API. That's relatively easy to do. I can help you with that bit (I'm doing something similar at the moment).
Neatly explained about difference between JS and ES here: Link
I don't know what your goal is. If it is to build a quick application for the satisfaction of built an app in React/ReactNative, then you've got 1000s of articles out there in the internet. Pick one, build it and publish it or whatever.
If you're genuinely interested to learn the ecosystem, then I'd warn you not to even think of React/ReactNative/Vue/blah blah frameworks. They nicely abstract you from the fundamentals so what I'd suggest is to learn HTML, CSS and JS --> then Web APIs --> Build apps on these along with Build tools(webpack or rollup) --> finally use frameworks for building decently sized apps. This whole process isn't as long as it sounds because conceptually they're not as overloaded as in Java (772 pages of lang specification! jeez!). You can grasp them up quickly.
Some of the popular resources;
For React, I'd highly recommend docs from reactjs.org itself as they've beautifully explained the concepts and ReactNative; learn this only after learning React so that it would be easy to relate.
One quick hack (incase you don't know it): Whenever you want to learn a particular technology or want to know the popular libraries around that tech, search "awesome-<technology>" in Github, for ex: awesome-js or awesome-web or awesome-java. That repository consists of all the necessary things one might need on that technology.
Cheers!
JavaScript was invented by Brendan Eich in 1995, and became an ECMA standard in 1997. ECMA-262 is the official name of the standard. ECMAScript is the official name of the language.
Is Javascript exactly the same as ECMAScript?
No, Javascript is not exactly equivalent to ECMAScript.
JavaScript = ECMAScript + DOM API;
DOM API like: document.getElementById('id');
more info: stackoverflow.com/questions/912479/what-is-the-di…
Gijo Varghese gave the best answer here... They are for all intents and purposes the same thing with the only difference being the underlying object model of the browser environment. It's just the older name having been used for so long refuses to go away, and ECMAScript doesn't exactly roll off the tongue.
... but I highly recommend you learn how to build things without the train wreck of developer ignorance and ineptitude -- yes, those two words I constantly overuse -- that are frameworks like React.
If you don't know how to do things with JavaScript/ECMAScript (same thing) without the framework, you won't know if what the framework is doing is in fact the correct, easiest, simplest, or best way of doing things.
Which to be brutally frank, any such nonsense is usually the exact opposite of. React, angular, vue -- complete waste of time, effort, and all the claims made about them are typically made out of ignorance on the most basic of HTML, CSS, and JavaScript concepts. They create more code, more abstractions, more convoluted logic, take longer to develop, are harder to maintain, and more often than not flip the bird at accessibility norms; no matter how often the fans of such trash constantly parrot how much "easier" it is or how "productive" it makes them. Such claims are at best those who don't know any better repeating what they were told, and at worst a bald faced lie!