Change of technology

[LuisEduardoFrias]

I believe it would be beneficial to explore alternatives to Cordova for the application's development. I've noticed performance issues during daily and prolonged use. Technologies like Flutter, React Native with Expo, and Ionic offer significant improvements. In particular, React Native with Expo stands out due to its extensive codebase and the efficiency of its applications, which tend to be faster and lighter than those developed with Flutter.
I'm interested in contributing to the project.

[bajrangCoder]

Yes, we also want to move away from Cordova because its ecosystem is slowly dying, and the developer experience is not great. However, rewriting Acode entirely would be extremely difficult and time-consuming, potentially slowing down feature development and bug fixes.

Instead of a complete rewrite, we could migrate to a technology similar to Cordova, such as Capacitor. However, even Capacitor would require significant effort to get Acode working properly.

If we ever decide to rewrite Acode, there are only a few viable options. As you mentioned, Flutter and React Native are strong contenders. If we choose Flutter, we would need to invest considerable effort into ensuring compatibility for existing plugins. On the other hand, React Native—while previously not ideal due to performance limitations—has improved significantly with its recent architectural updates, making it a more viable option. But react native is react centric and acode isn't written in any react framework, it's js, scss, etc

There is also a new player, Lynx, which is quite impressive, but its ecosystem is not mature enough yet.

Regarding performance improvements, we can optimize our plugin architecture to provide a significantly better user experience. As that's what makes Acode slow. Additionally, we have plans to extend our plugin system to support WebAssembly (WASM) and run plugins in worker threads. This would ensure a smoother experience. However, at the moment, this is only a planned feature, and no active development is underway.

[LuisEduardoFrias]

I understand all the points perfectly. As you say, Lynx is another good option, but it's still very new.

I think you should stop focusing on new features and fix the bugs that already exist. For example, every so often I have to back up and delete the app data, as the app starts to freeze constantly, which is one of the most concerning issues, among others. As I said, I use the pro version of the app a lot.

If changing or migrating to other technologies will speed up development and prevent errors or increase the error resolution process, then you could consider it further.
Just like Microsoft migrated from TypeScript to Go, and that was just for performance.

If you plan to do so in the future, please contact me, I am willing to contribute.

[bajrangCoder]

As you say, Lynx is another good option, but it's still very new.

Yes , it's new but it has potential and also it is already in use but it's community isn't big enough

Yes, there are many issues and also dx issue which is related to our tech stack and it's very difficult for a single contributor to do that(As currently I'm the one who is maintaining the project)

Just like Microsoft migrated from TypeScript to Go, and that was just for performance.

Yes, there are many examples in community like fish shell, etc
Btw Microsoft have enough resources and people to do that kind of milestones , we are very very small.

If you plan to do so in the future, please contact me, I am willing to contribute.

We always love support from our nice community

[LuisEduardoFrias]

(As currently I'm the one who is maintaining the project)

Oh I see, I assumed that since there were 81 contributors, many would provide support.

Btw Microsoft have enough resources and people to do that kind of milestones , we are very very small.

Yes, of course I understand that, I only mention it because it is a very recent topic.

[UnschooledGamer]

Oh I see, I assumed that since there were 81 contributors, many would provide support.

81 Contributors are those who contribute sometimes or specifically, including translations, etc. Raunak Raj(bajrangCoder) is the Current Maintainer.

Others Might Help out when they notice or are asked to do so in their free time as a helping hand.

[LuisEduardoFrias]

Okey, I understand.

[LuisEduardoFrias]

Hi, one question, when you delete a file from acode, where does that file go? I know it asks a verification question before deleting a file, but I just deleted my src folder.

[deadlyjack]

It might still be in cache. If you can access cache folder then you can restore it.

…

On Tue, 8 Apr, 2025, 11:53 am Luis Eduardo, ***@***.***> wrote: Hi, one question, when you delete a file from acode, where does that file go? I know it asks a verification question before deleting a file, but I just deleted my src folder. — Reply to this email directly, view it on GitHub <#1228 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJHIHI2WHLBSWZ5MHV2576T2YNTNDAVCNFSM6AAAAABZVBWWO2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZVHE4TINY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** .com>

[LuisEduardoFrias]

I'll try, thanks.

[RohitKushvaha01]

Moving away from Cordova is the right decision. Capacitor is actively maintained and claims to have some level of backward compatibility with Cordova. Switching to Capacitor might be the least painful process compared to other technologies.

they even seem to have a migration guide
https://capacitorjs.com/cordova
https://capacitorjs.com/docs/cordova/migrating-from-cordova-to-capacitor

[UnschooledGamer]

Apart from migration guide. It's not straightforward migration even though capacitorjs has backward compatibility to cordova. Requires additional efforts to be put in to get Acode working.

[UnschooledGamer]

Original Discussion regarding migration to capacitorjs started at #1038 while it didn't move that much.

[bajrangCoder]

Hmm, in case of capacitor we need to port things but in other cases we need to rebuild.

Also it requires many manual efforts when migrating to capacitor and also we need some compatibility APIs for plugins similar to Cordova

[bajrangCoder]

Original Discussion regarding migration to capacitorjs started at #1038 while it didn't move that much.

I'll continue it (someday)

[UnschooledGamer]

An Attempt for Cordova to capacitorJS migration is made at #1266

(Just for heads up, if someone wants to help him. Kindly ask him first.)

[peasneovoyager2banana2]