zarkones
Get Rid Of GinGonic Framework
Right of the bat I wish to state that there is nothing wrong with GinGonic itself. Motivation behind this move is to eliminate major dependencies as much as possible. Go's standard library has the sufficient features to get the job done quite fine.
A bit of history; For those who aren't aware of, the alpha version of XENA was made in TypeScript, Go, Haxe, C++, and Python. With major dependencies such are Vue2 and Adonis5. All of that was making difficult for other people to contribute and the Node ecosystem kept breaking everything with each update of almost any dependency.
Moving 100% of the code base to Go with Fyne and GinGonic being the only major dependencies has transformed the product in technical terms and allowed for rapid growth. Once GinGonic is removed, Fyne will remain as the only major dependency apart from the Go's standard library.
