| ▲ | BoorishBears 4 days ago |
| Funny you say that since Dart is the primary reason most people I know don't want to use Flutter. There's been a trend of improved DX for languages used in app development: ObjC -> Swift Java -> Kotlin Javascript -> Typescript ...Dart feels like the before with no after, even though it got traction in the era of the Afters. |
|
| ▲ | vips7L 4 days ago | parent | next [-] |
| Darts pretty good. It has a lot of modern features, nullable types, pattern matching, sum types, and factory constructors; some really good build tooling. It can compile fully AoT. |
| |
| ▲ | saagarjha 4 days ago | parent [-] | | It’s not very good if you’re comparing it against Kotlin or Swift though. | | |
| ▲ | realusername 4 days ago | parent | next [-] | | It's a matter of taste, even just the swift example on this website makes me raise eyebrows. | | |
| ▲ | saagarjha 3 days ago | parent [-] | | I think that is valid because the syntax shown off here is controversial. However, I think Dart is just generally worse in almost all of its features. |
| |
| ▲ | wiseowise 4 days ago | parent | prev | next [-] | | It is great if you’re comparing it against Kotlin or Swift, unless you’re stuck in an era of 1.x Dart. | | | |
| ▲ | satvikpendem 4 days ago | parent | prev | next [-] | | Eh, it's getting there, slowly at first but more rapidly now. It now got tearoffs, I explained in another comment but > if you have an `enum Color { red, blue }` and a function takes `Color`, you can just do `f(.red)` not `f(Color.red)` Dart is getting new features pretty fast, they really started focusing on the DX more after Dart 2 and now especially after Dart 3. Macros were supposed to ship but it was incompatible with the goals of fast compilation, so other sorts of smaller features will ship instead. | | |
| ▲ | virtualwhys 4 days ago | parent [-] | | Big turnoff with Dart is the lack of json (de) serialization -- kind of shocking to have to resort to source code generation libraries in a modern language. Also, statement based instead of expression based, and not immutable by default are kind of a drag; not the end of the world but a bit unpleasant, IMO. | | |
| ▲ | satvikpendem 4 days ago | parent | next [-] | | Serialization support is coming, probably this year. As for statements vs expressions, it does have some expressions such as if and for inside lists but changing it wholesale to an expression based language would be too much of a breaking change. | | |
| ▲ | virtualwhys 3 days ago | parent [-] | | Serialization support has been coming for years, I lost patience. Otherwise, yes, some support for expressions, some support for immutability, no support for optional semi-colons, no privacy modifiers so "_" littered everywhere. I just found it to be an exceedingly ugly language when I used it a couple of years ago. Yes, some more pleasant modern functionality has been bolted on since then, but it's unfortunate that Dart was chosen as the backing language for Flutter, which is an awesome mobile framework. | | |
| ▲ | satvikpendem 3 days ago | parent [-] | | Serialization has always been possible via libraries, so most people were doing fine with that, what is coming is native serialization support, but in practice it will be functionally the same, ie rather than you running build_runner, the compiler will do it for you. I'm not sure what you used but that's what you were hung up on, there were always ways to solve it. Dart is a pragmatic language, it has everything you need and has a lot of benefits too, such as sound null checking (very few languages have this, Rust comes to mind), JIT and AOT support (Javascript / TypeScript such as for React Native doesn't, and Kotlin is just getting there with Kotlin Native but it still has a lot of issues), and now more functional programming concepts with algebraic data types via sealed classes and pattern matching. What language would you have chosen when Flutter came out circa a decade ago, or, we can be even more charitable and ask what language would you use today if you were to implement Flutter? I'm curious because everyone has their own ideas but they all don't work for one reason or another. | | |
|
| |
| ▲ | vips7L 3 days ago | parent | prev [-] | | I thought dart could natively deserialize via dart:convert? It just only decodes to lists and maps, you have to manually map into classes. |
|
| |
| ▲ | 4 days ago | parent | prev [-] | | [deleted] |
|
|
|
| ▲ | websiteapi 4 days ago | parent | prev | next [-] |
| isn't this just because Dart is way newer than those? it's from the 2010s. it's really modern in comparison (same generation as Kotlin swift and typescript) |
| |
| ▲ | BoorishBears 4 days ago | parent [-] | | > Dart feels like the before with no after, even though it got traction in the era of the Afters. It's aged like the recent languages but feels clunkier like a language that's much much older. |
|
|
| ▲ | mdhb 4 days ago | parent | prev | next [-] |
| Dart is hands down the best modern language out there for app development right now what are you even talking about? I understand that maybe a lot of people haven’t used it or maybe haven’t used it in years and that probably drives a lot of the FUD but for those who use it, it has stupidly high ratings from developers who use it and has for years. |
| |
| ▲ | BoorishBears 4 days ago | parent [-] | | It's not FUD when you make something terrible* and that reputation doesn't immediately slough off. And I just checked the Dart release notes from all of 2025: https://dart.dev/resources/whats-new Great progress! But smells a lot like the language I had it pegged for when "underscore as a wildcard" lands in February 2025, 2 years after pattern matching lands. How did they ship pattern matching in 2023, with a million examples of how to do it right already hashed out and in the wild... and then not figure out a wildcard symbol for 2 years? - * Dart was awful, lost to Javascript because no one rated it highly enough to justify moving off Javascript, and was practically dead until Flutter dusted off the corpse and pivoted away from their browser goals... so super weird revisionism to act like we're talking about some beloved evergreen language. | | |
| ▲ | munificent a day ago | parent | next [-] | | > How did they ship pattern matching in 2023, with a million examples of how to do it right already hashed out and in the wild... and then not figure out a wildcard symbol for 2 years? We shipped support for `_` as wildcards in patterns with Dart 3.0 when pattern matching first shipped. However, prior to Dart 3.0, `_` was already a valid identifier (as it is in most other languages). The feature you're mentioning from last year was to remove support for uses of `_` as an identifier outside of patterns. This way `_` consistently behaves like a wildcard everywhere in the language. We didn't ship that in 3.0 because it's a breaking change and those are harder to roll out without causing a lot of user pain. It's OK to not like Dart. There are multiple popular languages for a reason. But it is helpful when communicating about a language to others to be accurate so that they can make their own informed opinions. | |
| ▲ | wiseowise 4 days ago | parent | prev [-] | | You seem confused and indeed spreading FUD. Dart wasn’t awful. It wasn’t adopted at the time because it had a distinct runtime that would require splitting web in two which nobody wanted. On top of that it gave Google too much power, because now they would control both runtime (V8) + language (Dart). TypeScript won and became king because it was pretty much JS 2.0 instead of JS++ like Dart. | | |
| ▲ | BoorishBears 3 days ago | parent [-] | | In your version of history Dart was always a great language... but Google was simultaneously too powerful for other vendors to allow Dart to proliferate, but also too weak to sustain it themselves despite Chrome going on to do just that for many many web standards. I'm sure that's a really cozy idea, but doesn't pass the "common sense" test: a bit like your random misuse of the term FUD. - The simple reality is it wasn't very good, so no one was rushing to use it, and that limited how hard Google could push it. ES6 made Javascript good enough for the time being. Dart 1.x had a weak type system, and Dart 2 was adding basics Kotlin already had almost 2 years earlier: that was also around the time I first crossed paths with Flutter, and honestly Flutter by itself was also pretty god awful since it was slowly reinventing native UI/UX from a canvas. (It was a lot like Ionic: something you used when you had a captive user-base that literally couldn't pick a better product. Great for Google!) | | |
| ▲ | wiseowise 3 days ago | parent [-] | | > In your version of history Dart was always a great language... but Google was simultaneously too powerful for other vendors to allow Dart to proliferate, but also too weak to sustain it themselves despite Chrome going on to do just that for many many web standards. "In my version of history" It takes two seconds to find this if you weren't there when it happened. Google had a fork of Chromium with Dart VM called Dartium, it wasn't a matter of resources. Industry flipped Google off, plain and simple. Educate yourself before making such claims, the decision to not adopt Dart wasn't because of its technical merits as a language. The rest of your comment is just your opinion, so you do you. I'm not a Dart or Flutter devrel team to sell you their product. | | |
| ▲ | BoorishBears 3 days ago | parent [-] | | I guess this is the Dunning-Kruger effect everyone talks about! To understand just enough to regurgitate what happened, but miss why it happened... and then assume someone who's pointing at the much more relevant why is just plain wrong. Because the why requires actually understanding of things like developer mindshare rather than regurgitating search results. - The hint I'll leave if you're willing to consider maybe you don't know everything ever... look at who's feedback is being promoted when Chrome wants to do obviously unpopular things on the web: https://github.com/webmachinelearning/prompt-api/blob/main/R... https://github.com/mozilla/standards-positions/issues/1213 And model for yourself what happens if developer interest exceeds vendor refusal in magnitude, so Google just ships the thing, without a feature flag, to a massive percentage of the web-going world. | | |
|
|
|
|
|
|
| ▲ | wiseowise 4 days ago | parent | prev [-] |
| Have you even used modern Dart? |
