3 ms·

>We created the JSON decoder in dart:convert, the serialization package, the protobuf compiler, and one of the JSON Schema based generators Great, then you alr

>We created the JSON decoder in dart:convert, the serialization package, the protobuf compiler, and one of the JSON Schema based generators Great, then you already have 90% of the job done then. >If you have an easy magical solution that fits more use cases that what we're already using in real production code What are bug reports for? >I'd be very interested in seeing what a team less apathetic that the ones that produced five serialization packages comes up with. I don't know, but the 5 bugs I've submitted to Dart haven't been fixed yet, I submitted those almost 2 years ago all marked in the core as medium, so, you tell me, what conclusion should I make?

spankalee 12y ago
>>If you have an easy magical solution that fits more use cases that what we're already using in real production code >What are bug reports for? If you have a bug report with the description of the behavior you want, then that's at least a start. My point is that I'm claiming there isn't an obvious one-size-fits-all solution, and that we've created several serialization packages, clearly demonstrating that we're not apathetic regarding serialization. To imply so is frankly insulting. >I don't know, but the 5 bugs I've submitted to Dart haven't been fixed yet, I submitted those almost 2 years ago all marked in the core as medium, so, you tell me, what conclusion should I make? That all projects of this magnitude have many open bugs? We have almost 4000 open issues out of 20,000 all time. Yes, many of those open issues are old, it's much easier to open them than close them, and some answers just aren't clear. I assume these are your issues: https://code.google.com/p/dart/issues/list?q=adrian https://code.google.com/p/dart/issues/list?q=adrian First, it's clear you've been using Dart from the start and that you've filed good reports, so thank you very much. There are 3 open out of 13 total. The double.round() one is good, IMO. I don't know why it hasn't been addressed, other than the sheer volume of bugs we have. I would recommend that the squeaky wheel gets the oil. Sorry, but it's just reality with a large project and team. The other two I don't see clear consensus on, and the comments seem to indicate that the current behavior is intended. I personally agree with you on the Dart parse issue, but think that we shouldn't special case Completer, but instead work on union types.
- adrianlmm 12y ago
  I know that I'm not working in the next super text-editor, or in the next super-game, but I'm using Dart in a enterprice enviroment where numbers do matter, so If I see something as trivial as double.round not having what I need I really get demotivated, so, I'm sorry for getting emotional. I'm using .NET in the server and if there is something MS does right is to listen to their enterprice customers, even if those customers do boring stuff like capturing forms and displaying numbers, but hey, those are important stuff for enterprices, same with the DateTime.parse, numbers and dates is an every day issue here, and is very important, and I'd like to see Dart also focusing in this type of market, we are alot. The Completer bug I is also key for scalable projects, we, the ones using Dart, assume that the type safety part of Dart is reliable to do our work. Anyway, I'm, glad at least one Dart developer is here to listen.

spankalee 12y ago

>>If you have an easy magical solution that fits more use cases that what we're already using in real production code >What are bug reports for? If you have a bug report with the description of the behavior you want, then that's at least a start. My point is that I'm claiming there isn't an obvious one-size-fits-all solution, and that we've created several serialization packages, clearly demonstrating that we're not apathetic regarding serialization. To imply so is frankly insulting. >I don't know, but the 5 bugs I've submitted to Dart haven't been fixed yet, I submitted those almost 2 years ago all marked in the core as medium, so, you tell me, what conclusion should I make? That all projects of this magnitude have many open bugs? We have almost 4000 open issues out of 20,000 all time. Yes, many of those open issues are old, it's much easier to open them than close them, and some answers just aren't clear. I assume these are your issues: https://code.google.com/p/dart/issues/list?q=adrian https://code.google.com/p/dart/issues/list?q=adrian First, it's clear you've been using Dart from the start and that you've filed good reports, so thank you very much. There are 3 open out of 13 total. The double.round() one is good, IMO. I don't know why it hasn't been addressed, other than the sheer volume of bugs we have. I would recommend that the squeaky wheel gets the oil. Sorry, but it's just reality with a large project and team. The other two I don't see clear consensus on, and the comments seem to indicate that the current behavior is intended. I personally agree with you on the Dart parse issue, but think that we shouldn't special case Completer, but instead work on union types.

adrianlmm 12y ago
I know that I'm not working in the next super text-editor, or in the next super-game, but I'm using Dart in a enterprice enviroment where numbers do matter, so If I see something as trivial as double.round not having what I need I really get demotivated, so, I'm sorry for getting emotional. I'm using .NET in the server and if there is something MS does right is to listen to their enterprice customers, even if those customers do boring stuff like capturing forms and displaying numbers, but hey, those are important stuff for enterprices, same with the DateTime.parse, numbers and dates is an every day issue here, and is very important, and I'd like to see Dart also focusing in this type of market, we are alot. The Completer bug I is also key for scalable projects, we, the ones using Dart, assume that the type safety part of Dart is reliable to do our work. Anyway, I'm, glad at least one Dart developer is here to listen.