jchrisa

129 ms·

1201.
by jchrisa 17y ago
It's about the technology being more generic. If you control the service (obviously you don't with YouTube) the host should have safe harbor. If a host controls the service, they are responsible for it's content.
1202.
by jchrisa 17y ago
"Given modern trends, if a given query isn’t scalable vertically, it also isn’t scalable horizontally, which makes SQL fundamentally unscalable, period."
1203.
Education and demographics: how do they affect unemployment rates? (1988)(bls.gov)
1 points by jchrisa 17y ago|0 comments
1204.
by jchrisa 17y ago
Good work imagining! Now go make something! Building tools for the personal web is no harder than writing a Hacker News clone. It just requires more imagination.
1205.
by jchrisa 17y ago
The difference is that YouTube profits from the videos, EC2 rents generic capacity to someone who could choose to profit from them.
1206.
by jchrisa 17y ago
You shouldn't be able to do whatever you want. Unless you only want to do good things. Law isn't perfect but it is meant to be applied impartially.
1207.
by jchrisa 17y ago
As far as making the tech easy for civilians, it turns out that's what I spend the majority of my time doing. Slowly. Working my way up the stack takes time.
1208.
by jchrisa 17y ago
I actually said I think services like S3 / EC2 / Rackspace should have safe harbor protection, as they are as content-agnostic as possible under the law (like landlords, not nightclub owners.)
1209.
by jchrisa 17y ago
So you'd rather be protected by the feudal lord (Google) than stand on your own? Make no mistake that's what you're saying.
1210.
by jchrisa 17y ago
I've got a blog post about why this might not be a bad thing here: http://jchrisa.net/drl/_design/sofa/_show/post/Imagine-There...
1211.
Imagine There's No YouTube(jchrisa.net)
82 points by jchrisa 17y ago|73 comments
1212.
by jchrisa 17y ago
Jan found the LOLs
1213.
by jchrisa 17y ago
I think he said "Contemplorary" which is where the LOLs come from.
1214.
AGPL != Awesome GPL(davispj.com)
11 points by jchrisa 17y ago|29 comments
1215.
by jchrisa 17y ago
Couch and Mongo are optimized for different use cases. CouchDB is pretty much the only (open-source) game in town if you care about offline replication. It is also designed for extreme reliability and concurrency. CouchDB's programming mode
1216.
by jchrisa 17y ago
Don't worry, 2010 is gonna be the year CouchDB lands the cluster-awareness (among other things). We've been moving forward steadily since 2005 and we're not stopping anytime soon.
1217.
by jchrisa 17y ago
It's true. We had a really great fundraising experience (awesome opportunity to meet smart people, but it's a lot of driving if you live in Berkeley). We're all about CouchDB adoption, so we'll be working to lower barriers to entry for new
1218.
by jchrisa 17y ago
The thing we see with CouchDB in production is that, although under low load we aren't the fastest kid on the block, as you ramp up concurrency (hundreds or thousands of simultaneous clients) with mixed reads and writes, on a multi-GB datab
1219.
by jchrisa 17y ago
Thanks. The important thing about CouchDB is that it allows you to write applications you could never dream of, with the standard LAMP stack. p2p replication makes a huge difference.
1220.
by jchrisa 17y ago
Thanks for the feedback. I think I have a little too much material in the talk for the format. The same slides took me 2 hours to get through at a user group meeting that night. My next goal is to cut the talk in half. Maybe 2 talks, one on
1221.
by jchrisa 17y ago
@antirez the thing is that CouchDB is designed for replication. Every CouchApp is a p2p web app. This is different from the web we've known before. CouchDB will never be as fast as some other k/v stores, but http based peer replication give
1222.
by jchrisa 17y ago
This site is a test of the technology, but not really in the sweet-spot. The real use case for pure CouchDB applications is the p2p web, where your application code can be replicated from one database to another, along with the data. This m
1223.
by jchrisa 18y ago
oops, commented when I meant to reply. Here goes: CouchDB is different from a relational DB in so many ways its almost silly to be doing the comparison. However, many people use and understand SQL, so we must show them what differences to e
1224.
by jchrisa 18y ago
CouchDB is different from a relational DB in so many ways its almost silly to be doing the comparison. However, many people use and understand SQL, so we must show them what differences to expect. Your argument about normalization being mor