I found it hugely useful in the .Net world. With closed source, obscure errors cannot be as easily tracked down, especially when they are not covered by MSDN or a prominent blog. A couple years after switching to an open source stack, I barely use it at all, and when I do finally hit a wall and ask a question, I get an answer ~20% of the time (compared to 90%+ when I was in .Net). I am a huge fan of SO, but good docs and readable code go a lot further.
Looks very cool. Pricing is a bit confusing though.
1 user, 1+ user, unlimited users
What does 1+ user mean if not unlimited?
Also, row limits are not listed in the top tier, making me think that they are either unlimited, or that the go until they break due to a technical limitation somewhere after 5k rows.
There's no limit to the number of Pro users that can work together with the same data sources.
> Also, row limits are not listed in the top tier, making me think that they are either unlimited, or that the go until they break due to a technical limitation somewhere after 5k rows.
Enterprise deployments can customize the row limits (default is 5K). There's no technical limit on the server side though some browsers slow down at very large limits. Using Chrome we've had no issue with 50K+ rows. It doesn't come up in real world use cases though as people dealing with more than a couple K rows usually want the data exported (which we support separately) vs just scrolling through a result set.
I got distracted and was looking at your other posts, when I noticed that the 5 or so I had looked at all said "1 day ago". I thought you must be a lunatic until I actually went back and read this post and saw that your dates had been lost. :)
I have lost a couple blogs over the years, mostly out of laziness, letting them expire. I got an itch to write some posts recently and wanted to set up a new site. This time around I decided I would do it with something git friendly, so that I could throw it on github and forget about it if I lost interest. I wrote a "from scratch" site with this in mind and it was working well, so I open sourced the core engine today. It runs on express and is about as bare bones as it gets. http://morganherlocker.com/post/badblog
> But if he can, we’ll get Node v0.12 delivered a lot faster and have a stronger community.
And of course, Strongloop could not help but make another half way claim that they are the ones "in charge" of node. This current stuff aside, I just cannot believe their lack of shame when trying to take commercial credit for a community project.
Ben is not a Joyent employee, but a Strongloop employee/cofounder. I Cannot say I am terribly surprised. Strongloop has rubbed me the wrong way from the very beginning. Since they have launched, they have displayed all the integrity of a used car salesman. I know they have some very strong core devs, and I know they are not all like this, but their public image has been max-sleaze ever since they started marketing in shady ways suggesting that they were the creators of node.js.
The stuff we are going through right now might seem scary, but McCarthyism was not exactly the golden age of trust. It was not so long ago that "mainstream" society did not trust blacks, working women, the japanese, or jews. We (royal "we" here, emphasis on the royalty) still don't seem to trust gays, atheists, or many other groups. Mistrust is what keeps humanity sharp, but it is also what has been holding us since the beginning.
