# Tidal 2.0?

**URL:** <https://uzu.lurk.org/t/tidal-2-0/4247>\
**Category:** TidalCycles\
**Tags:** innards\
**Created:** [31 August 2022 13:44 UTC](https://uzu.lurk.org/t/tidal-2-0/4247 "2022-08-31T13:44:53Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\
**Post date:** [1 September 2022 10:16 UTC](https://uzu.lurk.org/t/tidal-2-0/4247/4 "2022-09-01T10:16:11Z")

</div>

@polymorphic.engine Yes true. That would also make implementing/testing against the strudel/vortex implementations easier I guess. Also with the new additional beat-oriented sequence representation, the mininotation should be a much more straightforward mapping to Haskell. This is also an opportunity to make breaking changes in the mininotation. For example now that \_ and @ are aliases, we could repurpose @ for ties. We can also make sure that everything is patternable in the mininotation that could be.

@jalex Yes that would be so good, and I share your frustration with this aspect and the difficulty of installing etc. See [Releasing Tidal 1.9.0](https://club.tidalcycles.org/t/releasing-tidal-1-9-0/4241) for steps towards this. It does need a lot of help though to get it working cross-platform.

---

_[View the full topic](https://uzu.lurk.org/t/tidal-2-0/4247)._