Came here to say the same thing, this is a must have. They should allow to pick "remote" or "telecommute" for people posting jobs too. For now I see posts using different wording such as "anywhere", "telecommute" and "remote". This is very important for devs.
As I saw the tweet I became uneasy, followed the link and, sure enough, it's my post he's referencing. That's a bit disconcerting, I feel responsible for trashing MongoDB all over the internet. At least my conscience is lighter because everything I wrote was true...
For pete's sake, for the last time: you were using 1.3.3 which is UNstable and not production ready. Its developers know it's likely to have problems and you proved them right. What you wrote was not "true". You found a bug in beta software.
This instance of CouchDB data corruption is in a production-ready version, aka a stable version. No doubt eventually MongoDB will hit a similar issue and then we'll all calm down and stop poo-pooing all the hard work everyone is putting in building these databases.
For the zillionth time: I moved to 1.4.0 after 1.3.3, and there was data loss on the stable version too. Seriously, what's up with everyone's reading comprehension?
My understanding is that you stopped using MongoDB and started using SQLite. To me, that means that you are probably not a Linux or Mac or Windows user because they all can crash and lose your data. Likewise you are not a user of any office suite because you've likely to lose data from all of them. Likewise, even ISPs can disconnect you half-way through a transaction (say buying something or editing a blog post) and so you will stop using them because of that.
So good luck with historious. I think it's an interesting idea, but by your logic I shouldn't try it in case it crashes and loses my bookmarking data.
Yes, it was true that the 32bit version of mongodb that is limited to 2gb would lose your data if you injected more than 2gb in it, shame on mongodb...
Jesus, I can't believe people still defend this shit. I don't care if MongoDB can store ten jiggerbytes, it should give an error when you're trying to insert more than that. When the hell did corrupting your data become acceptable for a datastore?
I'm confused, are you talking about me or MongoDB? If you're talking about me, I don't think I made a mistake, and if you're talking about MongoDB, the guys on IRC were very civil about it and did say that silently corrupting data was the wrong way to go about it.
It's these apologists who are giving MongoDB a bad name, really, because the guys on IRC were nothing but helpful about it.
The 32bit version is available for convenience, nobody uses it in prod. You can't complain that a simple testing tool limited to 2gb can't store more than 2gb.
You used a dev version of a tool that is not meant to be ran in production or for any serious task and then complained it didn't work with your attempt. As this bug is not present in the real prod version of mongodb, it doesn't make sense to criticize mongodb for it. Also next time RTFM before using a tool you don't know much about.
fwiw, the only error Damien made was failing to review some patches other people wrote. Also, this issues is much less serious than the Mongo problems as it's A) localized and B) fixed. Eg it's a bug not a design decision.
Errors:
- not reviewing
- poor testing procedures
- new code in 1.0.0????
Why your claim that its not as bad as mongo is crazy and self serving:
- poor code quality is MUCH worse than a design you don't agree with. how could anyone trust couch? at least mongo is upfront about their design decisions, whether you agree or not
- the couch team has gone on and on recently about how unreliable mongo is, and yet here is this...
- there were a number of unanswered questions on mikeal's blog - sadly he took them down - probably because he didn't like them. maybe his couch db lost the data and he couldn't figure out why...
Also - really nice job attacking mongo while you guys have a MAJOR bug... classy and proessional...
Another funny thing - how long has 1.0.0 been out? 3 week or so? and this was just found? so what, there are like 10 people using couch in production?
And i'm sure this will be down-voted by the couch fan boys - but this ridiculousness has to be addressed.
Pure trolling. New user. Jabs at MongoDB aside, CouchDB has acted quickly and professionally to the kind of rare unfortunate critical bugs that can (and do) happen to software projects. This quality of response creates trust, not diminish it. Shit happens. What matters is that you admit the mistake and fix it as quickly and publicly as possible. Props to CouchDB.
The reason the bug took so long to surface is that it is only triggered by an edge case. Most users will not experience issues. After two reports of missing data, the whole team focussed on getting to the bottom of it. This is because we take data integrity seriously.
I don't believe the emergence of a single bug tarnishes an entire codebase and labels it as poor quality. This situation seems like a lapse of judgement in process, which they've fessed to and provided a path to correction for.
WebObjects is/was NeXT's web application development framework. Think of it as being like the iPhone SDK for the Web (http://en.wikipedia.org/wiki/WebObjects).
Interestingly, back in the 90s WebObjects was programmed using Objective C. In 2000, Apple (post-NeXT acquisition) overhauled WO to use Java. This was around the same time that the Cocoa/Java bridge was released for building native Cocoa apps in Java.
WebObjects seems to be on life support inside Apple today. They haven't released a new version in about 20 months, and there's not much sign they'll update it any time soon.
Others have pointed out that WebObjects is an actual Apple framework for making web applications. If I'm not mistaken, Dell used to use it for their online ordering site in the late 1990s. Apple used it also for the first iTunes Store iterations (not sure what they use today). I only have a superficial understanding of WebObjects but it looked a lot like a Rails/Django style framework with Objective-C Script or Java, and about 10 years too soon.
I'd be curious to see how accessing an open wifi can be made illegal. I mean, it's legal to scan for wifi networks, this how we all connect to wifi networks. Now, what happen when my laptop finds an open wifi network? I if I click to connect to that network, my laptop wifi is going to ask permission (through handshake and protocol etc) to the open wifi which is going to accept and grant me permission. How can asking first and receiving a positive response to enter an open wifi be illegal? I mean it's not like I actually broke into it or cracked the password, I actually asked first and got an inviting response.
I'd be curious to see how accessing an open wifi can be made illegal.
Using the magic words "expectation of privacy". If we assume that the general public is clueless about computers and thus many people expect that their open wi-fi is private (even though technically it isn't), then there's a problem. Also see the debate about thermal camera scanning of homes.
...my laptop wifi is going to ask permission to the open wifi...
But that's not what Google did; they were sniffing traffic without associating, so the APs had no opportunity to deny access.
What's the point of enacting laws that are impossible to prove in court? How can I, a user that doesn't even know that I shoudl have a Wifi password, prove that someone passively received radio waves coming out of my house?
The answer is: you can't. If you can't prove someone did something, it's dumb to make it illegal.
People here are probably not going to like this but I will not trust Duck Duck Go until they release their whole source code and allow me to run my own instance. For now, there's still a middle man called Duck Duck Go that I have to blindly trust. I salute his efforts to make his page privacy friendly, but as long as there is a middle man and no one to check his source code to check if he's not sending anything about us, there can't possibly and technically be any guaranteed privacy. Any one who has taken basic cryptography course would agree with that.
Unless they have constant access to your servers to make sure you don't make any changes afterward... But even then, the only way to be sure about one's privacy on the net is to run your own server, no web service can beat that kind of privacy. I personally prefer Google to Duck Duck Go by the way (especially using chromium search feature by pressing TAB) but if I really really cared about privacy to the point of giving up on Google, Duck Duck Go wouldn't be enough, sorry. Good luck though.
Stallman usually talks about software when it comes to freedom. I wouldn't make any conclusions on his opinion about "freedom to kill" without asking him for clarification.
