Skip to content

Rapid reaction to Marimo being acquired by Coreweave #536

@choldgraf

Description

@choldgraf

What happened

  • Marimo announced they've been acquired by CoreWeave https://marimo.io/blog/joining-coreweave
  • We think this is great news for the Marimo team, congratulations to them and all of their hard work paying off!
  • We also think that this is a key moment to highlight the importance of multi-stakeholder and openly-governed projects, like Jupyter.
  • People have been talking about Marimo "replacing" Jupyter for years. At a product level, it is very impressive, and there's a lot that Jupyter can learn from Marimo's functionality (and I'm excited about projects like https://github.com/ipyflow/ipyflow which build on ideas from the CalPoly team originally explored 7 years ago: https://github.com/jupytercalpoly/reactivepy)
  • But Jupyter differentiates in a key way from Marimo: it is governed and led by a community of peers, not a single company.
  • This acquisition is one key reason why that is important. Marimo is an excellent team and an excellent product. That said, the acquisition means that Marimo's product roadmap is now driven by CoreWeave's business strategy. That might be a great, or it might not, but either way it highlights the way in which one company drives products that don't have multi-stakeholder governance behind them.
  • It's one reason I'm excited for myself and for 2i2c to continue supporting the Jupyter ecosystem, especially in ways that make it a healthier multi-stakeholder community. Lately we've been doing that by providing foundational contributions at the executive level - serving on Jupyter's executive council and co-leading many sub-projects. We're also investing efforts in supporting Jupyter's community through things like JupyterCon (Jenny) and the Community Building working group (April).
  • We're excited for Marimo and CoreWeave, and we think Marimo will continue to build an excellent product.
  • We're also doubly-invested in making Jupyter the healthy, multi-stakeholder community that we need it to be for a healthy ecosystem to grow around it.
  • Jupyter will never be acquired, that's a feature, not a bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions