Google's Dart Language Reaches 2.8 Milestone With New Features

[ElectricPrism]

"compiles to JavaScript"

Well guys, I think it's time to get off this crazy train for good, I've heard it all.

[c117152]

I think GTK is pretty okay. It has some stuff I don't like about it, but some of that is getting fixed with the upcoming GTK 4.

Try changing input event logic or touch the threading logic.

[woprandi]

I don't know a single person that uses dart. Nor a single FOSS project I usually work with that uses it.

You should update yourself, it's used by the Flutter framework to build mobile (and soon web) apps

[kpedersen]

You should update yourself, it's used by the Flutter framework to build mobile (and soon web) apps

Thats cheating since flutter is made by the same developers as dart . I think the question still stands; "Who uses it?"

Who would tie themselves down to a fairly niche language just to use a GUI library?

[uid313]

Try changing input event logic or touch the threading logic.

I haven't tried much of that. As for threading, I don't think it is a concern of GTK (which deals with widgets) if you cant threads you can use GLib. But I haven't used it much, only to show a spinner while loading something.

[woprandi]

Thats cheating since flutter is made by the same developers as dart . I think the question still stands; "Who uses it?"

Who would tie themselves down to a fairly niche language just to use a GUI library?

Flutter is now one of the most famous project in GitHub, many mobile developers use it or are interested to it to avoid double native development. I use it for months and I won't go back.

[danielmaciel]

So fast. Much speed. Dart lang. Amaze.
"Fast on all platforms! Look at our native Hello World benchmark, runs in only 22ms!"

[jKicker]

Flutter is now one of the most famous project in GitHub, many mobile developers use it or are interested to it to avoid double native development. I use it for months and I won't go back.

You should have tried Qt/QML I do both.

Long before Flutter came that was already possible with QML. It has the same idea behind it, don't use native widgets with declarative language.
Where Flutter comes short is 7+k open bugs (just try it yourself, to do like a small project in it and let me know if you didn't hit at least 5 bugs in the process) and the fact that they do use Dart.
Dart was not intended for UI development from the get go but as a general purpose language for clients and server, to replace JavaScript more or less. Only with 2.0 they started to optimize it more for UI. So because of that you cannot get rid of semicolons https://github.com/dart-lang/language/issues/69
So it's super wierd and hard to try to make declarative language that breaks because you put , but it should have been a ; or vice vers (yeah, all those nested declarative UI views - see last example in https://medium.com/@DakshHub/flutter...r-f2cedb1a19fb).

However, given that Google is pushing Flutter, it's popularity is immense. Even though performance and stability wise is not comparable to Qt/QML. Not to mention the fact that QML was designed especially for UI development. However, Flutter has better license and it has a proper package manager.
So it's kinda sad to see people jumping now on some alpha level software that didn't even plan desktop support. Like, hot reload works every second run.
However, that is reality that we live in and one of mistakes (imho) of Digia behind Qt. I think it they made it under MIT (this mixed LGPL, Commercial approach will always alienate indie devs and small companies because they have no proper plans for small devs, and also big companies don't want to feel locked in, like my current company) it would get it so popular as Flutter and then it's easy to introduce Enterprise support (same as Ionic for example or many other opensource projects).

A bit of a rant but those are my 2 cents.

[woprandi]

You should have tried Qt/QML I do both.

Long before Flutter came that was already possible with QML. It has the same idea behind it, don't use native widgets with declarative language.
Where Flutter comes short is 7+k open bugs (just try it yourself, to do like a small project in it and let me know if you didn't hit at least 5 bugs in the process) and the fact that they do use Dart.
Dart was not intended for UI development from the get go but as a general purpose language for clients and server, to replace JavaScript more or less. Only with 2.0 they started to optimize it more for UI. So because of that you cannot get rid of semicolons https://github.com/dart-lang/language/issues/69
So it's super wierd and hard to try to make declarative language that breaks because you put , but it should have been a ; or vice vers (yeah, all those nested declarative UI views - see last example in https://medium.com/@DakshHub/flutter...r-f2cedb1a19fb).

I use it for months and I didn't hit any bug. Watching bugs count is stupid...
Dart is not a declarative language.
But Flutter just follows a declarative pattern for the UI. It's just a widgets tree. There are not any problem with colon or semi-colon. it's like many languages : colon to separate method parameters, and semi-colon in the end of expression. Your example has nothing special....
And with QML/Qt, you have to use a second language : C++

[jKicker]

I use it for months and I didn't hit any bug. Watching bugs count is stupid...

? Do you have to support app in production? It's not stupid, I'm not saying they are all relevant but use some filters to see critical ones. It's not a nice picture with only 2 officially supported stable platforms.

Dart is not a declarative language.
But Flutter just follows a declarative pattern for the UI.

Exactly my point, now Dart has to be adapted for something it is not intended. https://medium.com/dartlang/dart-2-s...m-3775d5f8eac7.

It's just a widgets tree. There are not any problem with colon or semi-colon. it's like many languages : colon to separate method parameters, and semi-colon in the end of expression. Your example has nothing special....

It was a first hit from google. It is a problem, that is why Android studio provides you with those comments // to help you to know where your ending is. I'm working with it, it's like developing declarative UI in C++, i.e. one nice C++ library to show you the same https://github.com/nlohmann/json#jso...lass-data-type.

And with QML/Qt, you have to use a second language : C++

That is not mandatory, only if you need to extend functionality. There is no need to use it otherwise but then you use JavaScript which is a second language. So indeed using only one language like Dart is a +1 for sure.
But you will need to use Java/Objective C++ with both for each platform. And given minimal support of core libs you will do that a lot compared to QML modules, i.e. Camera support in Flutter is horrible https://github.com/flutter/flutter/issues/31225.

I'm not trying to make it look bad for no reason, I just wish it was made better and learned from others. Stability and feature wise imho it is nowhere near Qt/QML. Architecture is also allowing for animations being blocked due to any 'heavy' activity like parsing json https://flutter.dev/docs/cookbook/ne...ground-parsing. But usually apps just get more and more logic so it happens that there is a death of thousand cuts and your app is not fluid for no apparent reason. This is easy to make architecture but quite disappointing since 3D engines are solving this problems forever. Oh, and also Qt with QML https://doc.qt.io/qt-5/qtquick-visua...-loop-threaded. You can put a while (true) in your code and still your spinner won't stop.

I do like it and use it for same goals that QML provides, but primarly due to better license, but I'm also disappointed with it and choice of Dart since engine is written in C/C++ you know https://github.com/flutter/engine/bl.../ui/dart_ui.cc. https://github.com/flutter/flutter/w...e-architecture.

I hope we see it being great in few years but it's a long road to there and it needs to survive this hype train.