Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Switching Rich Text Editors, Part 1: Picking Tiptap

ashbyhq.com

Post reply on HN
Print view View original

31–40 of 54 posts

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#31

Post by earthboundkid »

rambambram wrote: post #5

Ah, the joy and horror of rich text editors. I completely understand the selling points and the attraction, but I gave up on 'm for my projects. Not saying that OP must do the same, though. I eventually settled for plain text in a simple textarea, with basic possibilities for markup by allowing Markdown. No more struggling with different browsers, no struggling with how the RTE looks and feels, no incompatibility iss…

Another opt-out route, which I am currently going down, is using Google Docs as an RTE and then just doing a good job of importing from it.

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#33

Post by evnp »

I'm glad OP didn't end up recommending Quill, though their representation of that library seems way off. To help others avoid the state we're currently in, a PSA:

https://github.com/quilljs/quill/issues/3359 ("Is quill dead?") Multiple open CVE with no plans to address, 1.1k open issues.

We're on the lookout for better options and a way forward, so apart from that this post is much appreciated!

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#34

Post by amelius »

rambambram wrote: post #5

Ah, the joy and horror of rich text editors. I completely understand the selling points and the attraction, but I gave up on 'm for my projects. Not saying that OP must do the same, though. I eventually settled for plain text in a simple textarea, with basic possibilities for markup by allowing Markdown. No more struggling with different browsers, no struggling with how the RTE looks and feels, no incompatibility iss…

> Ah, the joy and horror of rich text editors.

The problem: there is no money to be made in writing software libraries these days, no matter how much a working solution is needed. So sadly, we're going to be stuck with all these suboptimal solutions for many years to come.

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#35

Post by kyawzazaw »

gadders wrote: post #26

What does Ashby actually do as a company? It might be my locked down corporate network but I can't find a description anywhere.

A lot of companies use it currently as a job application submission. At least from what I know.

I guess they have a product that is similar to lever or greenhouse atm

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#36

Post by rambambram »

amelius wrote: post #34
rambambram wrote: post #5

Ah, the joy and horror of rich text editors. I completely understand the selling points and the attraction, but I gave up on 'm for my projects. Not saying that OP must do the same, though. I eventually settled for plain text in a simple textarea, with basic possibilities for markup by allowing Markdown. No more struggling with different browsers, no struggling with how the RTE looks and feels, no incompatibility iss…

> Ah, the joy and horror of rich text editors. The problem: there is no money to be made in writing software libraries these days, no matter how much a working solution is needed. So sadly, we're going to be stuck with all these suboptimal solutions for many years to come.

Maybe that's true. A lot of people tried the RTE stuff, and Basecamp/37Signals came close with a solution (I forgot the name). I guess it's a hard problem by definition, dealing with copypasted stuff from Word, dealing with browsers, etc. After using my simple Markdown solution for some years now, I came to appreciate the bare basic style of it. But it's not for every use case.

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#37

Post by hanspagel »

mtlynch wrote: post #12

I use TipTap as a rich text editor in my open-source weekly journaling app.[0] One of the big gotchas I've had with TipTap is that it's extremely sluggish once you get to more than 300 words or so and you're using different formatting options. There's a multi-second delay between typing the word and the text appearing in the screen. The APIs are pretty nice, and I was able to convert to/from Markdown with it easier t…

Try disabling spellcheck, this has serious performance issues for content editable in recent chrome versions.

https://bugs.chromium.org/p/chromium/issues/detail?id=107671...

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#39

Post by hanspagel »

gilli wrote: post #7

I've been using Tiptap for my little brand design app ( https://baseline.is ) and it's been awesome to work with. The guys over at Überdosis are constantly working on it making it even more powerful and you can easily bend it to your will, which is very necessary in my case since I'm using it as a part of a design tool. I would definitely recommend it to pretty much anyone since you can adapt it to your needs.

Thanks gilli! Great to have you in the community. (Tiptap co-creator here)

Re: Switching Rich Text Editors, Part 1: Picking Tiptap

#40

Post by pqb »

Great article and fantastic choice!

This is a topic I have been very interested lately. I had been lucky to start using since Slate 0.61.x, but I cannot say anything good about it. It has a major problem with managing large documents [0]. I tried to introduce multiple improvements of performance, but it is very ungrateful project – change in one place affects many things at the same time. I am shocked, how many projects are still using it. For example, open-sourced Notabase [1]. My 4+ weeks with Slate.js completely killed motivation, and I was only thinking to put a whole project to litter.

In the result of being unhappy, I switched to Draft.js. It was 2020, and I was eager to try it out, so I did. Sadly, in 2020 there was also the last release [2]. Initially, I didn't like how it works. I preferred the Slate data model. Also, the draft.js project felt not maintained at that time (by looking at commits activity, issues and pull-requests). It is written in the Flow which I detest. I spent few weeks to try "merge" the draft.js and sentry with doing a "rewrite" to TypeScript. Obviously, quickly I realized myself it is stupid idea.

Then, I took a look at ReMirror. Yet another problem that was struggling with maintenance and active contributors. It is based on ProseMirror, so I thought it is better choice than previous. ReMirror is overly complex for simple things. It was hard to find any help - neither by googling examples nor via ReMirror's Discord (it was dead silence there).

After that, I have found information about the TipTap. Back then, there was only provided support for Vue.js. Fortunately, it was that time, when they have promised the v2 with React support. I skipped it to wait for the new version.

Maybe, a raw ProseMirror with React? Yep, tried it, but I wasn't very happy of the result. I knew the TipTap v2 will be released and there were already existing projects that were using ProseMirror behind the scene, for example: Outline's rich-markdown-editor[3]. It has tons of built-in components that I had with Slate. I was extremely happy about it, because "everything what I needed" was there – typical bold, italic, code, code block, quote, multi-level list and even table editing. Really awesome piece of code! However, authors decided they are opting for TipTap and they have archived repository on GitHub, which means officially the project is dead.

I had no time to test Quill.js. It looked interesting, but it has noticeable poor development pace, and it looks a dead project with many bugs.

Currently, I am using the TipTap v2 and I can't say how happy I am now. I guess I will stick with it for longer. However, I know the journey to find the best Rich Text Editor has not ended :sweat-emoji:. There are more alternatives, for example Stylo [4] that I've found in this week.

[0] Try to copy the contents of https://www.slatejs.org/examples/huge-document and paste it back. In a result, my Firefox on Macbook M1 hangs.

[1]: https://notabase.io/

[2]: https://github.com/facebook/draft-js/releases/tag/v0.11.7

[3]: https://github.com/outline/rich-markdown-editor

[4]: https://stylojs.com/

Post reply on HN