3 ms·
Man, I really should revisit whether or not TinyMCE is still the best open source option
by skeptrune 3y ago
Man, I really should revisit whether or not TinyMCE is still the best open source option
- be_erik 3y agoQuill is already over 10 years old! I've deployed it in multiple applications with a lot of success.
- b33j0r 3y agoWhat a journey. Used it in production when I just needed arbitrary richtext documents in whole. Customizing has been harder than anyone would like. I became an event sourcing aficionado, initially to support parchment’s delta format. It’s a solid idea, but also required (unless you do backend diffs, which I tried too). My vanity test: I can’t believe how hard it still is to make a TODO checklist with indented levels. I try like every 18 months, surveying the plugin ecosystem. It never works well, so far. Editor.js isn’t a one-stop rtf editor, but that was the first thing I noticed “just working.” That said, I’m upgrading an old prototype to quill v2 today.
- ulrischa 3y agoI really like to hear about experience with Editor.js. It looks like the most modern editor but seems complicated. Is this true?
- mati365 3y agoWhat about CKeditor?
- bklyn11201 3y agoI much prefer to CKEditor to TinyMCE, but CKEditor has done a lot around licensing: https://ckeditor.com/legal/ckeditor-oss-license/ https://ckeditor.com/legal/ckeditor-oss-license/ They also modified their last CKEditor 4 open release to check the version and prompt the user to buy the LTS support.
- romanhn 3y agoTinyMCE just changed their licensing from MIT to GPL, which may impact your decision. Fun fact - TinyMCE and CKEditor are both owned by the same holding company (Tiugo Technologies).
- mbesto 3y agoCurious - whats the real life implication of using GPL in this case?
- romanhn 3y agoI'm not a lawyer, but it is my understanding that using a GPL library on the frontend triggers the "distrubution to users" clause of GPL. It's a strong copyleft license, turning the entire frontend portion of the application GPL-licensed, which means any user can now request the source code for it. That's an IP risk for any commercial code, and many companies shy away from GPL. Backend use of GPL should be fine since there's no distrubution (AGPL "fixes" this, and such libraries should just be avoided in commercial settings).