No more CSS and HTML, just JS
What problem is ojjs solving and what are the trade-offs?<p>For me personally, the design principle of "separation of concerns" has always worked well, especially in a team environment. Having a pure designer (on photoshop or illustrator), then an html/css expert for coding pages and finally a programmer for adding dynamic content works out as a nice pipeline for web development. With ojjs, the programmer and html/css person would have blurred lines separating their responsibilities. It is a cool project, but it seems like a step backwards to me. Maybe it's just a step sideways or a better way of doing things for a team consisting entirely of programmers.<p><a href="https://en.wikipedia.org/wiki/Separation_of_concerns" rel="nofollow">https://en.wikipedia.org/wiki/Separation_of_concerns</a>