The strongest foundation for every successful company is its people. At Boldare, we are proud of every single person who takes part in our journey of building amazing digital products because we know that they are exceptional individuals and team players. And the Marble.js framework by Józef Flakus perfectly illustrates what kind of forward-thinkers we have working with us.
Why Marble.js? The inspiration for the name came from a popular form of notation and visualization of asynchronous data streams, also called „marble diagrams”, which are used for teaching, and documenting the data flow and stream transformations.
I asked Józef why he decided to build Marble.js:
Using a lean startup approach for Marble.js
Building a new framework is not something you can do overnight. It is always a process with a clear philosophy behind it. For Józef, the idea for Marble.js was born months ago. However, he took his time and made sure that there were no similar solutions on the market.
>>Interested in lean approach? Check out Polco case study
Marble.js to enrich reactive programming
Marble.js received an incredibly positive response from the JS community. In the first week of its publication on GitHub, Marble.js earned 700 stars (and for the first two days, it was the most popular TypeScript repository) and its fair share of exposure on social media, getting attention from, among others, Ben Lesh (core maintainer RxJS) and Minko Gechew (Google Developer Expert).
What are the plans for Marble.js? Józef:
The short-term plan is to release a 1.0 version of the framework within the next two months. But for the long run, I would like to create a community around Marble.js. Because it is an open architecture based on a ‘middleware system’ the community can create its own (let’s call them) plugins to complement the infrastructure. I also hope that Marble.js will contribute to the popularization of the reactive programming approach.
I keep my finger crossed.
Share this article: