3 ms·
Does seem very neat and I like the proposal except for the idea that all JS/CSS/HTML are all contained in the same code... that to me seems like a recipe for he
by josscrowcroft 15y ago
Does seem very neat and I like the proposal except for the idea that all JS/CSS/HTML are all contained in the same code... that to me seems like a recipe for headaches down the line, even if it does speed up initial development.
- arturadib 15y agoHey there, I think it's actually the other way around -- down the line, I will appreciate the fact that all that stuff is right within the object I need to work on. There's no need to go around multiple HTML/CSS/JS files looking for the ids/classes I need to maintain. It's all right there. (I agree that the need for a backslash is annoying, but the tradeoff is favorable in my opinion). That being said, you don't have to use in-object CSS, and very soon we'll be relaxing the HTML requirement as well.
- rufugee 15y agoI kind of like that idea as well, although the escaping is a little ugly. The purist in me wishes I was always dealing with objects which knew how to display themselves and behave. Then I'd simply be an object arranger/orchestrator and life would be simple. What is wrong with this approach really?
- jpadvo 15y agoIf you use this with Coffeescript, you don't need the backslashes. :)
- yaix 15y agoThat is actually one part I liked, especially the HTML. For bigger projects I would do the development of different parts of the app in different JS files and have a server side script combine them when requested from a web browser.