4 ms·

It fascinating that in 2019 we aren't able to get one text editor that would work seamlessly across all frameworks , but instead need to basically re-write huge

It fascinating that in 2019 we aren't able to get one text editor that would work seamlessly across all frameworks , but instead need to basically re-write huge "bindings" to support the reactivity and the rendering logic in each of them. Web Components have definitely failed.

marmada 7y ago
What does this have to do with Web Components? Even if you used Web Components you would still need to write bindings for each framework.
philippkuehn 7y ago
It's built on top of ProseMirror (plain JavaScript).
- dwaltrip 7y ago
  You only have 5 comments, all from today, and 2 of them were flagged dead. I couldn't see any reason why so I vouched for them. I am a bit confused about the situation though.
  - philippkuehn 7y ago
    Sorry I'm not very active here. Reading most of the time.
    - dwaltrip 7y ago
      Oh no worries at all. I was just curious why your comments were flagged, as they seemed perfectly fine.
      - philippkuehn 7y ago
        it's HN. that's why :)
        realty_geek 7y ago
        Shame that HN works like that. Anyway, upvoted your comments too ;) Thanks for creating tiptap, you rock!!!!
pxtail 7y ago
Same thing goes about almost all controls and UI elements existing inside web browsers. I'm around web development for years and it's very saddening and heart breaking for me to see all this milling around in one place, round and round and results are not that much different. Sometimes I really, really dread this whole "frontend" related churn, tooling, javascript and it's quirks. I looked at Flutter recently wondering - maybe this is the answer? But this probably is just another turn of the wheel, it was attempted already in the past with adobe air/flex and many other projects. Maybe reason for this is that programming and whole IT is very young craft, mere child's play compared to different industries like for example construction which has thousands years of history, trials, successes and errors.
- luckydata 7y ago
  the web is a really poor abstraction for building UIs and it's kinda incredible that we collectively don't internalize that simple lesson. We have hacked to death a platform for linked text documents because it's what everyone has, that's the extent of the merits of the web platform, but it's not a good fit for what we're trying to do in the productivity world. Flex for example was leaps and bounds better in that regard, and any desktop OS is too. Javascript is a poorly designed language that we beat into submission by working around its many, many flaws. We keep making this mistake of wanting to use what's available instead of coming together to build something better, so we waste MILLIONS of collective hours because we're dumb.
zemptime 7y ago
While I agree we (as in the internet at large) haven't solved the text editor problem, by saying "web components have failed" you're concluding in bad faith. If such a "universal rich text edit" web component comes out, have web components then succeeded? Then failure isn't such a permanent state as your comment implies, rather an indication of work yet to be done. Unless you'd like to clarify more, your comment seems to me like you're flinging mud without being able to back it up. What's the reason for that? Of note, Trix has been using the `customElements` standard since forever: https://github.com/basecamp/trix/ https://github.com/basecamp/trix/ There's also slate, the (old!) tinymce, umm... I know I've at least experimented with a good couple more I can't recall. And, on the topic of components I wish existed (anywhere - react, vue, angular, etc - anything), I've been searching for a good rich multiselect for a long time! If you know of any please let me know :)
- deergomoo 7y ago
  > And, on the topic of components I wish existed (anywhere - react, vue, angular, etc - anything), I've been searching for a good rich multiselect for a long time! If you know of any please let me know :) Select2 [1] has been around forever but it's always worked out pretty nicely for me. It's a jQuery plugin, so it's somewhat out of vogue these days, but it's trivially easy to wrap it in a component to make it play nicely with Vue (in fact, the Vue documentation uses it as the example for writing wrapper components [2]). I imagine something similar can be done with React, Angular, etc., though I'm not too familiar with the process there. [1] https://select2.org https://select2.org [2] https://vuejs.org/v2/examples/select2.html https://vuejs.org/v2/examples/select2.html
  - dpau 7y ago
    not that there's anything wrong with jquery or select2, both of which i used heavily in the past, but if you're working in vue it's a very nice feeling to just completely drop the jquery dependency. ive been using https://github.com/shentao/vue-multiselect https://github.com/shentao/vue-multiselect for over a year now in production and despite its quirks i'd recommend it.

