Seems so https://github.com/flutter/flutter with 81.3k stars.

That is Google

You don’t need more AWS support really. You can use any language that technology that AWS supports as the backend for a flutter app.

Not if you want to use Lambda. You could write your own wrapper for the AWS API's for other use cases, but you could also repeatedly hit your head with a hammer.

Server side is not dead, just dont expect them to make a Ruby on Rails kind of framework.

Very comparable with node.

How so?

Pros:

* Flutter is faster. You really notice that for example the animations in flutter are much smoother than in RN

* Flutter has really fast development cycle with hot reload (< 1s)

* Writing UI only once for both iOS and Android

* Better documentation

* Better tooling support in editors (VSCode and Intellij)

Cons:

* The Flutter ecosystem is quite small, there are many lacking plugins

* The Dart ecosystem is way smaller than JS

* RN uses the native widgets, in Flutter they are mimicked and sometimes wrongly, for example the iOS datepicker

To add to this -

* Developing plugins (to use native code functionality) is fairly easy. I recently created a PDF viewer plugin for Android without any prior knowledge of java, in 2 days.

* Dart has smaller ecosystem but dart is a real language with a batteries included std library. I don't think I need to state the superiority of dart as a language.

* Flutter's non native components make it easier for you to customize them

* Flutter doesn't have an obvious way to use native views in apps. You can launch native views but compositing native and flutter views is a bit weird right now.

* The ease of use in the development cycle is phenomenal. Nothing like I've ever seen in UI dev.

I would add on the Cons that Flutter is a bit more verbose than React-native since it does not have JSX. And also on the Pros that the community is much nicer on Flutter, RN is Facebook's own pet project and it's very visible when you run into issues.

Since there's so much competition in this area, hopefully this means Apple and Google will start to make this style of development a native part of their APIs and IDEs.

My only complaint so far is some things are not documented very well.

I started leveraging the json_serializable lib and all my responses were returning null... it took me a few days of heavy debugging to figure out it was how I crafted my constructors and how the code generators worked with it.

Thankfully, the community is really welcoming. Not like RN where issue are closed for no reason all the time..

I updated the article to make more clear that examples are from modern languages, but many of the ideas come from older languages.

> All the examples above are from Reason, Swift, Kotlin and Dart. However, many of the ideas above can already be found in much older languages such as Lisp (1958), Smalltalk (1972), Objective-C (1984), Haskell (1990), OCaml (1996) and many more. So while the examples are from modern languages, the ideas in this article are actually very old. (*)

> You could say that those “modern” languages are trying to popularise old ideas. They put the idea in a different more common syntax while also leveraging older ecosystems. All the languages in this article use the popular C-style syntax. For example, Reason is OCaml in a C-style/Javascript-style syntax while also leveraging the JavaScript and OCaml ecosystem and Dart is heavily influenced by Smalltalk and leverages the Javascript ecosystem.

I recently made this little tool for writing latex macros: http://kasperpeulen.github.io/PressAndHold/ It works the same as the OSX press and hold accent picker. I have also a unicode version which I think is much more appealing for young mathematicians: http://kasperpeulen.github.io/PressAndHold/Unicode/

All MIT licensed if you are interested in using it.

I'm working on the controls. Let me know what you think: http://euclidthegame.org/Level1anew.html

That's a lot better. I'd like to see it try to snap when dragging. I notice I can click once (compass) and click again on a point, but a click-drag to a point doesn't seem to snap to the point.

I'm working on some of those suggestions here: http://euclidthegame.org/Level1anew.html

Thanks for your feedback!