5 ms·

Definitely. It's a shame that dart gets so much unwarranted hate. I mean, I also think it's an absolutely awful language but it's really proven to be a valuable

Definitely. It's a shame that dart gets so much unwarranted hate. I mean, I also think it's an absolutely awful language but it's really proven to be a valuable source of data for what other programming languages should do and perhaps more importantly: not do. I really hope we see a lot more things like Dart, and not so much negativity.

lucasmullens 7y ago
I haven't heard this general hatred of Dart. Why do you think it's an absolutely awful language?
- nsonha 7y ago
  not awful, more like mediocre and has no reason to exist
munificent 7y ago
Depending on when you last looked at Dart, there's a good chance we've either fixed or are fixing the things you hate about it. What didn't you like?
- virtualwhys 7y ago
  > What didn't you like? That the suggested features in this open issue [1] can't be implemented soon enough :) Is there a roadmap available that would give an idea as to when x, y, z language features may be implemented? [1] https://github.com/dart-lang/language/issues/546 https://github.com/dart-lang/language/issues/546
  - munificent 7y ago
    We don't tend to have detailed roadmaps because it risks setting people up for disappointment when schedules change. But what's roughly happening right now is: - Extension members are basically done and out the door. (See: https://medium.com/dartlang/extension-methods-2d466cd8b308 https://medium.com/dartlang/extension-methods-2d466cd8b308) - Non-nullable types are well underway. All but a few corners of the design are pinned down, much of the static checking is implemented, the core libraries have been mostly migrated, and we're working through the runtime implementation, migration tests, etc. - Next up after that, the current plan (which may change) is control over variance and stuff around pattern matching. We're working on it.
- Zarel 7y ago
  Personally, I'm just waiting for non-nullable types. After getting used to them, it's hard to imagine going back to a language that doesn't have them.
int_19h 7y ago
The use of ?? and ?. for null coalescing and null chaining comes from C#, and predates Dart.
- realharo 7y ago
  According to https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/operators/member-access-operators#null-conditional-operators--and- https://docs.microsoft.com/en-us/dotnet/csharp/language-refe..., ?. was only added to C# 6.0, in 2015. Groovy had ?. in at least 2005. Then there were CoffeeScript, Kotlin, Swift and a bunch of others in the meantime. Not that it matters :)
  - nsonha 7y ago
    coffeescript

lucasmullens 7y ago

I haven't heard this general hatred of Dart. Why do you think it's an absolutely awful language?

nsonha 7y ago
not awful, more like mediocre and has no reason to exist

munificent 7y ago

Depending on when you last looked at Dart, there's a good chance we've either fixed or are fixing the things you hate about it. What didn't you like?

virtualwhys 7y ago
> What didn't you like? That the suggested features in this open issue [1] can't be implemented soon enough :) Is there a roadmap available that would give an idea as to when x, y, z language features may be implemented? [1] https://github.com/dart-lang/language/issues/546 https://github.com/dart-lang/language/issues/546
- munificent 7y ago
  We don't tend to have detailed roadmaps because it risks setting people up for disappointment when schedules change. But what's roughly happening right now is: - Extension members are basically done and out the door. (See: https://medium.com/dartlang/extension-methods-2d466cd8b308 https://medium.com/dartlang/extension-methods-2d466cd8b308) - Non-nullable types are well underway. All but a few corners of the design are pinned down, much of the static checking is implemented, the core libraries have been mostly migrated, and we're working through the runtime implementation, migration tests, etc. - Next up after that, the current plan (which may change) is control over variance and stuff around pattern matching. We're working on it.
Zarel 7y ago
Personally, I'm just waiting for non-nullable types. After getting used to them, it's hard to imagine going back to a language that doesn't have them.

int_19h 7y ago

The use of ?? and ?. for null coalescing and null chaining comes from C#, and predates Dart.

realharo 7y ago
According to https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/operators/member-access-operators#null-conditional-operators--and- https://docs.microsoft.com/en-us/dotnet/csharp/language-refe..., ?. was only added to C# 6.0, in 2015. Groovy had ?. in at least 2005. Then there were CoffeeScript, Kotlin, Swift and a bunch of others in the meantime. Not that it matters :)
- nsonha 7y ago
  coffeescript