Status Updates From JavaScript: The Good Parts

Then only reason for anyone that writes JavaScript to read this book is for giggles. This books is grossly outdated.

I realized I love Java for how strong and structured it is, and I love JavaScript for how loose and free it is, they both give unique experiences.
In java you can get an error for using "int" instead of "INTEGER" class, while in JavaScript everything is an object you can play with as much as you want!
The similarity in name is not intentional, but I keep thinking of Java as the older, wiser but close-minded brother.

I am renting this book to ”my Kindle” (which, still to this day, is a virtual one — the iOS app, currently enjoyed on my iPad mini 6).

Am I the only one renting Kindle books? The price difference compared to buying this bible is noticeable. But it wasn’t nearly free, not by a long shot.

I can see why you’d rent a novel you’d be unsure of. Or an impulse buy. But a reference book? That’s stupid.

I wonder if Swift took inspiration from JS? Swift supports Cascading.

Great things so far, especially this which binds to outer function or constructor

“JavaScript doesn’t do this but we can fix that,” paraphrased ad nauseam. This book was written by someone who very much wants to constrain JavaScript to match the patterns of other languages. Very obviously, JavaScript is its own language. The author very clearly had a bad time with that.

Two interesting concepts have been made more prominent to me from the chapter on functions: modules and memoization. Perhaps this book is good for something after all.

Reading this out of sheer curiosity. After reading the Preface, I’ve determined that homeboy is incredibly pedantic and takes a narrow and very limiting view on the language. However, I’m of the frame of mind that there is something to be learned from everything, even if that thing is about how not to be. I shall see if there is anything further to be gained here.

Another test

Another test

Been doing method extensions, still have lots to finish

i can't see these updates. sorry if they're annoying.

"The worst features of a language aren’t the features that are obviously dangerous or useless. Those are easily avoided. The worst features are the attractive nuisances, the features that are both useful and dangerous."

The long-term value of software to an organization is in direct proportion to the quality of the codebase.

I started over and finished it last week during my commute.

Intriguing

I've never actually studied javascript before.... quite fascinating to learn it's mostly a functional language (duh!)

Great book, so much knowledge but too much ego.

JSLint

== and != test for any of 7 different conditions, I already hate this language

String.prototype methods done!

CHAPTER 6 - Arrays

Regex was a long, pleasant, and not a little disorienting detour in this chapter...

Found a good companion talk on YouTube: https://www.youtube.com/watch?v=v2ifW... The talk makes the book make more sense - it's also more fun hearing Crockford talk about JavaScript than just reading.

CHAPTER 5 - Inheritance

CHAPTER 4 - Functions

Trying to impose pseudo-classical patterns on JavaScript can be an unnecessarily complicated approach, although it may feel comforting to some. Without the constraints of static type checking on your back, JavaScript provides some other, better options.

Starting Chapter 5: Inheritance...

Reviewing some topics in Chapter 3 like enumeration and global abatement using a single global variable for your application. Would like to see the ES6 updates for this book.

Arrays are really just Objects in JavaScript