@jeromesnail
At first I was like "I can't think of anything this video could teach me". After two minutes "I don't even know how console logging works..."
@perfectwebsolutions
00:48 how to use console.log 02:39 Object Destructuring 04:00 Template Literals 06:09 Spread Syntax 08:20 Loops 10:21 Async/Await
@yandodov
console.table() --- mind blown
@andyyuan9338
It's a whole new level of console.log!
@bender7367
00:51 - Debugging with console.log 02:39 - Destructuring 03:59 - Template literals 06:07 - Spread syntax 08:19 - Loops 10:18 - async/await
@mihutz98
Code not this that
@bigal3434
A lot of valuable information in here, thanks so much. Not too basic, but also not confusingly high-level. The console table, "Oh that's sexy"
@tehdave192
Another thing to keep in mind at ~10:15 is that you're now doing 3 loops compared to one loop. At some point you have to wonder whether you want to give up runtime for readability, because the for loop is definitely going to be faster. It doesn't matter when you have one record, but if you have an array of multiple hundreds of thousands of records if you're running a batch or an import of something, it is going to make a difference if you reduce, filter, and map, or just do one for loop. Technically you could also just do it in one reduce function.
@vitamin_ce
Fireship : So we're going to parse the arguments in it.... Me : Looses focus for a bit Fireship : So yeah that's how you make Minecraft with JS
@aindaecedo
A coffe for the great content of the channel
@anand_undavia
"I can do a whole video on console logging" Please do!!
@TwinFeats
Excellent video! I've been a JS developer for 20 years, and so I learned a ton from this. :) As an old-timer, I do have one comment on some of the efficiencies here: I prefer code clarity over code brevity. Shorter code is not necessarily easier to understand, especially for someone who is not yet a JS expert. So some of the tricks you showed I will absolutely be using, but others I won't just because - to me - they aren't as clear as what they are replacing. :)
@RonanConnolly
Wow, I had no idea about:
- console.table
- console.log({propertyName})
- CSS style in console.log
Thanks for the tips!
@yunusdurdygulyyew9270
This is depressing and motivating at the same time
@Wildenfree
Trying to watch this at night in bed in the complete darkness before I go to sleep, and the switching between dark & light screens made me for sure turn this into a tomorrow endeavor.
@sleeplessdev7204
Most "pro" tip videos are pretty obvious syntax sugar in ES6; But I actually learned some cool stuff from this one! I can use console.table to print formatted arrays?? "Woah!" I can add inline styling to console.logs?? "Whaaattt!" I can use template literals to automagically destructure function parameters??? "Mind BLOWN!!" Great video!
@AlejandroVivas
Shit, I just realized I don't know nothing about JS.
@basketball_court_2
Very nice video! But I find the Object.assign bit misleading. So I decided to comment here to clarify. In the video, he said instead of mutating an object, we might want to create a whole new object. Then he talked about Object.asign and said that object spread is just a syntactic sugar. This might mislead you to think that Object.assign will create a new object. But in fact, it doesn't. It mutates the first object in the arguments. And the object spread is only a syntactic sugar for Object.assign({}, ...), not for the whole Object.assign function. I hope this will clear things up. At last, thanks again to the creator for this informative, concise and easy-to-follow video!
@Goofy8907
6:15 I can respect someone who codes examples in Pokémon
@Fireship