twipped, 25 days ago

@chriscoyier coercion. 90% of people’s problems with JS are because they don’t understand the coercion rules

DavidDarnes, 25 days ago

@chriscoyier

console.log(document.querySelector("button"));  

If there’s one line of JS I could hold aloft and proclaim “I have the power!” it's this

iamdtms, 25 days ago

@chriscoyier It's not the same thing?

Hybrid/Unicorn/Web/Frontend designers
Without OOP JS (jQuery/Nuxt/ES5/... framework level)

Frontend/Full Stack Devs
With OOP JS (Angular/React/Vue/... API level)

adactio, 25 days ago

@chriscoyier

“Find stuff and do stuff to it”

querySelector (they already know CSS for that), then addEventListener, and then …whatever behaviour they’re designing (that last bit could be simple or complex depending on what they want to do—maybe start with changing the classList of an element?)

chriscoyier, 25 days ago

@adactio Yeah that's definitely my line of thinking too. I think I can flesh that out into some half decent advice.

Ciantic, 25 days ago

@chriscoyier That is though because you can't learn JavaScript by knowing "one thing". Knowing how to do IF/FOR/WHILE statement is useless, same with other constructs, they are more than one thing.

I think it leaves only one thing to know: JavaScript can be used for interactive behavior in UI.

eeeps, 25 days ago

@chriscoyier
ideal world: querySelector/All
real world: npm