matt2000

This is pretty funny, and yes Spring itself is pure insanity, but it's not really fair to equate Java the language with Spring the framework.

Is anyone here using this? I'm interested in how well this works in practice. I'm finding AWS RDS to be less reliable than I'd like and this seems like a good alternative.

This to me feels really sci-fi since "we sent a rover to mars and another thing we already had hanging around took a picture of it." That feels pretty neat.

I thought there was a ban on radioactive materials being launched by NASA but I couldn't find anything about it, does anyone know any more?

It's a ridiculous statement. Microsoft has chosen not to make their UI look like 70's tape machines. That's a choice as much as Apple deciding that that's a good idea. There are a huge number of details and decisions in even a design that seems much simpler than others.

I agree with you, the wording from the WSJ sounds like they want the investment size to seem ridiculous. How about "quickly growing and profitable software company github..."

This is an awesome answer, thanks so much for doing the research here. So although the time of outage was much shorter this time, what I'm concerned about was that they seem to have violated their "AZs are totally separate" claim again, which would point to a still-lurking fundamental problem. Happy to be corrected here if I'm wrong.

Is it true that they're getting better? As I understood it, the major outage last year was a cascading EBS failure caused by one AZ, which this was too. I personally do not have the feeling that EBS behavior is completely understood in different failure scenarios.

I couldn't figure it out from the docs, do the plugins get approved by DuckDuckGo? Or does the user have to install them for their own account? I'm a bit confused at how you would mediate between different plugins trying to provide an answer for the same query, etc.

Hey, this looks like it might be exactly what I was looking for! I will definitely give this a try and let you know how it goes. I see that the pricing hasn't been determined yet though, which might be a factor if we're expecting higher volumes ultimately.

I have seen that, thanks for reminding me though. From what I can tell it's just for PDF generation though, right?

I would disagree and say the author is making a very sound argument. The web is becoming more like an application and so it makes a lot of sense to have a standardized UI, for all the reasons you mention.

Hi there, I'm a Docracy founder. The frustration that fueled the creation of the site was us trying to sign an NDA in my previous startup. None of the parties involved really knew what NDA would be a good one to sign, we both just wanted that part of the relationship protected but over with as quickly as possible. We were surprised to find that there wasn't a repository of accepted standards for some of these things, so ultimately we decided to take a shot at making it ourselves.

When the site works best is when a document becomes a standard (for example, a NYC startup NDA) and you sign it on the site. Then you know it hasn't been tampered with by the counterparty and you can execute it quickly and confidently.

Would some node.js experts mind weighing in here with pros and cons of this framework as they see it? I'm too new to node to really understand the tradeoffs here. Thanks!

Just out of interest sake what are people doing as a backup to heroku, and is failover automatic or do you have to make DNS changes?

It seems like a fair complaint that G+ should have a better mobile experience, not so fair to demand to not post on G+ anymore.

I was actually going to comment that I find G+ a great experience for these kinds of posts... oh well.