6 ms·

I do understand the frustration with syntax. The good thing is, none of that is finalised and we are in fact seeking people's idea of whats best. But one thing

I do understand the frustration with syntax. The good thing is, none of that is finalised and we are in fact seeking people's idea of whats best. But one thing that always holds on this subject is "tradeoffs"! It's an inconvenient word but we wouldn't do anything on the web without it. See also Evan You's talk on seeking that balance: https://youtu.be/ANtSWq-zI0s?si=fDbJLfA9T5VLvgsZ https://youtu.be/ANtSWq-zI0s?si=fDbJLfA9T5VLvgsZ. I'm happy to incorporate constructive feedback on this project, and it's early age affords us a great opportunity to do just that. So what's your thought on the challenge?: a native way to bind an element's css properties, class list, attributes, etc. to application data?

gloosx 3y ago
My thought is that it is a dead-end. You don't need to extend HTML with data binding. You need functions, and you need an appropriate language to write functions, it can be PHP, JS, but not weird HTML attributes.
- phrasecode 3y ago
  Thanks for your sharing your thoughts.
  - gloosx 3y ago
    Yeah, after revisiting it again and also checking out your article I find my comments a bit too harsh and functional-approach-biased. But I'm in general no fan of Svelte or Vue approaches – for me as a lifelong React junkie this is all extra complexity i hate. Maybe my brain is now rooted and wired in the React so deeply it cannot accept anything else, but when I try to do something with Vue, it is just screaming: Too hard! Too many redundant entities spawned around! I just need my function, my reducer and my side-effects and I can do everything with these three! Like, I want to do this: https://codesandbox.io/p/sandbox/strange-hofstadter-kd59k6 https://codesandbox.io/p/sandbox/strange-hofstadter-kd59k6 It is a beautiful functional example of React's power. How do I even do it in OOHtml or Vue or Svelte? I still can not learn.
    - phrasecode 3y ago
      I love how we can talk about differences and preferences here like this. Now, I can't wait to put my thoughts further together on the pros and cons of a HTML-first approach like OOHTML's vs a JS-first approach like React's and why there seem to be strong opinions either way. I'm happy to share a link under here when I do put that together.

gloosx 3y ago

My thought is that it is a dead-end. You don't need to extend HTML with data binding. You need functions, and you need an appropriate language to write functions, it can be PHP, JS, but not weird HTML attributes.

phrasecode 3y ago
Thanks for your sharing your thoughts.
- gloosx 3y ago
  Yeah, after revisiting it again and also checking out your article I find my comments a bit too harsh and functional-approach-biased. But I'm in general no fan of Svelte or Vue approaches – for me as a lifelong React junkie this is all extra complexity i hate. Maybe my brain is now rooted and wired in the React so deeply it cannot accept anything else, but when I try to do something with Vue, it is just screaming: Too hard! Too many redundant entities spawned around! I just need my function, my reducer and my side-effects and I can do everything with these three! Like, I want to do this: https://codesandbox.io/p/sandbox/strange-hofstadter-kd59k6 https://codesandbox.io/p/sandbox/strange-hofstadter-kd59k6 It is a beautiful functional example of React's power. How do I even do it in OOHtml or Vue or Svelte? I still can not learn.
  - phrasecode 3y ago
    I love how we can talk about differences and preferences here like this. Now, I can't wait to put my thoughts further together on the pros and cons of a HTML-first approach like OOHTML's vs a JS-first approach like React's and why there seem to be strong opinions either way. I'm happy to share a link under here when I do put that together.