On 13 Jan 2014, at 16:36, Marcus Denker <[email protected]> wrote:
> >>> >>> Fuel is included, but that implements a binary, not textual encoding. >>> IMHO it would make sense to include either or both STON and NeoJSON. >>> On the other hand, the same can be said about many external frameworks. >>> You can very easily load both STON or NeoJSON manually. >> >> Thanks, Sven. >> >> I just wonder what are the plans for future, because knowing that some >> functionality will be available by default helps me to introduce new >> interesting workflows. >> > Why? Because it’s nice if you can do something with just “vanilla” Pharo. Yes, STON is easy to load, but if you want to automate something you have to preload it, and if you are not automating you have to do the thing over and over again. I want to come up with something cool and say: “Look, you can do this and this and get awesome result”. The less “this”s are the better it is (IMHO). So if STON will be preloaded and JSON - not, I will definitely go with STON. If not - probably JSON, as it has more support across different tools. Etc. This isn’t really special. Just bugs in my head :) Uko > >
