Tiptap 将10个以前的专业扩展以MIT许可证开源。
嗨,HN,截至六月底,我们将开源一系列曾经属于付费版本的扩展。这些扩展将以MIT许可证免费提供,包括表情符号支持、拖动手柄、隐形字符、数学处理、文件处理等功能。完整列表见下文。
我们几年前创建Tiptap,是因为对现代应用的富文本编辑器现状感到沮丧。大多数编辑器要么功能有限,要么过于僵化,或者试图通过单一的设置解决所有问题。我们希望有一个更具可组合性和框架友好的解决方案,因此我们进行了开发。
最初,我们通过销售单个“专业”扩展来实现盈利。起初这种方式有效,但随着时间的推移,我们意识到这些小功能并不是我们真正的价值所在。它们是常见需求,但并不是我们的竞争壁垒。与此同时,我们专注于更大的功能包(如协作编辑、AI辅助内容、文档等),这些功能包能够解决完整的问题,并包括后端基础设施、用户界面组件和集成逻辑。
同时,我们已经停止了Tiptap Cloud的免费版本(其中包含这些扩展),并改为限时免费试用。这并不是一个容易的决定,但它帮助我们保持可持续发展,同时仍然支持项目的开源部分,并围绕其构建生态系统和平台。
我们选择MIT许可证而不是更具限制性的许可证,因为我们不希望开发者在商业工作或副项目中使用这些扩展时感到担忧。这种自由对我们来说非常重要。我们的核心编辑器和这些扩展将保持开放。付费功能现在以明确的捆绑形式存在,关联到实际的产品成果。
以下是免费的开源内容:
```
- Details, DetailsContent, DetailsSummary
- Emoji
- DragHandle (React 和 Vue)
- FileHandler
- InvisibleCharacters
- Mathematics
- TableOfContents
- UniqueID
```
欢迎提问,或者分享你的想法。我很好奇其他人是如何处理类似的许可证变更,或者在开源与商业目标之间是否有类似的权衡。
谢谢,
Philip
查看原文
Hi HN, as of the end of June, we’re open-sourcing a bunch of extensions that used to be part of our paid tier. They’ll be available for free under the MIT license. These include things like emoji support, drag handles, invisible characters, math, file handling, and more. Full list is at the bottom.<p>We started Tiptap a few years ago because we were frustrated by the state of rich text editors for modern apps. Most were either too limited, too rigid, or tried to solve everything with a monolithic setup. We wanted something more composable and framework-friendly, so we built it.<p>We originally monetized by selling individual “Pro” extensions. That worked early on, but over time we realized these smaller pieces weren’t where our value was. They were common needs, but not really our moat. In the meantime we’re focusing on larger feature bundles (like collaborative editing, AI-assisted content, documents, etc) that solve complete problems and include backend infra, UI components, and integration logic.<p>At the same time, we’ve sunset the free tier of Tiptap Cloud (where those extensions were included) and switched to a time-limited free trial. That wasn’t an easy call, but it helps us keep things sustainable while still supporting the open source side of the project and build the ecosystem and platform around.<p>We chose MIT over more restrictive licenses because we don’t want developers to worry about using these extensions in commercial work or side projects. That freedom is important to us. We’ll keep our core editor and these extensions open. The paid features now live in well-defined bundles tied to real product outcomes.<p>Here’s what’s free and open:<p><pre><code> - Details, DetailsContent, DetailsSummary
- Emoji
- DragHandle (React and Vue)
- FileHandler
- InvisibleCharacters
- Mathematics
- TableOfContents
- UniqueID
</code></pre>
Happy to answer questions, or just hear what you think. Curious how other folks have handled licensing shifts like this, or if you’ve had similar tradeoffs in open source vs. business goals.<p>Thanks,
Philip