thanks! this helped me realize a switch block was NOT the correct way to handle what i was doing 😂

your teaching style is so great, thank you very much!

tbh using Objects/Maps instead of switch usually is much more readable and convenient. You can use ?? to implement defaults, some prototype key collision(like valueOf) is not an issue 99% of the time(and can be avoided with null prototype or Map), having multiple values match the same case can also be fixed with Map. You can't really implement a case without a break tho unless you get really verbose but then just actually use a switch - but honestly how often do you even need this in a switch statement? If anything it makes your code even less readable when you have to consider that some cases don't cause a break. using switch over if else doesn't bring any benefits really - I find them both to be quite unreadable and verbose and I think performance-wise they're literally the same.

Kyle, what is your opinion on use of switch statements versus objects with keys being the case constants and values being the case blocks wrapped in functions? Of course readability will take a hit, but will that not make the code more declarative and hence reactive?

Your videos are so easy to understand thanks Bro👌👌

Thank you so much, you explain magnificantly

Never tired watching and executing your tutorial ❤

In php I sometimes do this: switch(true) { case ($myVar1 < 5): {echo "case 2 " ;break;} case ($myVar2 != "foo" ): {echo "bar" ;break;} case ($myVar3+2 < 5): {echo "foo bar" ;break;} }

Thanks WDS!

Your videos are the best in KZfaq. But this one was simple and trivial. By the way, Thank you

great video 👍🏿

Thank you

But you can use switch statements to check if, say, a number is less than 5. You just need to gently abuse what a switch is used for. The expression in a switch statement is the value you are testing your cases against, and if the derived value of the case matches the derived value of the expression then a Boolean true happens which runs the code inside the matching case. So, you can shortcut a switch by setting the expression to be a Boolean true and then do whatever you want in the cases const x = 50; switch (true) { case x < 50: console.log("Less than 50"); break; case x > 50: console.log("Greater than 50"); break; case x === 50: console.log("Exactly 50"); break; default: console.log("x isn't a Number"); }

Thanks

Thanks for always enlightening us!

Kyle is super awesome at teaching stuff. That being said, I just don't see the need to get into Switch Statements unless there is a huge performance increase. It can't do anything else other than equals, needs breaks... whereas if/else is much easier for a newb like myself to understand and all Comparison Operators work with it. Can anyone please share the more advantages to Switch?

I generally don't like switch statements, they take a lot of space and look ugly af (thats personal preference tho), also the fact it does the fallover when you dont have break is an easy way to end up with a bug that's not very obvious (thats kinda depending on what type of logic is in there), what I tend to do instead is just use maps/objects (or whatever u call the equivalent in any given language) and just map the values straight to the logic that handles them

Can you repeat this example using object literals instead?

i love this channel

Hey bro, how are you changing multiple words at once for example you highlighted cat and changed it to bobcat twice

you can also drop the "break" if you add "return"

Hey bro I had developed a simple react website it's running properly in firefox but lagging in chrome and other browser

I much rather a lookup table/dictionary but the problem is most people use object literal when they should be using map

Great ad :))

how bout using object literal for simple cases like this one.

you can put the default case first btw

Hi, is there any way to change a=× b=y If(a=× and b=y){} to switch statement?

This is one instance I actually prefer VBs implementation where there is no need for a break statement. I can’t think of a single instance where I didn’t want the break in each case, so why not just make that the default behavior?

Switch case is antipattern. Better way is to use hash (object)

Object or Map is better than switch statements in my opinion

if you want to use greater than, less than in your switch statement try this: switch (true) { case x < 5: console.log('small');break; case x >= 5 && x < 10: console.log('medium');break; case x >= 10: console.log('large');break;

id rather use json objects as map console.log(message[faveAnim] || "unheard")

Switch would be great if it behaved like Select Case without the breaks.

dogs are actually awesome animals and they can be taught to not make loud sounds while being at home dont hate them Kyle

Best youtuber

I don't like switch statements. I really wish they were exhaustive or more like match statements in rust

I prefer if over switch.

Thanks for the video. It was difficult following you because you talk fast

Not adding a break;/return; statement after your logic is complete is a bad practice. You want the logic under a specific case to be executed and proceed with the rest of the code outside of the switch~case block. Always add a break; statement after you're done with your case logic. Additionally, I know this is JavaScript, but make sure to manipulate the input string into something generic, such as all lowercase to make sure user input won't be a problem. Where applicable, use Enums and other values you can directly control when using switch~case. Performance-wise, it's much better than an if~else if block. You should really be using if~else if when you have multiple mutually exclusive conditions that can be fulfilled within the same program loop (such as whether the user has admin rights and is logging on with certain options enabled). If it's a single variable that can contain multiple values you need to check for, switch~case is better.

For this case I use switch statements like this: function getAnswer(animal) { switch (animal) { case 'cat': return 'Cats are great' case 'dog': return 'Dogs are kinda loud' case 'shark': return 'That's an interesting choice' default: return 'I have never heard of that animal' } } I like to use oneliners in these kind of cases because every line belongs to a value. It's also easy to test because it's a pure function.

only things i have against this video is how cats are better than dogs

This is decent info to know how these work, but really should not be used anymore. Switches generally does not lead more maintainable/readable code. Heck there is proof with someone showing that you can write conditionals of less than and greater than.

Some say, switch is an anti-pattern.

someone show this video to yanderedev

First comment. That's Kyle

I don't like the switch syntax, usually i do this let favoriteAnimal = { "cat": ()=>{ console.log("Cats...")}, "dog": ()=>{ console.log("Dogs...")} } favoriteAnimal["jaguar"] = favoriteAnimal["cat"]; favoriteAnimal["jaguar"]();

In my opinion, switch statements is bad style. It's hard to read and maintain

I still think switch statements are useless compared to ifs

swith-case is a bad programming practice.

I'm first comment...

Objects are better: const favoriteAnimals = { cat: "Cats are great", dog: "Dogs are kinda loud", shark: "That's an interesting choice", } function getAnimal(animal) { const animalDescription = favoriteAnimals[animal] ?? "I've never heard of this animal"; // For beginners: read more about short if statements, short circuiting, and nullish coalescing. console.log(animalDescription); } If you want multiple animals to match the same result, such as Cat, Bobcat, and Jaguar all matching "Cats are great", you can use multiple techniques. If can get pretty verbose, and switch is bad imo. I used an array with the allowed values, and return "cat" if the animal exists in the array function getCat(animal) { const cats = ["jaguar", "bobcat", "cat"]; return cats.find(cat => cat === animal) ? "cat" : undefined; }

Bro did you see my email.

or you can rewrite it to: const favoriteAnimal = "shark"; const favoriteAnimalList = { cat: () => console.log("Cats are great"), dog: () => console.log("Dogs are kinda loud"), shark: () => console.log("That's an interesting choice"), }; favoriteAnimalList[favoriteAnimal] ? favoriteAnimalList[favoriteAnimal]() : console.log("I have never heard of that animal");

Make youreself a favor and dont use switch at all. Its bad practice. There are other, more readable ways