Finally, 2.0 is released. I'm sorry for the long wait.
As a short disclaimer before you continue reading this: I'm very thankful for Marius creating this library and giving me the opportunity to maintain it. Although you might find some frustration in my statements, I don't want anyone to spread hate towards Marius. I will continue to support him and so should you.
Release 2.0You'll notice that the 2.0 release isn't hosted on the official ChartJs.Blazor but instead on ChartJs.Blazor.Fork. The reason for that is simple, I cannot publish to ChartJs.Blazor. I pushed everything to the releases branch but the release pipeline was paused quite a while ago and I don't have permission to enable it again. The same goes for the samples thus https://www.iheartblazor.com/ will remain in an old state as long as Marius doesn't return to update it. Of course I tried to publish it normally but Marius hasn't responded to my mail so I thought I'd get it over with now.
Marius (@mariusmuntean), the owner of the project, has had very little involvement throughout the last year. Both the project maintenance and the development of version 2.0 was done by me since the end of 2019 and I really enjoyed it. However, single-handedly maintaining a library with ~80k downloads as an 18yo without real world experience was challenging at times.
I was the one who put in some horrible features and made some terrible decisions (e.g. the covariant datasets) which made the library unpleasant to use. The goal of version 2.0 was to fix all of my prior mistakes and make the library ready for easy use in most projects. I believe version 2.0 accomplishes that goal but that doesn't mean the library is now finished. We're still only supporting Chart.js 2.9, there are still missing features and bugs (e.g. support for gradients, issues with responsiveness) and we don't have any docs yet.
I will continue to maintain this library by responding to issues and fixing urgent bugs. However, I won't actively develop new features.
I'm still hoping Marius will return and either continue to work on the library or hand the ownership to someone else. I don't feel comfortable searching for new maintainers in the name of the library since I'm "just" a contributor.
However, if you'd like to help develop this library and/or take over it, please tell us and we might get back to you.
When Chart.js 3.0 releases, many people will want to upgrade and so will the people using ChartJs.Blazor. I encourage you to try working with Chart.js 3.0 if you need the new features or the insane performance improvements but it will require some customization and you should probably use your own fork for it (and reference that directly). In the spirit of Open Source, I highly encourage you to contribute those changes back to the library ❤️
As a side-note, I have compiled some of my thoughts in a GitHub project. These are just some points that were important to me and I thought I'd do something public instead of just telling Marius about it.
My journeyBack when I started to work on this library (June 2019), I had very little experience. I had only worked on a handful of terrible school projects, never seen or worked with Open Source and had zero experience with Blazor. As such, most of my changes were bad but for better or worse, they all found their way into this library and now about 80k projects have to suffer from my incompetence. After some time, I got better at programming (of course I'm still nowhere) and started to understand and like Open Source. Suddenly I found myself being the maintainer of this fast growing library in the fast growing Blazor ecosystem. Although stressful (I'm sorry for all the poor issuers that received an unfriendly response), it was a really educational period.
At some point I realized just how big this library got because searching "blazor chart" on google shows this repo as first result. This might be influenced but on DuckDuckGo, it's the 4th entry. Also, ChartJs.Blazor is used in a sample project of an official dotnet repo along with multiple Microsoft employees opening issues on our repo. I thought this was absolutely insane and being the only person actively working on the repo, I didn't want to make all these people use a version that never should've been considered 1.0 in my books. So I got to work on 2.0 and now we're here.
Unfortunately, I have continuously lost interest in this library and it was just about finishing 2.0. A big factor in this is probably that I don't use Blazor myself anymore and I don't think I'll get back to it until .NET 6. Now that version 2.0 is released, I can peacefully slow down my activity here. As I said, I will continue to assist with issues because at the very least, this library has a special place in my heart.
I'd like to thank everyone who supported me and this library be it opening helpful issues, submitting pull requests or participating in discussions.
Special thanks go to Marius (@mariusmuntean) who has made this all possible in the first place. Without him, ChartJs.Blazor wouldn't exist.
I wish everyone the best
~Joel
Thank you all for this journey, it's been great. Now, it's time to say goodbye. The last semester of my apprenticeship is about to start and I'd like move on from ChartJs.Blazor. I have contacted Marius multiple times about the state of the library, the 2.0 release and me leaving. I've not heard back from him.
That being said, I wish ChartJs.Blazor the best and it makes me happy to see this community be so helpful and grateful. It's not a big community but we've surpassed 100k downloads recently and I'll gladly look back on this achievement in the future.
As suggested in the comments, I've also contacted Blazorise but I won't pursue that further (if you'd like to, please do).
Goodbye
~Joel
esso23, pvoliveira, mcraveiro, wuyuanyi135, Darki93 and 2 moreQuelo2020, SeppPenner, codelastnight, diXav, Apollo3zehn and 10 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4