3 ms·
I looked over the web site. A few questions: - Why won't the OSS version provide features like history of execution? It seems like those are pretty basic to ad
by blagie 4y ago
I looked over the web site. A few questions:
- Why won't the OSS version provide features like history of execution? It seems like those are pretty basic to adoption. I'm working on an open source project, and it'd be a nice tool to potentially integrate. The commercial license is of zero interest since it's, well, all open-source.
- Why don't you sell the OSS version as well (e.g. for people who want to support you, or who want support)?
- Do you provide consulting services? Are they in the $50/hour range (just extrapolating from $200/year for up to 4 hours support)
- Why Django? I like Django, but it seems like using the same tech stack as Jupyter would make for simpler integration, administration, and lower TCO (plus the universe is going async)
- For presentation, the speed is an issue. Regeneration takes a while (I'm playing with the demo on Hugging Face). It's not quite adequate for interactive presentation. I do really like the concept of making presentations in Jupyter.
- And on that topic, the biggest gap I have is with interactive front-ends. I'd like to be able to somehow connect notebooks (both for dashboards and otherwise) for data munging to data visualization frameworks like D3. Jupyter is nice. Observable would be nice if it were open-source. There's a mile-high wall between the two.
- pplonski86 4y ago- What is your project? is it from data science space? - Selling OSS might be a great idea. Didn't consider it. I thought the Personal Pro version ($199/y) will be good for persons that would like to support the project or just need a support/guidance. - Yes, I do consulting services. I don't treat support hours in similar way as consulting. The support is for product that I love working on and I love supporting people using it. - Django - I'm pretty good at Django. What is more, I wanted to use Celery for processing background tasks and scheduling. This gives an architecture that can handle large loads. The frontend is in React with TypeScript. - Speed can be improved. There are many ways to better handle that (it is version 1.0). You can add Plotly charts to make presentation more interactive. The advantage of Mercury is that you can recompute all slides if needed.
- blagie 4y agoI don't disclose my identity online, and I think if I posted the project (or a description), it would do that. If you're curious, I'm glad to reach out by email. It is a data science project, and potentially, high-profile if it goes well. On a mile-high level, Mercury seems like a perfect fit for what I'm doing. Conceptually, it's exactly what I was looking for. Diving into the code, the fit seems less great, for reasons which are incidental (and wouldn't be worth changing for one integration). I'm trying to constrain the number of technologies in the overall project, to make it maintainable and deployable, and you seem to be on a completely orthogonal stack. So I'll keep diving in and trying to understand it better.
- pplonski86 4y agoMy email is piotr at mljar dot com