Re:Ask HN: Why did Frontend development explode in complexity?
by peterhunt on Monday January 02, 2023 @12:33PM
(#34220772)
I didn’t say they were meaningless, just that they are often overused and can make systems needlessly more complex.
How many microservices architectures with dependent webs of async queues emulating distributed transaction semantics could be replaced by one big rdbms? I think a lot!
Re:Ask HN: Why did Frontend development explode in complexity?
by taeric on Monday January 02, 2023 @12:42PM
(#34220920)
My favorite is when a new project thinks it needs this on day one. I'm willing to place money that most new projects will struggle to saturate a single computer. Much less a distributed infrastructure. (yes, I'm well aware there are some cases. But even most fang projects are doing relatively little work, all told.)
Re:Ask HN: Why did Frontend development explode in complexity?
by ericlewis on Monday January 02, 2023 @01:08PM
(#34221323)
Chime famously (but maybe not externally) ran almost all infra off two co-located beefy servers all the way up to their millionth customer. Maybe that is dumb, but we never had any downtime or slowness that was a result of work we did. The APIs we would rely on sometimes though did.
Re:Ask HN: Why did Frontend development explode in complexity?
by z3t4 on Monday January 02, 2023 @02:38PM
(#34222585)
* * *
Re:Ask HN: Why did Frontend development explode in complexity?
by taeric on Monday January 02, 2023 @04:30PM
(#34223935)
You aren't wrong, but I suspect there was more unnecessary complexity in early computers then you'd allow. Is why don't ridiculous demo scene stuff is still created today. :)
Re:Ask HN: Why did Frontend development explode in complexity?
by torginus on Monday January 02, 2023 @04:50PM
(#34224155)
It's just so ironic to see this monstrous amount of complexity that is only made tolerable by the massively overpowered hardware beneath it, and which, reduces the throughput of said hardware enough that said complexity becomes necessary.
If you can't see the advantage of keeping your processors fed with work as close to 100% of the time as humanly possible, I got nothing for ya. Hell, AWS is basically popular because you can have novice programmers toss up synchronously programmed lambdas, and scale out the underlying infrastructure with Amazon magic, which in a non-AWS system translates to "define queue and message format which will be servicing producer/consumer workers, deploy and start dumping messages in/popping messages out of said queue; scale to taste.
It takes a while to wrap your head around async, but once you get there, you're building with one of the most powerful computing primitives I've yet to come across.
It's just unfortunate that the language and requisite mental model around it is, in my experience, a bit difficult to intuitively reach.