This trademark is almost never enforced, and likely couldn't be at this point.įor these reasons, some have suggested we use JS instead of JavaScript. Oracle (via Sun), the company that still owns and runs Java, also owns the official trademark for the name "JavaScript" (via Netscape). In some ways, legal relationships run even deeper than the syntax. We also use the to punctuate the end of a statement. Those similarities don't particularly come from shared development, but from both languages targeting developers with assumed syntax expectations from C (and to an extent, C++).įor example, we use the to end that block of code, just like C/C++ and Java.
There are some superficial resemblances between JavaScript's code and Java code. It could just as easily have been called "WebJava," for that matter.
In other words, JavaScript was a marketing ploy to try to position this language as a palatable alternative to writing the heavier and more well-known Java of the day. These lightweight "scripts" would be the first ones to embed inside of pages on this new thing called the web! Why? Because this language was originally designed to appeal to an audience of mostly Java programmers, and because the word "script" was popular at the time to refer to lightweight programs. But when it came time to publicly name the language, "JavaScript" won the vote. Internally at Netscape, the brand LiveScript was used. When Brendan Eich first conceived of the language, he code-named it Mocha. The truth is, the name JavaScript is an artifact of marketing shenanigans. Is this language related to Java? Is it only the script form for Java? Is it only for writing scripts and not real programs? The name JavaScript is probably the most mistaken and misunderstood programming language name. A good start always depends on a solid first step. So to get the most out Get Started, make sure you spend plenty of time writing JS code to build up your experience.Įven if you've already written a lot of JS before, this book should not be skimmed over or skipped take your time to fully process the material here.
This book's main job is to get you ready for studying JS deeply throughout the rest of the series it's written assuming you already have familiarity with JS over at least several months experience before moving on in YDKJSY. Keep in mind that even though this book is titled "Get Started," it's not intended as a beginner/intro book. But all of JS is founded on these three foundational pillars. JS is a broad and sophisticated language, with many features and capabilities. In particular, Chapter 4 identifies three main pillars around which the JS language is organized: scope/closures, prototypes/objects, and types/coercion. Instead, patience and persistence are best as you take these first few steps.įollowing this background chapter, the rest of the book lays out a high-level map of what you will find as you dig into and study JS with the YDKJSY books. So don't look at this book as something to rush through for a quick achievement. No matter how much time you spend with the language, you will always be able to find something else to learn and understand a little better. I emphasize the word journey because knowing JS is not a destination, it's a direction.
If you want to get to know JS, this is how to get started taking the first steps in that journey. This is valuable insight into the identity and process of how JS is organized and maintained all JS developers should understand it. We need to start by covering a variety of important background housekeeping details, clearing up some myths and misconceptions about what the language really is (and isn't!). In this first chapter of the first book of the You Don't Know JS Yet (YDKJSY) series, we will take some time to build a foundation to move forward on. But we can all start getting to know JS better. You Don't Know JS Yet: Get Started - 2nd Edition Chapter 1: What Is JavaScript?