Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why new framework? #25

Open
j209 opened this issue Apr 22, 2019 · 2 comments
Open

Why new framework? #25

j209 opened this issue Apr 22, 2019 · 2 comments
Labels

Comments

@j209
Copy link

j209 commented Apr 22, 2019

Hi
Would not it be better to work on existing frameworks like Create-React-Kotlin-App instead of creating a new framework for java-based front-end?

@konsoletyper
Copy link
Owner

Why people keep creating frameworks while there're plenty of existing ones? Why did people create React while there were jQuery, Dojo, Knockout, Backbone, etc?

In my case the reasons are:

  1. Kotlin team was not interested in incorporating TeaVM support in their framework
  2. Personally, I think that React is built on concepts that don't fit with Java/Kotlin/Scala idioms. You end up with tons of wrappers (and still keep dealing with leaky abstractions). Why do you think Google wrote separate Angular implementation for Dart instead of bingind to Typescript implementation?
  3. I started Flavour before Kotlin was even released.

@cyberquarks
Copy link

Yes I think what Kotlin have now is Ktor, to me it looks like Vert.x

@j209 TeaVM/Flavour at first looks unusual but the more you use it, considering it TeaVM at core, it makes more sense. At first I was skeptical about why and how it works comparing to other framework; but don't compare it to other frameworks, Flavour is a new kind of beast with a different punch/approach which as we use it I find allows as to make webapps super fast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants