3 ms·

> My argument is that such an API cannot be made, because it will be too large, too fragile, or both With that logic, why does Dart even has futures? I bet tho

> My argument is that such an API cannot be made, because it will be too large, too fragile, or both With that logic, why does Dart even has futures? I bet those are more complex and use more code, and yet, Dart have them, so I don't think it is about "being large and fragile". >I don't know if Polymer.dart depends on mirrors, but it's irrelevant as neither Polymer or Mirrors are part of the core library Since Dart developers are obsessed with Polymeter I wouldn't say is not relevant, and if they would have to make the JSON to Object<T> serialization in another library and not in the core then so be it, nobody is asking them to put it in the core. > Yes, because because reliably instantiating an arbitrary object with all data in the right place during runtime is just quite a hard problem in a static language They already have 90% of te job done, they have the JSON parser, they have mirrors, btw, JSON is a very simple format in the case you don't know, they already have mirrors to instantiate objects at runtime, they instantiate Maps, why can't they instantiate Objects with mirrors? is not logical, the other reflections libraries seem to work pretty well so, is not an excuse. > My argument is that it's an issue of downsides not being worth the benefits For who? maybe not for you, but for others it would. > That's your problem, not a valid reason to criticise the Dart developers Dart developers are humans and fallible, so they are not supergods or something, and Im not asking to put this in the core.

DCKing 12y ago
Wow, 90% really? It seems you figured it out. Maybe you should break through this appalling apathy and show them how it's done. After all, it's clear that your need should be catered to and these strangers providing things for free simply won't do it. Moreover, it's obviously only 10% of the work left, and less than the work on Futures. How hard can it be?
- adrianlmm 12y ago
  When I said 90% it is because the hard part is already done, and that hard part are mirrors, they already have the JSON parser too, so, they just have to put them together. Anyway, since you are starting in using sarcasm and I'm not interested in that kind of argument, so we are done here.
  - DCKing 12y ago
    I'm sorry about that. I thought we left serious conversation behind when you started asserting that most of the work was done (as Jackson shows, parsing and reflection are not the hard parts of a JSON-to-class library), and continued that apathy was still the most likely explanation. I thought I would have presented you enough evidence of the hardness of solving this problem, but you appear to be entitled enough to ignore it.

DCKing 12y ago

Wow, 90% really? It seems you figured it out. Maybe you should break through this appalling apathy and show them how it's done. After all, it's clear that your need should be catered to and these strangers providing things for free simply won't do it. Moreover, it's obviously only 10% of the work left, and less than the work on Futures. How hard can it be?

adrianlmm 12y ago
When I said 90% it is because the hard part is already done, and that hard part are mirrors, they already have the JSON parser too, so, they just have to put them together. Anyway, since you are starting in using sarcasm and I'm not interested in that kind of argument, so we are done here.
- DCKing 12y ago
  I'm sorry about that. I thought we left serious conversation behind when you started asserting that most of the work was done (as Jackson shows, parsing and reflection are not the hard parts of a JSON-to-class library), and continued that apathy was still the most likely explanation. I thought I would have presented you enough evidence of the hardness of solving this problem, but you appear to be entitled enough to ignore it.