iter-ops VS Editor.js

I think I'm gonna stick with iter-ops, where I can use map without Promise resolution, so I can execute any resolution strategy described there.

So I’ve branched away from iter-ops, and into iter-ops-extras, coding away with no strings attached.

Is there a good reason to choose this solution over rxjs or iter-ops?

That's why I went an extra mile within iter-ops to provide such performance monitoring tools as pre-defined operators:

Someone posted this recently. Maybe it'll help?

P.S. I started within the esm branch there, but didn't make much progress. In case you want to re-use that branch ;)

Check out Aggregates, it explains why things like groupBy or sort aren't there.

JS supports functional programming very well, but I do miss a more native way of processing Iterators without adding a lib like iter-ops, since it is clunky (and a most likely a performance killer) converting Sets and Maps into Arrays back and forth.

I am supporting a project where lawyers, advisors can publish articles or news, to get more attention and clients. Initially it was made through TinyMCE, but they wanted not just HTML, but also a way of showing many pictures with interactions. I was seeking UI editor like Medium, and I guess best what I found was EditorJS and during checking its Awesome List there were several carousel plugins and I stopped on this.

We call it EmailBuilder.js – a powerful block-based email builder that takes the best parts of other open source libraries like Editor.js and email component libraries and puts them into an easy to use no-code builder.

I tried the "Doc", "Sheet" and "Slide" feature and each of them are incomplete and lacks most of the popular features. It would be better if the author uses existing solutions instead of implement them from ground up.

editor.js [0] for documents and Grist [1] for spreadsheet are some good examples.

[0]: https://editorjs.io/

Editorjs [https://editorjs.io/]

Use Gutenberg or a block editor like this (https://github.com/codex-team/editor.js) for a CMS. The WYSIWYG days are over.

Has anyone had any luck adding editor.js to your app? I've got a plain rails/stimulus/turbo/activeStorage app which needs a dynamic page builder and editor.js looks like it has promise. However it's a pretty specialized workflow and Im not sure if it jives well with the plain Rails ecosystem.

try this: https://editorjs.io/ might come handy, it's a very nice library and it's well maintained.