marmada 7y ago

What does this have to do with Web Components? Even if you used Web Components you would still need to write bindings for each framework.

philippkuehn 7y ago

It's built on top of ProseMirror (plain JavaScript).

dwaltrip 7y ago
You only have 5 comments, all from today, and 2 of them were flagged dead. I couldn't see any reason why so I vouched for them. I am a bit confused about the situation though.
- philippkuehn 7y ago
  Sorry I'm not very active here. Reading most of the time.
  - dwaltrip 7y ago
    Oh no worries at all. I was just curious why your comments were flagged, as they seemed perfectly fine.
    - philippkuehn 7y ago
      it's HN. that's why :)
      - realty_geek 7y ago
        Shame that HN works like that. Anyway, upvoted your comments too ;) Thanks for creating tiptap, you rock!!!!

pxtail 7y ago

Same thing goes about almost all controls and UI elements existing inside web browsers. I'm around web development for years and it's very saddening and heart breaking for me to see all this milling around in one place, round and round and results are not that much different. Sometimes I really, really dread this whole "frontend" related churn, tooling, javascript and it's quirks. I looked at Flutter recently wondering - maybe this is the answer? But this probably is just another turn of the wheel, it was attempted already in the past with adobe air/flex and many other projects. Maybe reason for this is that programming and whole IT is very young craft, mere child's play compared to different industries like for example construction which has thousands years of history, trials, successes and errors.

luckydata 7y ago
the web is a really poor abstraction for building UIs and it's kinda incredible that we collectively don't internalize that simple lesson. We have hacked to death a platform for linked text documents because it's what everyone has, that's the extent of the merits of the web platform, but it's not a good fit for what we're trying to do in the productivity world. Flex for example was leaps and bounds better in that regard, and any desktop OS is too. Javascript is a poorly designed language that we beat into submission by working around its many, many flaws. We keep making this mistake of wanting to use what's available instead of coming together to build something better, so we waste MILLIONS of collective hours because we're dumb.

zemptime 7y ago

While I agree we (as in the internet at large) haven't solved the text editor problem, by saying "web components have failed" you're concluding in bad faith. If such a "universal rich text edit" web component comes out, have web components then succeeded? Then failure isn't such a permanent state as your comment implies, rather an indication of work yet to be done. Unless you'd like to clarify more, your comment seems to me like you're flinging mud without being able to back it up. What's the reason for that? Of note, Trix has been using the `customElements` standard since forever: https://github.com/basecamp/trix/ https://github.com/basecamp/trix/ There's also slate, the (old!) tinymce, umm... I know I've at least experimented with a good couple more I can't recall. And, on the topic of components I wish existed (anywhere - react, vue, angular, etc - anything), I've been searching for a good rich multiselect for a long time! If you know of any please let me know :)

deergomoo 7y ago
> And, on the topic of components I wish existed (anywhere - react, vue, angular, etc - anything), I've been searching for a good rich multiselect for a long time! If you know of any please let me know :) Select2 [1] has been around forever but it's always worked out pretty nicely for me. It's a jQuery plugin, so it's somewhat out of vogue these days, but it's trivially easy to wrap it in a component to make it play nicely with Vue (in fact, the Vue documentation uses it as the example for writing wrapper components [2]). I imagine something similar can be done with React, Angular, etc., though I'm not too familiar with the process there. [1] https://select2.org https://select2.org [2] https://vuejs.org/v2/examples/select2.html https://vuejs.org/v2/examples/select2.html
- dpau 7y ago
  not that there's anything wrong with jquery or select2, both of which i used heavily in the past, but if you're working in vue it's a very nice feeling to just completely drop the jquery dependency. ive been using https://github.com/shentao/vue-multiselect https://github.com/shentao/vue-multiselect for over a year now in production and despite its quirks i'd recommend it.