htsh

No, we have migrated prototypes to redshift. You just need to keep your database logic in a separate layer, which is something one should do anyway. I say "I think" because I agree with you that most will not. If you implement mongo such that you will be stuck on mongo, then do not use it. You always want to have a layer that handles your database operations, with any database, but obviously you are safer in SQL-land as switching costs are lower.

I do not think the "cancer" metaphor is valuable here. What you describe are bad ideas that I agree are bad ideas but really one has to know the tool they are using and what it is bad at.

I think the thing you describe can happen but that is just poor planning more than anything. Why does the database have anything to do with the design of your API layer? That sounds bonkers. And I would not blame the underlying database tech. I would blame the implementer.

But really, please consider that many of us have, or are as we speak, losing loved ones to a deadly sickness which you have compared to a poor database implementation.

I have used Mongo for 9 years. First at a game company, then for several prototypes that made it to production in my current role. We have not lost data once. Many of my friends at medium-sized companies use Mongo for much larger projects and have not lost data a single time, either.

And it is it not just me and my friends -- HSBC recently announced they are moving 65 of its relational databases to mongodb. I am not sure that is wise, but I think it furthers my view that data-loss is not a concern in many contexts.

The data-loss thing was most certainly real, but has not been since wiredtiger if one manages it the right way or uses it as a service.

I would not say that I would say that HN != reality, maybe !== reality :). Neither side of the debate is wholly right, and neither is wholly wrong.

The reason I use it is that for many projects, all you need is a relatively fast JSON document store, and mongo is so developer-friendly such that speed-to-prototype is so much shorter than anything else I have used in 25 years of building database-backed applications. Rethink was the only product that I would have used in its place and I was extremely sad to see it go. I agree with the commenter elsewhere in the belief that it would have thrived had it survived. I was using it for my personal/learning projects and was ready to switch everywhere.

We have stuck with Mongo in production for a few products, one relatively large, and I think if you have separated your concerns well-enough, it is okay developing in Mongo while leaving yourself a path to postgresql or something else. You need to prove, first, that the thing you are building is useful, and Mongo will let you get to that really fast.

I believe what is happening here is that the happy folks are quiet, and the aggrieved folks' experiences are real but it likely was a bad fit for their particular situation. For the subset of situations where we use it, it has allowed my teams quickly in our experimental work.

All of that said, I work in an innovation space where we throw a lot of things at the wall to see what sticks, and our time-to-prototype is often a few months at most. For us, it has been a godsend, but our situation is rather unique.

-h

signal? the desktop apps are available now on mac/windows/linux and are pretty good.

the tougher thing for me has been the network effect and getting folks to make the jump since _everyone_ is on whatsapp.

I think it's because the more restrictive license of the Linux kernel (GPL) vs the more permissive BSD License. What Google is doing technically doesn't violate the GPL but it kinda gets away doing the sort of thing copyleft licenses were intended to prevent. People have been upset at Ubuntu forever too since they started including closed source drivers.

How does this compare to Webstorm's autocomplete functionality (as it's one of the primary reasons I started using WS years ago)?

This is primarily pre-2011 CPUs, though? Looks like everything since Sandy Bridge and Bulldozer will be okay.

I guess we never know what's running on our cloud instances.

Until there's something like CUDA for AMD isn't this going to be difficult? I don't know the area well, just curious.

(How good is openCL when it comes to this sort of stuff? Could they support it without crazy effort?)

Yup, I did and mine was fine. I mean I used the hell out of the phone since it came out and I knew the battery was bad just based on the cycle count and my heavy usage.

I believe the tech checked as well right when I brought it in. What was weird was they told me the battery was fine and something else was wrong. And the phone has been fine since the replacement.

And I think coconut is pretty reliable. We ran it on a couple of coworker phones before bringing my phone in, and mine was by far the lowest. Everyone was up in the 80s and mine was in the 40s. It ran multiple times with the same result.

The apple tech told me green means it's in the 80s.

One tangential weird experience: My iPhone 6s plus battery went obviously bad, as in reduced battery life and really big jumps down from 100 -> 70 and then from 40 -> 10 from minimal use. After months of dealing with the bad battery, hooking it up to my mac & running Coconut battery showed it was 46% good.

So I took it to the store for an official replacement (I decided I would pay for it). The genius ran a diagnostic which showed the battery as fine (green, he called it) and almost immediately started to tell me why it may be something else in the phone and started pointing me towards buying another phone instead of getting the battery replaced.

But for some reason their diag tool is worse than coconut battery or just wrong? If my battery were 60-70% good and they had lowered thresholds that's one thing, but my battery was long gone and they told me it's fine. And of course I insisted and the phone is fine now with a new battery.

I know there's probably a decent explanation for it but it certainly felt like they really wanted me to buy a new phone, and that their diag tool perhaps isn't the most truthful right now when it comes to battery health.

Seems waste has been covered well but I was curious about what people think about these services and how they relate to food deserts. I think there are at least a few interesting takes on this.

First, this helps a ton. Fresh food isn't available in a lot of areas and this makes it easier for both current residents and it reduces friction for people looking to move to these towns.

On the other hand, will a societal trend towards this lead to the creation of more food deserts? These services are not cheap, and food deserts tend to be in impoverished areas.

Zelda.

I get (and agree) with your point but aren't they making it harder than other coins here by limiting the pre-sale to accredited investors?

A small independent game is where I've used it before as well. And currently I'm working on an app/game sort of thing where it makes a lot of sense because we're iterating often and fast. I like that it kinda gets out of my way and just works, though perhaps I would not so much had I experienced the data loss others speak of.

I'm interested. When you say almost, can you elaborate on any remaining use cases when you'd use Mongo?

