Improving the UX of extension install, and Butterfly

I'm only sharing our experience and approach, not arguing in any particular direction for the CS&S distribution, especially given that our approach is optimized for our "hosted-multi-user" use case.


We actually dropped extension support a while back in favor of either integrating features into core or making them API clients/integrations. Prior to that we did implement API versioning, support for multiply versioned GREL runtimes and two SDKs as new surface areas for integrations. This allowed us to keep the internals (and most importantly dependencies!) free from integrations, it was a complete game changer for maintenance of "core".

It might be tricky for the CS&S distribution given local installs but maybe it could be possible if there was some broker protocol in place?

I am commenting here since this is the thread where we discussed the DEF grant. Our application was not selected for funding. the Data Empowerment Fund (DEF) did not share more details as they received over 800 eligible applications.

I open PR#347 to update the grant status accordingly.

I think this is a MUST do, kind of a low-hanging fruit. I really would like to have that. Once the problem is identified, it’s easier to fix…

I’m kind of surprised we didn’t see faster that we broke our own extensions…

Regards, Antoine

1 Like