3 ms·

To respond to OP's edit: frontend catches more shit because it's largely gotten worse at the same time as getting more complex. This isn't (only) outsiders look

To respond to OP's edit: frontend catches more shit because it's largely gotten worse at the same time as getting more complex. This isn't (only) outsiders looking in leveling that criticism—it's people who worked on GUI software in the 90s looking at the state of things and wondering why it's both constantly changing and, in many ways, worse than it was back then. Slower, worse tools producing slower, worse software, while constantly demanding that frontend developers run on a churn-treadmill for—it sure seems—no good reason. Backend suffers from some similar issues, but not to the same degree. Frontend seems to be subject not just to the effects of the apparently-eternal fat/thin client cycle, as the backend also is, but to some other pressures that lead it to be constantly changing but not really getting better, and even getting worse over time.

marcosdumay 4y ago
> frontend catches more shit because it's largely gotten worse at the same time as getting more complex. The "microservices by fad" based architecture usually comes with a huge decrease in performance and an even large one in reliability. The NoSQL for no reason fad came with horrible performance and some very bad data losses. Every once in a while we get some data leakage story here, certainly many are due to complexity (but nobody can tell which ones). Frontend is not alone suffering for the complexity.
- yamtaddle 4y ago
  > The "microservices by fad" based architecture usually comes with a huge decrease in performance and an even large one in reliability. Good point, that one was a big mess. > The NoSQL for no reason fad came with horrible performance and some very bad data losses. 100% agreed. My perception at the time, though, was that it was largely driven by frontend folks who'd come to the backend via NodeJS buying (especially) MongoDB's marketing hype. There was a real "finally, all those barriers the backend folks had for no reason whatsoever are gone and this is easy now—better, even, you dinosaur, have you seen the marketing, it makes it so clear that this is the future—so I can be full-stack without having to learn much!" vibe to the whole thing. But maybe that's just what I happened to see and that wasn't really the main cause of that going as far as it did.
deleted 4y ago
[deleted]

marcosdumay 4y ago

> frontend catches more shit because it's largely gotten worse at the same time as getting more complex. The "microservices by fad" based architecture usually comes with a huge decrease in performance and an even large one in reliability. The NoSQL for no reason fad came with horrible performance and some very bad data losses. Every once in a while we get some data leakage story here, certainly many are due to complexity (but nobody can tell which ones). Frontend is not alone suffering for the complexity.

yamtaddle 4y ago
> The "microservices by fad" based architecture usually comes with a huge decrease in performance and an even large one in reliability. Good point, that one was a big mess. > The NoSQL for no reason fad came with horrible performance and some very bad data losses. 100% agreed. My perception at the time, though, was that it was largely driven by frontend folks who'd come to the backend via NodeJS buying (especially) MongoDB's marketing hype. There was a real "finally, all those barriers the backend folks had for no reason whatsoever are gone and this is easy now—better, even, you dinosaur, have you seen the marketing, it makes it so clear that this is the future—so I can be full-stack without having to learn much!" vibe to the whole thing. But maybe that's just what I happened to see and that wasn't really the main cause of that going as far as it did.

deleted 4y ago

[deleted]