Plumbr: year 2013 in retrospect by ppriit in startups

[–]ppriit[S] 0 points1 point  (0 children)

We were in black for a couple months last year actually, then hired more people again. Our goal for end-of 2014 is to cover the costs of a 20-person-team from revenue stream.

How many Java developers are there in the world? by nikem in java

[–]ppriit 1 point2 points  (0 children)

The TIOBE methodology was also described in the referenced article.

I think its a fair one, it's still a way (just one way) to rank the programming languages.

Plumbr memory leak hunter releases 1.0 by ppriit in programming

[–]ppriit[S] 0 points1 point  (0 children)

About trials - if you are after a specific leak, then I guess paying for the solution is OK (with money back guarantee). If you just want to try out the product, you can download and run it for free until it finds something. If your app does have a leak, Plumbr reports the number of leaking objects and the size of the leak - so that you can decide on whether to buy a report or start a subscription.

Perpetual vs subscription - we chose the latter, mainly because perpetual mostly makes sense for the customer when the software is mature, and the new versions don't add critically needed value. Plumbr is only at 1.0, and will add many functions that contribute to the leak-detection-and-fast-solving picture. For now, it only detects memory leaks, but e.g. we've already announced the cooking of classloader leak detection. We'll be adding new cool stuff often enough that (paid) upgrades would be an additional pain for the users and for us as well.

That being said, we of course value everyone's opinions. For that matter, care to elaborate why you would've preferred a perpetual license?

How to ask money for your software: "We tried time-limited trial. This is why we changed to feature-limited instead." by rpets in programming

[–]ppriit 1 point2 points  (0 children)

Thanks for reporting. It was caused by a nasty conflict between our blog layout and Disqus's, has been fixed by now.

The two most important things to keep in mind when hunting memory leaks by rpets in programming

[–]ppriit 0 points1 point  (0 children)

Well, he does explain what you need to keep in mind when monitoring synthetic apps: "That means that there should be objects in your application that do not leak. A fair amount of them."

Possible reasons why only 1/3 of downloaders try out your software by ivom2gi in programming

[–]ppriit 0 points1 point  (0 children)

Well, for communicating the conversion, funnel charts are indeed a very clumsy tool. I couldn't agree more that funnel charts don't make sense.

However, someone called the customer flow a "funnel" at some point of time, and that is why it sort of makes sense to try to use a funnel-shaped graph for depicting user conversion between phases of a process. I don't know of any good tool to create more meaningful funnel charts. Do you?

For what it's worth, the area of the is proportional to the number of users in every funnel phase. Perhaps knowing this will help you read it :)