Please help me decide on further development of KV...

# kvision

[Robert Jaros]

Please help me decide on further development of KVision. Vote!
1️⃣ Maintain backward compatibility for as long as possible. Make breaking changes only when required by the development of core tools and libraries (e.g. KGP). Keep current modules up to date, even if they're probably not being used by anyone.
2️⃣ Modernize! Support ES modules, TailwindCSS, kotlinx-datetime, Kilua RPC integration, at the expense of having to make changes (sometimes significant) to my existing projects. Deprecate and drop modules which require a lot of work to maintain and are not used often or at all.
3️⃣ Let it burn! Focus on Kilua development (I'm already migrating my applications!) 😉
4️⃣ I have different opinion (please leave a comment)

[rocketraman]

The only part of KVision I use is RPC, which I will migrate to either Kilua RPC or #C072YJ3Q91V in the future. Therefore I will abstain from voting as the decision does not affect me greatly. However, if I was a bigger KVision user, I would probably vote for 3️⃣ -- your valuable time should be focused on the future! :-)