3 ms·

I'd be interested in hearing what you think about the article I linked then. Jade is so close to Hiccup, except you can use it alongside your code. Jade/Handl

I'd be interested in hearing what you think about the article I linked then. Jade is so close to Hiccup, except you can use it alongside your code. Jade/Handlebars don't map to React components.

notNow 11y ago
Jade can be used along with code too. I think that you mean view logic by code here as mixing business logic with your view is a big no no. I took a look at Hiccup. It looks interesting and promising but I'm an indentation oriented developer and that's why I favor Jade and Sass and the likes. Also, I like the design philosophy that they chose with Jade by absorbing JS in HTML and not the other way around like in JSX where HTML & CSS being subordinates to JS thus making the process a whole lot more tedious and time-consuming.
undershirt 11y ago
to Notnow: > Jade can be used along with code too. I think that you mean view logic by code here as mixing business logic with your view is a big no no. Code is data. Separating concerns by using different technologies to solve the same problem is not simplification. You can separate views from logic as you would separate different functions in code. We can organize that. > I took a look at Hiccup. It looks interesting and promising but I'm an indentation oriented developer and that's why I favor Jade and Sass and the likes. Not liking Hiccup because you prefer indentation doesn't make sense. Hiccup is indented by convention. If you're speaking about the delimiters, those are what keeps it from slipping into limitations shared by JS, Jade, etc. > Also, I like the design philosophy that they chose with Jade by absorbing JS in HTML and not the other way around like in JSX where HTML & CSS being subordinates to JS thus making the process a whole lot more tedious and time-consuming. You don't need to choose an absorption direction between JS and HTML if you treat HTML as what it is, a nested data tree, and realize that templating is the mixing of logic into this data tree. S-expressions in Lisp were designed exactly for this.

I'd be interested in hearing what you think about the article I linked then. Jade is so close to Hiccup, except you can use it alongside your code. Jade/Handlebars don't map to React components.

notNow 11y ago

Jade can be used along with code too. I think that you mean view logic by code here as mixing business logic with your view is a big no no. I took a look at Hiccup. It looks interesting and promising but I'm an indentation oriented developer and that's why I favor Jade and Sass and the likes. Also, I like the design philosophy that they chose with Jade by absorbing JS in HTML and not the other way around like in JSX where HTML & CSS being subordinates to JS thus making the process a whole lot more tedious and time-consuming.

undershirt 11y ago

to Notnow: > Jade can be used along with code too. I think that you mean view logic by code here as mixing business logic with your view is a big no no. Code is data. Separating concerns by using different technologies to solve the same problem is not simplification. You can separate views from logic as you would separate different functions in code. We can organize that. > I took a look at Hiccup. It looks interesting and promising but I'm an indentation oriented developer and that's why I favor Jade and Sass and the likes. Not liking Hiccup because you prefer indentation doesn't make sense. Hiccup is indented by convention. If you're speaking about the delimiters, those are what keeps it from slipping into limitations shared by JS, Jade, etc. > Also, I like the design philosophy that they chose with Jade by absorbing JS in HTML and not the other way around like in JSX where HTML & CSS being subordinates to JS thus making the process a whole lot more tedious and time-consuming. You don't need to choose an absorption direction between JS and HTML if you treat HTML as what it is, a nested data tree, and realize that templating is the mixing of logic into this data tree. S-expressions in Lisp were designed exactly for this.