These are chat archives for dry-rb/chat
Method#parametershas entirely different data on rubinius :weary:
Serialize) which will receive object that needs to be serialized and mapper as
Serialize) object in
corecontainer or in API sub-app container? I’m in doubt since looking at berg, all “wrappers” are a part of core component, however, in this case, serialization will be performed only for sub-app.
require "yaks" module Main class JsonSerializer Serializer = Yaks.new do # yaks config here end def call(*args) Serializer.call(*args) end end end
JsonSerializerbasically just “wraps” the yaks instance
Serializeronly in API sub-app container?
If you remove it, I would suggest a quick closing summary.
Something along the lines of:
I'm not here to bash Rails, I'm trying to drive a conversation about diversifying the Ruby ecosystem. Ruby needs new frameworks and libraries built on top of solid abstractions. These abstractions should provide services with which a developer can build applications suited to a diverse range of domains. I'm currently building (some projects) to accomplish those goals. If you're interested in a more robust Ruby ecosystem, join us (point to the projects, gitter, or wherever).
Or if that's not quite your goal, just summarize the importance of good abstractions in frameworks