Unnecessarily biased, boring, unprofessional JavaScript study note.

Gyunam Park — Thu, 24 Apr 2025 13:17:59 +0000

Please comment any inaccurate information.
I'm constantly updating it as I study.
Or if you have a better example or content, please let me know.

a perfect program

There is a minor complaint that nothing is calculated and no function is performed, but there is a significant possibility of bugs occurring instead.

I dare predict that even with any programming language, the code is very, very likely to be the same.

comment

// line comment 
/* 
 * block comment
 * You said you'd buy me a cheeseburger. 
 * Why would you give me a cheeseburger without the meat patty?
 * You stupid.
 */

I'm sure comment is the most beautiful feature. After I write a complaint about a close friend's barking prank on this code, even if I execute it in front of him by mistake, he has no way of knowing it.

console.log

console.log(`It's not called a cheeseburger.`)
console.log(`It's just a stack of bread, cheese, and bread.`)

However, sometimes I have to express my sincerity. Cheese Burger without meet patty are a serious issue.

letables

let cheeseBurgerCount = 0;
let cheeseBurgerSpelling = "Cheese Burger";
let meetPatty = null;
let isCheeseBurger = false;
let thenWhatIsIt = undefined;
let thisIsJust = Symbol("bunWithSource");

thenWhatIsIt = "somethingCanEat";

// Remember. 
// just like my cheeseburger doesn't have a meat patty, 
// there's no var.

Variables are data that can change bindings.

Can anyone explain bindings with my cheese-free cheeseburger?

Oh, mistakes. Because 'var' is a non-existent being, it should be called 'Letables'.

constants

const doesCheeseBurgerNeedMeetPatty = true;
const sayWhatCheeseBurgerNeed = "meet patty";

doesCheeseBurgerNeedMeetPatty = false; // eeeh. error.

Constants are data that can not change bindings. And It's an immutable truth that cheeseburgers need Meet Patty.

objects

const cheeseBurgerIngredients = ["bun", "ketchup", "onion", "pickle", "cheese", "meet patty", "bun"];
cheeseBurgerIngredients[3] = "jalapeño";

const food = {
  name: "CheeseBurger",
  ingredients: ["bun", "ketchup", "onion", "pickle", "cheese",  "bun"]
};
food.name = "noCheeseBurger";

Objects are different from regular letables. Can you see this absurdity? The cheeseburger is missing a meat patty, but it's still food, so there's no problem.

functions

function checkRealCheeseBurger(cheeseBurger) {
  let isCheeseBurger = cheeseBurger.hasMeetPatty;  
  return isCheeseBurger;
}

const checkRealCheeseBurgerAgain = function(cheeseBurger){
  let isCheeseBurger = cheeseBurger.hasMeetPatty;  
  return isCheeseBurger; 
};

const checkRealCheeseBurgerFinal = (cheeseBurger) => cheeseBurger.hasMeetPatty;

The function can be written in three forms. Even if my friend gets mad and says, "Don't say the same thing anymore!" there are two more ways to ask him or her.

The world calls this justice.

condition & loop

if (isCheeseBurger) {
  console.log("Good!");
} else {
  console.log("Nooo!");
}

for (let cheese = 0; cheese < 2; cheese++) {
  addExtraCheeseToCheeseBurger();
}

while (isCheeseBurger === false) {
  console.log("Nooooooo!");
}

ingredients.forEach(item => console.log(item));
for (const item of ingredients) {
  console.log(item);
}
for (const item in ingredients) {
  console.log(item);
}

operators

+,-,*,/,%,**
+=,-=,*=,/=,%=,**=
===,!==
>,<,<=,>=,

// ... blah, blah, and ...

typeof

Type error is like a farting that can come out laughing. I don't think so, but like anyone can go through it.

It's a very tragic thing. Slightly less than a cheeseburger without a meat patty.

class

class CheeseBurger {
  constructor(hasMeetPatty) {
    this.hasMeetPatty = hasMeetPatty;
  }

  checkMeetPatty(hasMeetPatty) {
    let reaction = hasMeetPatty ? "Good" : "Nooo";
    console.log(reaction);
  }
}

class CheeseBurgerYouBuy extends CheeseBurger {
  checkMeetPatty() {
    console.log(`no meet patty, no cheese burger.`);
  }
} // can be overriding and succession

DEV Community: Gyunam Park