Feedback and talk about future of Scarlet.

[solidogen]

I'd like to share my overall feedback:

• Library is great to work with, very easy and fast setup
• Huge split between 0.1.x and 0.2.x versions makes people afraid of using this library in production. There is no clear roadmap for this project and we have no idea what to expect in the future
• It's unclear which version should we use - 0.1.x seems more supported, 0.2.x has new desirable features (like Flow support) but it looks fully abandoned
• 0.2.4 version doesn't seem to support kotlinx.coroutines versions 1.4.0+, I get crashes using ReceiveChannel after updating coroutines. Effectively, I'm tied to old coroutines without StateFlow/SharedFlow, which hurts. I could rewrite some with RX and convert, but to be honest I'd rather replace Scarlet if I need new hacks
• People already use 0.2.5 snapshots for a year from what I've seen in other issues, so an official release would be nice

We would really love an update concering this, to see where we are heading. I do not want to replace Scarlet, because overall it's pretty great. Thanks

[aaronweihe]

0.2.x added support for several other persistent protocols. because of that, there were some underlying architecture changes. I will prepare for 0.2.5 release soon.

To support Kotlin 1.4.0 in general, feel free to open PRs. I may find some time towards the year end.

We are targeting 1.0 in the beginning of 2021, then making 0.2.x essentially 2.x.

[tnyeanderson]

@aaronweihe so does this mean that when 1.0 is released, it will be based on v0.1.x ? How long will this "1.0/0.1.x" version be supported from then on? Will it become deprecated as soon as 0.2.x is released as 2.0? Is there any timeline for this?

I'm looking to use this library for my project, and it is my understanding that 0.1.x is what is currently in production at Tinder, but I need to have an idea of how long each will be supported.

Finally: when 2.0/0.2.x is officially released, will the API be at all backwards compatible with 1.0/0.1.x if using only the basic websockets implementation (not any new 2.0 stuff)? Or will I have to refactor my application for 2.0?

Thanks for everyone's hard work on this library, I hope to start using it soon.

[solidogen]

@aaronweihe hi Aaron, it's been six months and we still wonder if 0.2.x will be continued in the nearest future.

By the way, what stops the library (0.1.x branch) from getting 1.0.0 release? First version of Scarlet seems kind of complete, as only dependency updates are getting pushed for quite a long time.

[HasanHaghniya]

@aaronweihe @solidogen any updates?

[danilkinkin]

@aaronweihe, hi Aaron. Library is support or not maintaining now? Looks like project is abandoned.

This is very sad because I do not see analogs for communicating via the stomp protocol in android(

[zakayothuku]

Any updates? This looks abandoned!