index_advisor VS quill

pghero and/or https://github.com/supabase/index_advisor

If you want to pay for a saas then pganalyze is like $400 a month for 4 dbs is a pretty good pricing model

The Supabase Index Advisor is now available inside Supabase Studio. We've integrated the Index Advisor into our existing Query Performance tool so that you can find your slowest queries and check recommendations. As its name suggests, this analyzes your queries and make recommendations to add or remove table indexes.

2. Copy/paste the plpgsql file:

https://github.com/supabase/index_advisor/blob/main/index_ad...

We are also developing the Trusted Language Extension with the RDS team, so at some point it should be easier to do this through database.dev:

https://database.dev/olirice/index_advisor

Speaking of text, here's another one for you. Quill is a rich text editor also built for compatibility and extensibility. The latest version prevents mistakenly overriding theme default toolbar settings, and Quill is now a valid ESM package for better ecosystem. There's nested Quill support, improved spelling support, and improved support for pasting from Google Docs and Microsoft Word. Check out all the changes on the Slab website.

Ontop of that this [issue](https://github.com/quilljs/quill/issues/3806) exists - which forces us to upgrade once primeNg lets us. Anyone knows a good alternative? I am done with quill and would love to use something more stable.

I started with Quill... wound up hitting lots of challenges. There are bugs/issues like, "don't add extra margin or it will be converted to extra spaces." I also struggled to embed Quill into an HTML form element, which I though would be easy.

Fair enough. Look maybe into more of a utility like Quill? https://quilljs.com/

I agree. Yes, you can. Quill is the example here.

Actually, back in 2015 when we started prototyping CKEditor 5, we started with this approach as well. Our goal from the beginning was to combine real-time editing capabilities with an engine capable of storing and rendering complex rich-text structures (nested tables, complex nested lists, other rich widgets, etc.). We quickly realized that a linear structure is going to be a huge bottleneck. In the end, if you want to represent trees, storing them as a linear structure is counterproductive.

So, we went for a tree model. That got many things in the engine an order of magnitude harder (OT being one). But I choose to encapsulate this complexity in the model rather than make it leak to particular plugins.

In fact, from what I remember, https://github.com/quilljs/quill/issues/117 (e.g. https://github.com/quilljs/quill/issues/117#issuecomment-644...) is a good example of issues that we avoided.

I also talked to companies that built their platforms on top of Quill. One of them ended up gluing together countless Quill instances to power their editor and overcome the limitations of the linear data model but is now looking for a way to rebuild their editor from scratch due to the issues (performance, complexity, stability).

So, yes. You can implement a rich-text editor based on a linear model. But it has its immediate limitations that you need to take into consideration.

I've always used Quill and always satisfied with it. It can be adapted to React Native as well. Despite the most popular RTE is Draft js it has some limitations on mobile.

NgPrime has this editor if you’re using it already for components. Or Quil could work

Quill