News for hackers. Stuff that matters.
Re:Pre-New-Year Check of PostgreSQL by systems on Wednesday December 25, 2013 @04:14AM (#6962652)
if they dont put the price online, it must be very expensive
Re:Pre-New-Year Check of PostgreSQL by LinaLauneBaer on Wednesday December 25, 2013 @07:29AM (#6962879)
I don't know this tool but I imagine they want to make very individual prices. They probably want to know who is interested in buying this tool before they tell you a price. Also they probably have lot's of (complicated) pricing models in mind and it would be too complicated to describe all the possibilities on the website.

I have worked in a similar project myself. We developed a very specialized tool for developers. Our boss decided that he did not want to mention prices on the website at first. Once we did some people complained publicly about the price although we invested months of development and the tool was pretty neat...

In general I think it makes more sense to tell the prices upfront and try to come up with a simple price model even if it means making compromises. You can always have something like this on your website: "If you think you do not fit in any price tier please contact us to find an individual price. The prices listed are meant to show what we have in mind for the general customers."

I would love to know the reason why some people think not having prices is a good idea. Care to elaborate?

Re:Pre-New-Year Check of PostgreSQL by spacemanmatt on Wednesday December 25, 2013 @08:19AM (#6962946)
Nutshell: Some clients expect a product with service and support behind it, and they expect to pay for it. In fact, if your price doesn't obviously include support you will be overlooked for not charging enough. Too low is not a plausible price. They will have to be charged more than a startup that wants to apply the tool using their own manpower and but for serious bugs, will provide most of their own tech support.
Re:Pre-New-Year Check of PostgreSQL by AndreyKarpov on Wednesday December 25, 2013 @04:51AM (#6962709)
PVS-Studio. Prices Dropping - http://www.viva64.com/en/b/0217/
Re:Pre-New-Year Check of PostgreSQL by evgryz on Wednesday December 25, 2013 @05:00AM (#6962720)
You can write us at [email protected] and receive individual price for your team.
Re:Pre-New-Year Check of PostgreSQL by derefr on Wednesday December 25, 2013 @05:16AM (#6962734)
Let's put that another way: if you have enough salesmen to operate smoothly given a high-touch sales process... your product must, on average, be very expensive.
Re:Pre-New-Year Check of PostgreSQL by AndreyKarpov on Wednesday December 25, 2013 @06:02AM (#6962787)
We don't have sales. We are developers.
Re:Pre-New-Year Check of PostgreSQL by oddx on Wednesday December 25, 2013 @07:31AM (#6962881)
Then you have enough developers to do salesman's work. This sounds even worse.
Re:Pre-New-Year Check of PostgreSQL by spacemanmatt on Wednesday December 25, 2013 @08:22AM (#6962950)
You guys are ruthless! Please see my earlier comment about different types of customers vs. pricing models. If you are a lean startup, variable pricing can work to your advantage. But it's certainly different than buying from commodity vendors who compete only on price.
Re:Pre-New-Year Check of PostgreSQL by ProblemFactory on Wednesday December 25, 2013 @01:14PM (#6963693)
I don't think people think that it's objectively too expensive, considering the time it saves for developers.

But without any pricing guidelines published on http://www.viva64.com/en/order/, it could be anywhere between $1k to $100k, and people assume without even asking that they cannot afford it.

Re:Pre-New-Year Check of PostgreSQL by Zancarius on Wednesday December 25, 2013 @07:22PM (#6964806)
I have a hard time differentiating between ruthlessness and contrarianism these days.
Re:Pre-New-Year Check of PostgreSQL by gfodor on Wednesday December 25, 2013 @09:47PM (#6965076)
You act as if there is a difference. These things mean the same thing.

And what do you mean by "hard time?" How can a temporal concept take on attributes of a physical surface?

beep boop

Re:Pre-New-Year Check of PostgreSQL by profquail on Wednesday December 25, 2013 @10:31AM (#6963179)
Is it more expensive than the potential downside if you run into one of these bugs? Sure, living dangerously allows you to avoid paying any up-front costs (e.g., the price of this tool), but on the other hand, without a tool like this it's hard to even tell what the probability of failure is or how much it'll cost you if something does fail.

Viva64 is not cheap, but it looks like an extremely solid tool; I'd imagine that for anyone with a reasonably large C/C++ codebase, it'd quickly pay for itself by offsetting time developers would otherwise spend troubleshooting, tracking down, and fixing bugs.

Re:Pre-New-Year Check of PostgreSQL by coolsunglasses on Wednesday December 25, 2013 @04:28AM (#6962669)
Probably cheaper than the shitty imitations of what this tool does in the web dev industry.

Talking to a vendor a couple months ago, they wanted $15k for a tool whose bug/security problem coverage they couldn't enumerate.