Live data from Hacker News

Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

news.ycombinator.com

11–20 of 105 posts

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#11
post #2

Since Tiptap is built on top of ProseMirror, do you contribute funds to support ProseMirror's development?

Since the last few weeks we are focusing on the development of Tiptap. We definitely want to have a solid foundation, so we will support the projects we rely on. Without their work, Tiptap wouldn't be possible.

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#12
post #4

Can you explain more about how Tiptap’s concepts extend or replace ProseMirror’s concepts? A few years ago I evaluated rebasing Notion’s editor on various editor frameworks. ProseMirror came out at the top of my list, but I wasn’t sure how to rank TipTap. Having more batteries included is good, but I’ve found that layers of abstraction can really get in the way. For example if I need to fix a bug with Android Gboard…

I'm not part of the TipTap team but I think I can help answer this.

Think of it like this... you're basically only coupling yourself to ProseMirror. That's the schema you're storing in your database. TipTap is a set of libraries that you can use for your web app etc... but if you ever find it insufficient, you're free to role your own thing.

ProseMirror has been around for a long time and is unlikely to be going anywhere, but having a company with VC funding using it as its base helps ensure that if ProseMirror got abandoned, it'd likely get picked back up by TipTap or some other interested party.

Even if you're building your own editor, unless your editor has a need that ProseMirror's schema doesn't account for or solve it makes sense to use it.

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#13
post #9

I use Tip Tap in SvelteKit and I like it a lot. I'm really glad I chose it over Lexical and other options. Congrats on the recent YC funding! Nice to see a player in this space that isn't from Facebook/React dominant. The only issue I have encountered with it that I haven't solved yet (I think there are multiple potential paths) is validating/sanitizing data with it. To parse the content and turn it into raw text req…

> I'm really glad I chose it over Lexical and other options. Congrats

Do you mind expanding on this? I've been comparing the two and found the lexical data model easier to understand.

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#14
About three years ago I was looking for an editor and while TinyMCE was the absolute best, its pricing model was as bad as CKEditor's, so I ended up testing Tiptap in a Vue project.

It's really a great and flexible editor, with a couple of rough corners, but overall the only serious alternative to the above-mentioned editors. And since it has a sensible licensing model it is an overall good choice.

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#15
post #14

About three years ago I was looking for an editor and while TinyMCE was the absolute best, its pricing model was as bad as CKEditor's, so I ended up testing Tiptap in a Vue project. It's really a great and flexible editor, with a couple of rough corners, but overall the only serious alternative to the above-mentioned editors. And since it has a sensible licensing model it is an overall good choice.

As we continue to improve Tiptap, we would be interested in more details about the "rough corners". Do you have any examples?

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#16

> The Tiptap AI integration beta is a service where you connect your OpenAI API key to our backend and install the Tiptap editor AI extension to get AI writing experience in your editor. Here’s a demo: https://ai-demo.tiptap.dev/ Congrats, any plan on supporting code/monaco and autocompletion? We had to rebuild it ourselves on top of yjs and gpt4 for windmill.dev and would have happily built it on a service if it exi…

Tiptap AI is still in it’s early stages and we are constantly thinking about how to improve the DX and UX. Autocompletion for text is already working quite well. Our next goals are streaming support for all commands and providing a SDK. Tiptap is primarily a framework for text editing, but we’ll definitely keep an eye on your use cases.

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#18
post #2

Since Tiptap is built on top of ProseMirror, do you contribute funds to support ProseMirror's development?

[flagged]

I was just curious given that ProseMirror is used a lot and doesn't seem that well supported financially.

> We are all constantly building products on other products, given a license that allows for that, without contributing work or money to the products.

This type of attitude is pretty harmful for open source. Folks (especially companies) should support their key dependencies where they can.

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#19
I wish the cheapest non-free tier was cheaper, but I totally agree that building an editor with all the features listed is very time consuming. I love that you are working to tackle this issue!

If I had one request, it would be instead of making me jump from $0 to $150 a month, have a usage-based model similar to OpenAI or Firebase, with functionality so I could cap costs to say $15 a month.

Re: Launch HN: Tiptap (YC S23) – Toolkit for developing collaborative editors

#20
post #9

I use Tip Tap in SvelteKit and I like it a lot. I'm really glad I chose it over Lexical and other options. Congrats on the recent YC funding! Nice to see a player in this space that isn't from Facebook/React dominant. The only issue I have encountered with it that I haven't solved yet (I think there are multiple potential paths) is validating/sanitizing data with it. To parse the content and turn it into raw text req…

> I'm really glad I chose it over Lexical and other options. Congrats Do you mind expanding on this? I've been comparing the two and found the lexical data model easier to understand.

Have you tried using Lexical? I found it to be very buggy and ended up replacing it with Quill.
Post reply on HN