perspective

ll eventually write my own). For larger datasets JSON generation and parsing performance bottlenecks. Additionally Parquet/Arrow offers much better types. Configuring AG-Grid is tricky, especially when you want config to be declarative. If you want to define your own custom rendering components, getting them to work properly per column when you want different renderers for pinned rows is tricky (my solution [3]) Support for the community version of AG-Grid is practically non-existent. I understand that they have an enterprise business model that charges for support. They don't seem to be interested in answering community bug reports or comments, even for generically relevant bugs. I have a decent amount of trust in AG-Grid's community offering [4], I don't see them cannibalizing community features to put them in their enterprise offering. Their enterprise features are the main development focus of the team, particularly the charts. The charts offering isn't impressive compared to bokeh, plotly, or vega. It would work for line of business apps, but not for a userbase familiar with better analytic platforms. All that said. AG-Grid has excellent documentation and examples. They examples are swappable between Javascript, Typescript, React, and Angular. [1] https://github.com/paddymul/buckaroo [2] https://github.com/finos/perspective [3] live example https://buckaroo-data.readthedocs.io/en/latest/examples/#/DF... [4] https://blog.ag-grid.com/javascript-jabber-podcast/

rward adapter API. Prospective integrates with existing data tools like Python and Jupyter, and all the dashboards created can be shared to ease collaboration. Our goal is to expand beyond financial services and become the standard toolchain for anyone whose job is to make sense and find patterns in large datasets. Prospective offers a great opportunity to dig into complex software. On any given day we might be optimizing how the database executes queries in C++, implementing API features in Rust, writing new language bindings for our API, speeding up our Bazel build process, or implementing new charting or query features in our graphical UI. Prospective is engineered to be fast and stable. We write good tests, and once a bug is fixed it stays fixed. Our team has a culture of mentorship and collaboration, and we work with each other knowing that every team member is always either teaching or learning. We pair-program regularly as a way to share our thinking and get feedback on our solutions. We hold each other to a high quality bar for performance and aesthetics, a constraint that we think creates a healthy environment for creative problem-solving. Every day has a brief "stand up" in the morning and a "stand down" in the afternoon to share what we've learned and what we're stuck on. Every Friday afternoon we demo what we're building for each other, which we call "dogfooding". And we talk regularly to our users, both paid and open-source, to create product feedback loops to understand where the rough edges are and what folks find extremely valuable. We'd love to chat with you if you have experience in WebAssembly, Python native extensions, C++, Rust or Jupyter. But regardless of your experience, we're very intentionally looking for people who are interested, motivated, and passionate about deeply learning WebAssembly and pushing the boundaries of what a browser can do. We believe smart, passionate people will channel that energy into learning how the tech stack works; and we believe that aligning people's work with their interests correlates with long term business success. We're currently looking for two additional engineers to join our five-person team. We're open to more-junior and more-senior engineers, and are committed to making a competitive offer based on experience and skill level. Contact andrew@prospective.dev