News for hackers. Stuff that matters.

A comment on What It Was Like to Write a Full-Blown Flutter App. Parent comment

Re:What It Was Like to Write a Full-Blown Flutter App by thosakwe on Saturday June 16, 2018 @08:24PM (#17330252)
Dart VM != Dart server in this case.

The focus of Dart 2 and beyond is the client side [0].

You can definitely run Dart in the VM, but beyond the HttpServer API, server-side support is mostly a community effort.

My point isn't that this is a bad thing, it's that it makes sense for Firebase to be promoted because Dart doesn't have _official_ server-side support.

[0]: https://medium.com/dartlang/announcing-dart-2-80ba01f43b6

[ Parent | on HN ]
Re:What It Was Like to Write a Full-Blown Flutter App by wmleler on Tuesday June 19, 2018 @01:27PM (#17348568)
Our focusing on the client doesn't mean you can't use Dart on the server. In fact, we (the Flutter team) use it on the server.

Analogy: JavaScript is focused on the client too, but people also use it on the server.

[ Parent | on HN ]
Re:What It Was Like to Write a Full-Blown Flutter App by boustrophedon on Saturday June 16, 2018 @09:28PM (#17330447)
I just think saying that it doesn't have "server-side support" is misleading. It makes it sound as though you'd need third-party code to run on the server at all.

I do agree they have pivoted to a more client-sided branding though.

[ Parent | on HN ]