Discontinuation of Support for Angular V17 and Future Directions

### Discontinuation of Support for Angular V17 and Future Directions

---

Hello community,

I wanted to bring to your attention that the `angular-material-rail-drawer` package will no longer be updated to support Angular V17 and future versions. This decision has been made after careful consideration, and I'd like to share the reasons behind it:

1. **Historical Context:** The need for this feature was first highlighted in an [issue](https://github.com/angular/components/issues/1728) dating back to Nov 4, 2016. Recognizing the community's demand and the lack of progress on the official front, I took the initiative to create this package and submitted a PR on May 12, 2020. Despite the clear demand and the passage of time, the concerns and needs of the community, in my humble view, seem to have been either ignored or given a lower priority by the Angular team.

2. **New Syntax:** Angular V17 introduces a new syntax that, in my opinion, is not in the best interest of developers. The changes seem to complicate rather than simplify the development process, making it less intuitive and more challenging to adopt.

3. **Direction of Angular:** Beyond just the syntax, the overall direction in which Angular is heading raises concerns. The framework's evolution seems to be diverging from the principles that made it popular in the first place.

### Options Going Forward:

1. **Continue Using Older Versions:** If your project relies on versions of Angular prior to V17, you can continue using the `angular-material-rail-drawer` package without issues.

2. **Hard Fork of Angular:** For those who share similar concerns about Angular's direction, one option is to consider a hard fork of Angular. This would allow the community to maintain and evolve a version of Angular that aligns more closely with our preferences and needs.

3. **Seek Alternatives:** There are other frameworks and libraries available that might better suit your needs. It might be worth exploring these alternatives if Angular's direction is a significant concern.

Lastly, I want to express my gratitude to the Angular team for their hard work over the years. While I have personal disagreements with some of the decisions, I deeply appreciate their dedication and contributions to the community.

Thank you for your understanding and support.