5 ms·

Exactly. I've met too many front-end devs who are unable to separate the architectural pattern from the implementation of the library they are using. They have

Exactly. I've met too many front-end devs who are unable to separate the architectural pattern from the implementation of the library they are using. They have the larger mountain to climb when needing to learn a new framework.

edblarney 10y ago
"I've met too many front-end devs who are unable to separate the architectural pattern from the implementation of the library they are using." That's because front-end development is based on a core of HTML/CSS/JS which itself does not lend very well to architectural paradigms. People 'starting out' on the front-end, in some ways, never learn how to write propers software. They've been using weird ideas from the start.
- tpolischuk 10y ago
  That's actually kind of interesting. HTML/CSS/JS really are the framework. It's already a great separation of concerns (HTML for data/content, Javascript for behavior and logic, and CSS for presentation). Everything on top of it just seems like implementation details.
  - elmigranto 10y ago
    If you want to display documents, sure, I agree. If you need complex UIs, manually updating DOM without any kind of abstraction is definitely not a right choice.
  - ktRolster 10y ago
    No, CSS/HTML in theory is a good idea, separating content from presentation. In practice, the HTML still needs to know about the presentation.
- abritinthebay 10y ago
  I find that it's the people that don't know HTML/CSS that have the problems. They end up reinventing the wheel repeatedly. There's a whole lot of JavaScript devs out there that think they are front-end devs. They aren't. There's nothing wrong with that of course.
  - webmaven 10y ago
    > They end up reinventing the wheel repeatedly. You mean like altering attributes directly on elements (and proud that they had encapsulated the code in a reusable function) instead of adding/removing a class?

5 ms·

Exactly. I've met too many front-end devs who are unable to separate the architectural pattern from the implementation of the library they are using. They have

by bobbytherobot 10y ago

edblarney 10y ago
"I've met too many front-end devs who are unable to separate the architectural pattern from the implementation of the library they are using." That's because front-end development is based on a core of HTML/CSS/JS which itself does not lend very well to architectural paradigms. People 'starting out' on the front-end, in some ways, never learn how to write propers software. They've been using weird ideas from the start.
- tpolischuk 10y ago
  That's actually kind of interesting. HTML/CSS/JS really are the framework. It's already a great separation of concerns (HTML for data/content, Javascript for behavior and logic, and CSS for presentation). Everything on top of it just seems like implementation details.
  - elmigranto 10y ago
    If you want to display documents, sure, I agree. If you need complex UIs, manually updating DOM without any kind of abstraction is definitely not a right choice.
  - ktRolster 10y ago
    No, CSS/HTML in theory is a good idea, separating content from presentation. In practice, the HTML still needs to know about the presentation.
- abritinthebay 10y ago
  I find that it's the people that don't know HTML/CSS that have the problems. They end up reinventing the wheel repeatedly. There's a whole lot of JavaScript devs out there that think they are front-end devs. They aren't. There's nothing wrong with that of course.
  - webmaven 10y ago
    > They end up reinventing the wheel repeatedly. You mean like altering attributes directly on elements (and proud that they had encapsulated the code in a reusable function) instead of adding/removing a class?