Is separation of concerns a goal or a lie?

"One way we can handle code that's too long is to separate it into different files - HTML for the content, CSS for the styles and JavaScript (js files) for functions. This way you can more easily separate the different areas you're dealing with: HTML for the structure, CSS when you handle the design and JavaScript when you handle the hardcore programming stuff."

"For years I didn't understand why React or Tailwind worked in the way they did, I felt frustrated because every little thing seemed to require more work then in plain JavaScript or CSS. I didn't think those frameworks save me much time or work in the long run and I was annoyed that I had to use them every day."

Early web development relied on clean HTML, vanilla JavaScript, and pure CSS with minimal frameworks such as jQuery. Frameworks like React and Tailwind later became common in team projects to keep everyone aligned. Developers often find frameworks initially more work compared with plain JavaScript or CSS and may not see immediate time savings. The concept of separation of concerns frames frameworks' benefits by splitting complex problems into smaller, manageable concerns. Practical separation involves dividing structure, presentation, and behavior: HTML for content and structure, CSS for styles and design, and JavaScript for functionality, which improves clarity and team collaboration.

Read at Medium