janl

6 ms·

31.
by janl 7y ago
That’s another great point, an exactly why we are doing this. It is a best practice already.
32.
by janl 7y ago
In CouchDB terms, you’d store data like this in attachments, not as raw JSON.
33.
by janl 7y ago
FoundationDB needs is a consistent (as per CAP) database, to make that work in a distributed fashion, there are limits on distributed transactions in size and time. CouchDB needs to adopt those in order to move to FoundationDB. The 3.x seri
34.
by janl 7y ago
Check out https://github.com/langalex/couch_potato/
35.
by janl 10y ago
Thanks, that's gonna be the limiting factor then, developers not finding a way to represent some of their storage needs on this platform. It's a fair trade-off, but hardly neither objectively worse or better than couch-sync. I&#x2
36.
by janl 10y ago
Oh, and while there is still room for improvement, we've improved the server-mobile sync case by an order of big-O-magnitude. And this is a first class design target for the future.
37.
by janl 10y ago
How is "conflict-free sync" done? The usual approach is last-write-wins, which is just a euphemism for "randomly losing user data", or CRDTs or Operational Transforms, which severely limit the data models one can sync. I
38.
by janl 10y ago
CouchDB doesn't have any iOS code, are you perhaps referring to Couchbase?
39.
by janl 10y ago
That wasn't production ready at the time and I'd argue it still isn't.
40.
by janl 10y ago
It didn't make the cut for 2.0.0, but we definitely should have a nice message there on the command line. Sorry about that! :)
41.
by janl 10y ago
Oh, well aware of this. It’s just that we’d have to secure the funding, unless you wanna sponsor :)
42.
by janl 10y ago
CouchDB is the only one of those that a non-profit could deploy at scale without paying loads of money for licenses or support.
43.
by janl 10y ago
it’s definitely no related to MangoDB
44.
by janl 10y ago
It’s MongoDB inspired obviously, but at the time MongoDB asked IBM/Cloudant to not call it that. They settled on Mango. The Cloudant product then became “Cloudant Query”, so CouchDB easily inherited the Mango nickname. We like it :)
45.
by janl 10y ago
Couchbase has a different API, so it is not an “upgrade”, more a rewrite. CouchDB 2 is 99% API compatible with version 1.
46.
by janl 10y ago
The book definitely needs an update. Just a heads up, Damien didn’t work on that.
47.
by janl 10y ago
CouchDB and PouchDB helped with the Ebola outbreak last year: https://www.youtube.com/watch?v=1sLjWlWvCsc Of course there is loads more, but this is the stuff that keeps us devs going.
48.
by janl 10y ago
We’d definitely love a Jepsen write up, preferably by @aphyr himself. We just need to find out how to get that going :)
49.
by janl 10y ago
> - faster bulk indexing With clustering you now get that. By way of “oversharding” even on a single node. Speed up is linear with number of shards / CPUs > - space reduction, 2.0 has the better compaction format. There are still
50.
by janl 10y ago
Except, you know, for the “Download” headline that I specifically put in for you ;)
51.
by janl 10y ago
The admin interface has a convenient “Setup” menu point that does all this for you :)
52.
by janl 11y ago
The old adage goes: you can only fix what you can measure. In the same sense, Greenkeeper measures the churn in your dependencies, and allows you to manage (fix) the requirement for change that comes with it.
53.
Sustainable Open Source(writing.jan.io)
2 points by janl 11y ago|0 comments
54.
by janl 11y ago
Not at this point, we are aiming at deep integration with the npm/GitHub ecosystem. Happy to talk to others on how to do it, though, just get in touch: hi@greenkeeper.io
55.
by janl 11y ago
No plans yet, just marvelling at the opportunities :)
56.
by janl 11y ago
Heya, you summed up the problem perfectly and we are not trying to be all clever solving this unsolvable riddle. All Greenkeeper does is send you a Pull Request, which then runs your test. Only when you as the maintainer are satisfied this
57.
by janl 11y ago
Greenkeeper dev here, Another fun thing we can do with this is, say Node 5.0 comes out, we send a PR for everybody’s .travis.yml, to also test against 5.0 and see if a package is still compatible. And all that with without the maintainers h
58.
by janl 11y ago
Our hope with Greenkeeper is to get all of npm on it, so we all get to benefit from it. In addition, we could do things like pro-active issue-opening. Say Underscore releases a new version and Ember uses it, gets a Greenkeeper dependency bu
59.
by janl 11y ago
The problem here is with your downstream users, an `npm install` two months after your release might install a broken sep for your end user and create a support request for you. This is a bad situation to be in if you are doing this for Ope
60.
by janl 11y ago
I’d love to take this discussion offline with a number key people. We have the Web Technology Fest in Berlin ( http://wwwtf.berlin formerly http://jsfest.berlin)in September (leading up to JSConf EU & CSSconf EU)

More ›