You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just giving a status update on Radashi. I've spent a lot of time recently getting Radashi into good shape to be sustainably maintainable™. This effort has manifested in several key areas:
GitHub Actions: I've put significant work into our CI/CD pipeline. The fruit of my free labor is most evident in our scripts directory.
Documentation: I've written our documentation site from scratch using Astro. You can find the source code here. While not all pages are published yet (like our Lodash parity overview), I'm particularly happy with our home page, my comparison post with Radash, and our "Browser Support" page.
Domain: We recently acquired the "radashi.js.org" domain, which feels irrationally satisfying.
Developer Tools: I've completed the first version of Radashi's CLI and VS Code extension. You can learn more about these tools and contribute to their development here.
Template Repository: I'm currently writing a guide on how to use Radashi's template repository (along with the CLI and/or VS Code extension) to easily customize Radashi to your liking.
The big vision here is for Radashi to become a solid foundation and common ground for decentralized collaboration. We're building an ecosystem where Radashi’s maintainers can't prevent you from easily using someone else's contribution. In fact, our new tools already include a command for importing unmerged PRs into your own Radashi fork.
In terms of the codebase itself, we've made numerous improvements already, like adding some much needed functions (#81, #52, #173, #148, #58, #16), extending our existing functions (#30, #128, #127, #135, #116), squashing reported bugs (#178, #112, #82, #18),fixing performance bottlenecks (#76, #62, #37, #33, #13), and refining their types (#142, #175, #12). Check out the changelog to explore our work further.
Looking ahead:
Finishing the release notes for our first official release (v12.2.0) is my next priority.
Post-release, I plan to refine our ethos and prepare an announcement post to share in various forums, aiming to attract more attention and contributors.
We have quite a few breaking changes both proposed and lined up. It'd be great to get more community feedback on them, so we can move forward with increased confidence.
On a similar note, I strongly recommend you to share your thoughts on the many proposals currently in review. The more diverse viewpoints, the better.
Long-term, I'm committed to collaborating with all of you to gradually improve Radashi over the coming years.
Finally, I'd like to extend my deepest gratitude to those who supported Radashi early on with their time, knowledge, and energy: @MarlonPassos-git, @Minhir, and @adamhamlin. A big, loving "thank you" to these folks. I hope more like them will join us in the future. If you're passionate about Radashi, please help in any way you can, so we can make Radashi as enjoyable to use as possible.
That's all for now. Hope you're all having a good day! Thanks for reading.
The text was updated successfully, but these errors were encountered:
Hey everyone,
Just giving a status update on Radashi. I've spent a lot of time recently getting Radashi into good shape to be sustainably maintainable™. This effort has manifested in several key areas:
The big vision here is for Radashi to become a solid foundation and common ground for decentralized collaboration. We're building an ecosystem where Radashi’s maintainers can't prevent you from easily using someone else's contribution. In fact, our new tools already include a command for importing unmerged PRs into your own Radashi fork.
In terms of the codebase itself, we've made numerous improvements already, like adding some much needed functions (#81, #52, #173, #148, #58, #16), extending our existing functions (#30, #128, #127, #135, #116), squashing reported bugs (#178, #112, #82, #18),fixing performance bottlenecks (#76, #62, #37, #33, #13), and refining their types (#142, #175, #12). Check out the changelog to explore our work further.
Looking ahead:
Finally, I'd like to extend my deepest gratitude to those who supported Radashi early on with their time, knowledge, and energy: @MarlonPassos-git, @Minhir, and @adamhamlin. A big, loving "thank you" to these folks. I hope more like them will join us in the future. If you're passionate about Radashi, please help in any way you can, so we can make Radashi as enjoyable to use as possible.
That's all for now. Hope you're all having a good day! Thanks for reading.
The text was updated successfully, but these errors were encountered: