Front-End Dissatisfaction (and Backing Off)

Asko Nõmm recently voiced their frustration with front-end development: They cited the constant influx of new JavaScript frameworks and tools, leading to a feeling of being perpetually overwhelmed and irrelevant. The joy, they said, was gone. Their solution? Resigning from their current position and pursuing an exclusively back-end role.

While back-end development might not be entirely immune to technological churn, the frequency of complaints seems significantly lower. The pervasive dissatisfaction with the front-end landscape is undeniable.

Remy Sharp offered a counterpoint in their article, "The web didn’t change; you did," suggesting that the complexity is self-imposed. While acknowledging that developers often lack control over their tech stack, Sharp highlights the continued viability of simpler approaches.

Marc (surname withheld), echoes this sentiment, advocating for the enduring power of plain HTML, particularly for personal websites. This view is supported by Steren Giannini and Terence Eden, who both champion the effectiveness of HTML-only development, particularly for critical applications where simplicity and accessibility are paramount. Eden specifically emphasizes the suitability of HTML, with minimal CSS and optional JavaScript enhancements, for public services and emergency applications.

My own perspective is one of balanced pragmatism. I recognize the potential for both excessive complexity and the value of simpler approaches. The key lies in consciously choosing the right level of complexity based on project requirements, understanding the trade-offs between speed, features, developer experience, and user experience.

The above is the detailed content of Front-End Dissatisfaction (and Backing Off). For more information, please follow other related articles on the PHP Chinese website!