Tweets for 2009-10-22
- RT @debasishg: RT @janl Erlang > C++ — by @metabrew: http://jan.io/HZ0R #
- @jboner avro seems the most well thought out but doesn't have extensible types (eg date/time in BSON). Useful for embedded semantic meanings in reply to jboner #
- RT @dalmaer: RT @cbeust: "Uh oh, somebody woke up the Lispers and told them about Clojure… we're in trouble" http://bit.ly/Xj0zn #
- @dehora @phunt – thanks for the avro tip .. looks quite interesting in reply to dehora #
- ??What?? RT @debasishg,@jboner,@niclasnilsson Architects do the right things in the wrong way, agilists do the wrong things in the right way #
- NoSQL is such an inappropriate name. NoTables at least makes a little more sense. #
- RT @simonw: Blogged "Why I like Redis" http://simonwillison.net/2009/Oct/22/redis/ #
- Twitter: You Say Transparency, I Say Vulnerability (via @thecancerus) http://ff.im/-ahUpT #
- memcached Functions for Drizzle now in main tree! http://ff.im/-ahXtY #
- @nawroth hmm .. thought they didn't have tables as much as just 'buckets'. Oh well .. so nosql still doesn't make any more sense
in reply to nawroth # - William Cook's ECOP 2009 speech (via @softmodeling) http://ff.im/-ai0zr #
- @edlich but its a pain to explain to every new participant "well NoSQL is not about not having SQL, its about ….."
in reply to edlich # - Interesting views on Erlang and Ruby – (37signals) http://ff.im/-aiwFd #
- Guido's Proposal: Moratorium on Python language changes http://ff.im/-aiwFe #
- RT @surya_s: New blog post: REST: DELETE operation and tunneling http://bit.ly/OHZm7 #
- @KentBeck Thats a great question .. still thinking .. best thought so far – FlexiStore (though not good enough yet
) in reply to KentBeck # - @KentBeck I see where u r going with this (a) unconstrained & composite storage (b) store resources not records (c) shard/scale horizontally in reply to KentBeck #
- .@KentBeck I think there is a merit in attempting to define nosql in terms of what it is rather than what it isn't in reply to KentBeck #
- RT @igrigorik: more nginx goodness, this time an upstream pool manager (pseudo haproxy features): http://bit.ly/4txN65 #
- @psnively Those are the paper joints between the otherwise steel rods
in reply to psnively # - @davetron5000 @psnively would it be fair to state that spring xml is the duct tape for java plumbing
in reply to davetron5000 # - @KentBeck Agreed .. and I'm aware of many more who wonder why we need a different datastore than the RDBMSs. NoSQL as a name doesn't help. in reply to KentBeck #
- @protoiyer Good suggestion. Will keep in mind. Thanks. Wasn't aware thats how it worked
in reply to protoiyer # - Linus in the windows 7 booth (photograph) http://bit.ly/2O35et
# - @psnively thats a nice one
in reply to psnively # - @debasishg The Big Big problem with annotation based DI is its hard to reconfigure on a per deployment basis – not practical for product cos in reply to debasishg #
- @debasishg OTOH the overall externalised configuration supported by Spring really helps product cos much more than single deployment s/w in reply to debasishg #
- Avanade finds growing Enterprise enthusiasm for the Cloud http://ff.im/-ajwd9 #
- @KentBeck I am done with storing large & complex objects as single blobs or 100s of name value pair rows in an RDBMS.. that is just gross
in reply to KentBeck # - @KentBeck Primary Need : We need support for flexible/arbitrary schemas with complex depths – RDBMSs don't dance well in this space. in reply to KentBeck #
- @KentBeck Secondary Need : Support for deferred processing required for analytics (eg. Map/Reduce). RDBMS don't do too bad a job here in reply to KentBeck #
- @KentBeck Tertiary Need (not one that I've felt strongly yet) : Distributed and horizontally scalable storage on commoditized h/w. in reply to KentBeck #
- @KentBeck Yes.. thats it! I'm looking for realistically or naturally structured data storage / persistence. Rocks compared to the term nosql in reply to KentBeck #
- @KentBeck Wonder if the term arbitrarily structured makes sense as well. This has been one heck of a conversation/Q&A so far +1:) in reply to KentBeck #
- Improving the Rubinius Bytecode Compiler http://ff.im/-ajK4p #