Ask HN: Do any of you suffer from “front-end fatigue”?
This is not an attack on front end development as a craft, my intention is not to start a flame war here. But I look at the tooling and evolution of frameworks etc and I question to relevance of this whole thing. Also why doesn't this happen in backend/AI/systems engineering ? Curious to know your thoughts.
4 comments
Ah, based on some other comments, I think I see what you mean with fatigue, because you have to use HTML/CSS/JS or something that compiles into this like Clojurescript and you still have to know what javascript is and how it works to get anything useful done on the front-end. I am praying for a really slick alternative to come soon, where we can capture clicks and events and still keep some sanity with regards to layout, structure, and tying things into the backend via message passing.
What do you mean, designing interfaces or getting code and components to play nicely together?
I think the tooling on front-end vs. backend has something to do with the end of the pipeline. Backend systems can be developed using multiple languages and frameworks that will ultimately run on only one platform. Front-end can be developed with multiple languages, but will ultimately be transpiled to JavaScript and rendered as HTML/CSS. Front-end has to accommodate multiple platforms and browsers.
To me it also feels like the "modern" tooling for front-end is created for front-end developers by backend-developers.
To me it also feels like the "modern" tooling for front-end is created for front-end developers by backend-developers.
I find writing front-end code, and process of learning new APIs, tools, and frameworks to do it in different ways, immensely interesting. I find I have the opposite of fatigue; building interesting browser-based software actually energizes me.