Future of dartson

[eredo]

There have been great improvements and changes in the dart ecosystem since the first version (0.1.0) of dartson was released in October 2013.
With the latest movement away from mirrors, transformers (barback) and towards code generation there are some great alternatives to dartson including:

https://pub.dartlang.org/packages/json_serializable
https://pub.dartlang.org/packages/built_value

With this in mind I was thinking about the future of dartson with the following points in mind:

• Why do developers choose dartson over other packages?
  • Popularity because of the article: https://www.dartlang.org/articles/libraries/serialization
  • Ease of use without importing generated files?
  • Custom type transformers?
• What features should be provided in the future?
  • Support across multiple packages
  • Complex objects
  • Runtime class/type replacements
  • Versioning support
  • Default value serialization
• Which packages are used commonly with dartson?
  • Should there some sort of adapters to these packages?
• On which platform is dartson used or should be used? (server,web,mobile)

I need your support to answer these questions and to make a decision of where to go next with the development of dartson. Therefore I would really appreciate feedback to these questions or any additional input.

[kevmoo]

Great reflection here, @eredo .

Happy to discuss alignment, code sharing, etc across dartson and json_serializable.

[jimirocks]

Well I was using dartson cause it was familiar to me coming from java world used to jackson. But now I am not on dart for more than year, so don't know how things have changed.

[eredo]

Thanks @kevmoo !
It sounds like a good idea, to have json_serializable as the basic serialization solution with no "magic" and dartson on top to provide some nice to have features. I'll go ahead and make a list of features which are currently available in both packages and gather some further features from known libraries of other languages (like jackson, gson, etc...).

[kevmoo]

Sounds great!

…

On Thu, Mar 1, 2018 at 12:59 AM, Eric Schneller ***@***.***> wrote: Thanks @kevmoo <https://github.com/kevmoo> ! It sounds like a good idea, to have json_serializable as the basic serialization solution with no "magic" and dartson on top to provide some nice to have features. I'll go ahead and make a list of features which are currently available in both packages and gather some further features from known libraries of other languages (like jackson, gson, etc...). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABCiox3U99m8BxzXRJaHfS2pcTLa06xks5tZ7hvgaJpZM4SVewB> .

[Meai]

Dartson was the only library that actually worked + quickly and easily given the sample code and it reminded me the most of how Gson from java or Newtonsoft from c# worked.

[albertocappellina]

dartson is the library used by swagger.io. we currently use it for native (android/ios) and web development so it will be cool to use it on flutter as well!!

[eredo]

Interesting! Didn't know it was used, but looks like they have also converted from dartson because of flutter support.

[eredo]

@kevmoo I'm still working on this, but it takes some time because of the lack of free time (tackling the release of our 2.0 software version).
I'm currently getting into the source of json_serializable builder and write a proposal of how the package could work together based on the features dartson could ship with.

There are also some additional proposals which could provide a functionality on top of json_serializable:
https://github.com/eredo/dartson/tree/master/doc/proposal

[kevmoo]

Sounds great!

…

On Fri, May 18, 2018 at 11:50 PM Eric Schneller ***@***.***> wrote: @kevmoo <https://github.com/kevmoo> I'm still working on this, but it takes some time because of the lack of free time (tackling the release of our 2.0 software version). I'm currently getting into the source of json_serializable builder and write a proposal of how the package could work together based on the features dartson could ship with. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABCipRaUzhKNCwSo_9bP4i3u7dhQOq1ks5tz8DKgaJpZM4SVewB> .