If you have a microcenter near you, you get the cpu / ASRock mini-itx mobo (with dc input) for < $50. I have a couple of these in tiny m350 cases and have been very happy.

Thanks, I had trouble with arrow keys working when I tried it a while back but I'll give it another go with the "-run {bash}" option. And the Mac autocorrected "htop" to stop.

Can you run things like nano & stop and navigate around with arrow keys?

I can see the value of the standup but I find daily to be too often.

The best teams I've worked with have staggered them to either M-W-F or T-R, primarily because the work we do require more than a day. And depending how one works, a daily standup every morning makes it tough to get a good night's work in.

I often point people to PG's relevant essay during discussions about this: http://www.paulgraham.com/makersschedule.html

And it works on Linux well, from early on.

It's not that bad. It runs node well and I can ssh out of it and do the things you describe. Powershell is an improvement from command prompt but it's still not as nice as terminal / iterm / gnome terminal.

And it's ubuntu, so you can apt-get install build-essential & whatever else you need. It doesn't do upstart or /etc/init.d services (like if you wanted to run mongo as a service) but it runs mongo instances fine for me while I develop locally.

I spent my first full day developing on a win10 box this weekend & it went fine. But since I've switched to webstorm for most of my development what o/s I'm running hardly matters outside of keyboard shortcuts.

For anyone considering switching, I'd recommend buying the "pro" version as you can use the services feature to turn off things like cortana or the automatically-restarting windows defender. It would like to do a whole lot of spying by default, more than I'm surprised people are comfortable with.

But as many in this discussion have said, please give linux (and especially gnome 3 a shot). It's a pleasure to work with, and if I could stream legal tv services and run photoshop there's no question it's what I'd run.

Can you expand upon this please? I'm considering doing the same now but this gives me pause.

Yes and no. Though I don't disagree with any of the criticisms or other comments at this level, for some of us MongoDB has been pretty good in production and we haven't experienced data loss. It all depends on your use case.

My first experience with it was for a social game running off of 3 mongo servers in a replica set & here at a large healthcare company we use it for several internal CRUD applications (again in 3-server replica sets) which we continue to iterate. In these use cases, Mongo's flexibility and ease of making changes trumped it's shortcomings. My understanding is that many social games still use Mongo to store player data as our studio was told to use it by a large publisher.

My take is that it's good for building prototypes and it's pretty flexible to both change & migrate data in and out & Javascript devs pick it up relatively quickly. But I also think one should be well aware of it's shortcomings and be careful not to use it where those things are of importance. More often than anything else, I recommend PostgreSQL when other people ask for a general-use db but I'd likely would pick up Mongo myself simply for speed of development.

Lastly, being part of the "MEAN stack," we can point junior devs & interns to one of the many books that cover the stack & they can learn best practices get up to speed quickly. There's an advantage to having books & a slew of SO answers to refer to in that other devs aren't pulled off of their work to teach. We literally had interns committing code on Day 1 of their jobs last summer as they came in having read up on our stack.

Regarding claims MongoDB has made, which I've only been made aware of the last two days, I don't think there's any defending that & it makes my itch to checkout rethinkdb a bit stronger than it was 2 days ago.

The successes tend to be quiet. And folks who are happy don't take to the internet to defend their choices.

I've been on two straight projects where Mongo has been fine, no better or worse than an SQL database, but certainly nowhere as bad as one would assume reading all the negativity around here. I have experience with it being stable in two different contexts in production (social games, a very common use case, being one). A search for "social games mongo" should show you some success stories.

The thing that makes it a good choice for me when starting a new project is that you don't really think about it, especially if you're following lean startup methodology where the goal is to get a product into the hands of the users as quickly as possible & you anticipate changes to your models. Mongo is pretty fantastic for this. And when things stabilize, moving data really isn't that bad or expensive if you modeled based on this assumption (which you should). And now that PostgreSQL has a pretty good JSON datatype, it presents a pretty painless path if and when you outgrow Mongo.

To me one of the more troubling aspects of this is that in 2013 and after 12 years, the specialists we have fighting this "war" still have trouble distinguishing between Hindu & Muslim (though obviously Muslims should not be treated like this either). It might be easier for me b/c I'm Hindu but just looking at a name is usually enough to at least get past that part.

Seconded. For our production game servers we've only used EC2 but a couple of us have started working with digitalocean for our own projects & are very happy with them all around.

haven't used it but this allows you to share your location for a limited period of time:

http://www.glympse.com/

My best friend (and first co-founder) died in a crash after hitting a tree at 48mph in a BMW 5-series.

I used to hold the same assumptions you did, particularly #'s 4 & 5. In my friend's case, the firewall gave & the engine came into the cockpit & exploded, splitting the driver in half & burning my friend past the point of recovery.

The fireball from the explosion marked the tree, the street, & the lawn for a 20-30 foot radius around the crash site, unbelievable that it could be created by one car.

It made me realize that the engines in these cars are optimized for serious performance and they can only be so safe. In this case, a C250 is getting 200+ horsepower out of a small 1.8l engine. Cranking at 80mph, I'm not sure there's anyway to avoid this sort of explosion or for the safety measures to kick in fast enough.

Just my two cents. Obviously I don't know the details here, but I did want to add that even a 48mph collision into a tree at a particular angle can very well create a really large explosion.

-h

Why not hire a devops guy & rack your own hardware? Or get some massive computing units at amazon (just as good but more expensive)?

This reminds me of the excellent 5 stages of hosting story shared on here from a while back:

http://blog.pinboard.in/2012/01/the_five_stages_of_hosting/

I believe a mistake of omission is different from being unable to distinguish a period and an apostrophe. Also, we are commenting online with each other, not responding in an official capacity to customer service inquiries.