"You seem to support the typical bloatware philosophy: First put everything which comes to mind into a "library", and then see what can be done with it. This is definitely not the PicoLisp way."
And that's why I go for Clojure for web development, Ring does exactly what I want a web dev framework to do straight out of the box, no more no less, JSON is already there too + so much more. I avoid the hassle of having to write a lot myself and still get to work in a beautiful language. I can then interface through http with a simple PL server if I want to use a PL database, or I simply use a Hadoop/Cassandra library if I want distributed data. If I want to work with a traditional relational database then there are libraries for doing that too. Combinations and choices are endless. I will however continue to work on distributed data with PL as I think it's possible to make something more dynamic and simple than current solutions in that area. On Sat, Jan 14, 2012 at 8:28 PM, Alexander Burger <[email protected]> wrote: > On Sat, Jan 14, 2012 at 06:49:34PM +0700, Henrik Sarvell wrote: >> That JSON implementation is too simplistic which kind of reinforces my >> point, writing good libs take time and for that to happen you need a >> ... >> Here is for instance Clojure's version: >> https://github.com/clojure/data.json/blob/master/src/main/clojure/clojure/data/json.clj > > Wow, that's really overkill! > > Why do you think that the example JSON implementation is too simplistic? > Can you say what is really needed in addition to that? It supports all > data types which exist in PicoLisp: > > - Symbols (transient symbols (strings) only, as JSON doesn't know > about internal symbols) > - Numbers (fixpoint only, as PicoLisp doesn't know about floating > point) > - Arrays and Objects (both represented as nested lists in PicoLisp) > > Derived types, like "null", "true" and "false" can be easily handled on > the application level. Or you might trivially extend the example, and > map them to NIL and T. > > What else do you want a JSON interface to do? If you make so much fuss > about something such simple, it is no wonder you miss libraries > everywhere ;) > > You seem to support the typical bloatware philosophy: First put > everything which comes to mind into a "library", and then see what can > be done with it. This is definitely not the PicoLisp way. > > Cheers, > - Alex > -- > UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe -- UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
