Give us a break! Stef
On Apr 24, 2012, at 1:39 PM, Göran Krampe wrote: > On 04/24/2012 01:06 PM, H. Hirzel wrote: >> On 4/24/12, Igor Stasenko<[email protected]> wrote: >>> can you name just one which can be useful in this context??? >>> what tools, except written in smalltalk and used by smalltalkers you >>> are expecting to use >>> with smalltalk source code stored in source code repositories? >> >> JavaScript :-) in connection with Amber. And couchDB. > > I do notice that Igor mentions a specific use case here, but let me ignore > that and just reflect on JSON in general: > > And Riak. And quite a few other NoSQL dbs use JSON. And lots of RESTful RPC > backends tend to use JSON, we do in our C# backend here at my customer. And > almost all web APIs on the net use JSON. > > And JSON pops up everywhere in fact. So personally, while I did actually > implement Tirade, JSON is still a very nice format due to its ubiquity. > > The main reason I made Tirade was because JSON didn't handle linefeeds in > strings so I couldn't store source code in JSON in a reasonably readable way. > At least not per true JSON spec. > > Also, Tirade supports more atomic Smalltalk datatypes. And since it encodes > keyword messages it simply offers more structure than JSON does. And it is > streamable. And perhaps one or two more things. > > But in summary - JSON is generally a very good choice and IMHO Pharo should > be *great* at handling JSON. It's not going away :) > > regards, Göran >
