# Sorry for ranting a little
all very interesting

# even the unabridged code is far from readable
# I think my attraction as a novice to Camping was for its clarity
these two things are inconsistent? but this brings it around:
# I'm being incoherent

# quickly I ended up using models in my apps that were just representations of 
the filesystem, or of some other API, or of documents in CouchDB
yep, to me a 'model' at request time is always based on inside some CSV or JSON 
file, an Email, an IRC log, something curl piped to a file in a script run by 
cron

the notion that you'll be writing new ruby Classes for each class of resource 
in th datamodel, and new "routes", and "migrations" to prime DB tables seems 
fundamentally crazy to me, and with rails' mindtrain it was copied on 
sinatra,camping,merb,ramaze

# I've mostly moved onto working in Python
i tired of ruby around 2007 after writing the webserver i actually wanted, 
rather than the "framework" i didnt want. it is baroque for the possibility of 
a runtime type-error failure to even exist. with type-inference, your Haskell 
or OCaml code is not more verbose than Ruby. i still maintain my webserver 
since it works fine but i'd never start a new project in ruby at this point

# their community actually brags about it, and makes a point of how much easier 
your life could be if you use it
the Rails community did this quite a bit too. all the alphabloggers like 
Ezra/Tom/court8nay and countless HN/Reddit mobs. i think it ties into human 
psychology of self-apprised status somehow, but it is just silliness, like 
obsessing about getting into a "VIP Room" at a club

> Rack does seem to be increasingly a source of pain. The guardians of the
> rack spec haven't done a good job keeping up with new tech.

Rack is really simple, in goes a Hash of request environment, out goes a 
status-number, response environment + body. essentially thats what HTTP is. 
after making handlers for ebb, flow, mongrel, it was nice to delete all that 
code and just write a rack handler - they were all so similar anyways

as for streaming, i was able to trivially implement 'tail -f' using rack [0] am 
interested in hearing what your thoughts on how Rack should change

[0] http://gitorious.org/element/element/blobs/master/ruby/W/tail.rb
_______________________________________________
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list

Reply via email to