Live data from Hacker News

Polychart.js: An Interactive Charting Library

polychartjs.com

41–50 of 72 posts

Re: Polychart.js: An Interactive Charting Library

#41
post #25
post #3

$300 for a single developer, and the EULA says I can't transfer this license to another person?

We'll be reviewing the licensing option per feedback from HN. Please send a note to team@polychart.com, would love to hear more about what you think would be reasonable :)

In a world of so many wonderful free open source graphing libraries, it's hard to see any reasonable licensing option for this. It might help if there was a page that listed features that a developer could not accomplish for $300 in flot, highcharts, or ndv3, or other popular options.

Re: Polychart.js: An Interactive Charting Library

#42
post #18

This looks interesting, but what are the advantages of this over Vega, which is free? https://github.com/trifacta/vega

It's hard to evaluate when the projects are so new. It was a similar problem with Crossfilter/Datavore/Data.js/Miso Dataset when they all came out. If I had to pick, I'd go with Vega because I think it has the most potential to develop a community around it. Especially as a bridge between Python/R and D3.js through JSON. Think iPython notebooks, R Shiny, etc.

Perhaps this is not the right place but can you expand on the Crossfilter/Datavore/Data.js/Miso Dataset comment?

Re: Polychart.js: An Interactive Charting Library

#45

Earlier quoted context omitted.

I don't understand this per-developer licensing model. Not only is it completely non-enforceable but feels really out-dated and out of touch in the era of FOSS. I will pay for an awesome charting product, but I don't want to have to think about how many developers will touch the code, when, how or why. Something like a license per production site or an unlimited license makes a whole lot more sense to me and allows m…

I don't understand this per-developer licensing model. Not only is it completely non-enforceable but feels really out-dated and out of touch in the era of FOSS. Hasn't commercial software been licensed effectively per-user since forever? It used to be per-machine but these days with lots of developers using a desktop and a laptop I think it makes sense to say it's for one user at a time instead and avoid creating lot…

In no way am I projecting a preference for everything should be free. I specifically said I was willing to pay, but per developer makes no sense to me at all.

I build a commercial product myself that I charge for.

My point is that per-developer licensing doesn't make sense on any level... just because "that's how people have always done it" doesn't make it a good idea and that type of pricing doesn't allow me to compare the cost to the value. Instead of thinking, this product is awesome and I can use it on my 5 sites for $X.. I have to think, ok I have 20 developers and 5 of them work on site A, 7 on site B and the rest float around so how many people would need to be developing with the library, etc etc.

Right? or am I missing something here and am crazy? which is entirely possible.

Re: Polychart.js: An Interactive Charting Library

#46

Earlier quoted context omitted.

I don't understand this per-developer licensing model. Not only is it completely non-enforceable but feels really out-dated and out of touch in the era of FOSS. Hasn't commercial software been licensed effectively per-user since forever? It used to be per-machine but these days with lots of developers using a desktop and a laptop I think it makes sense to say it's for one user at a time instead and avoid creating lot…

In no way am I projecting a preference for everything should be free. I specifically said I was willing to pay, but per developer makes no sense to me at all. I build a commercial product myself that I charge for. My point is that per-developer licensing doesn't make sense on any level... just because "that's how people have always done it" doesn't make it a good idea and that type of pricing doesn't allow me to comp…

I agree there are certainly other models that would make sense, given that this is probably a library that's going to be incorporated as part of a larger project rather than a standalone piece of software for in-house use.

It seems reasonable to have a predictable price up-front, particularly one that can be transferred to a client as part of an overall project budget if necessary.

It also seems reasonable to have a more transparent level of scalability. Something like per-domain pricing might make a lot of sense as an approximation of buying it once for each project where it'll be used.

I suspect a commercial project like this is mostly going to be used by larger organisations who aren't going to sneeze at real money, because there are too many good-enough alternatives for the little guys. That being the case, if you want to allow for increasing value as a project grows, you could do something like per-(public-facing)-server instead of per-developer and just make as many in-house machines as you want free.

That might be awkward with cloud-based projects that activate and deactivate instances on the fly, so maybe just band it "$x for up to n public servers/instances at once", "$y for up to m public servers/instances at once", "for more servers/instances contact us for special rates".

Licensing is always a mess, unfortunately. I think the best you can ever do is probably to present something that is clear in what is covered, realistic in what it costs, and reasonably consistent/predictable.

Re: Polychart.js: An Interactive Charting Library

#47
post #25
post #3

$300 for a single developer, and the EULA says I can't transfer this license to another person?

We'll be reviewing the licensing option per feedback from HN. Please send a note to team@polychart.com, would love to hear more about what you think would be reasonable :)

Interesting question. So if I use this to display site metrics for me and my team, is that a commercial use? I'm not selling that service but in that example I would be using it to provide a visual indication of how the site is doing which helps me do my job.

Generally pricing isn't particularly challenging, people exchange money for perceived value so identify the value that you add and charge for that.

So places where you might be adding value;

developer training - A common source of value and one which a lot of non-community FOSS members appreciate. So folks who aren't part of the community or know much about anything find it valuable to have someone who will answer their stupid questions in a timely fashion without insulting them. That could certainly be charged on a per-developer level and annually.

data-hoisting - (see what I did there? clever huh?) basically there is value in getting your data from X hosted on Y. So lets say I periodically scrape all of the stock prices for the DJIA and want to provide an interactive chart for that. A data hoisting service would provide a repository for post-processed and chart friendly data. You can price that with visualization support almost on a contract basis.

custom visualizations - there will be people of course who want to visualize something in a way which is unique, consulting services for them can be quite valuable.

ad-sponsored charts - something between hoisting and foisting but there are charts that people "check" very often (like the 5 day weather forecast, or the traffic delays on various freeways). You can certainly create pages which display visualizations of these and also are "sponsored" by an advertiser. The trades of bit coins for example, rent prices by zip codes, basically changing data sets of interest to both a number of people and to people who would like to advertise to people interested in that data.

Re: Polychart.js: An Interactive Charting Library

#49
This is pretty cool, but $300 is a lot to pay, even for commercial use. There are a lot of free client-side charting projects out there. Charts.js was a recent one on HN: http://www.chartjs.org/

While this new one does offer interaction between charts, that wouldn't be too hard to add into other existing free projects that have event systems to hook into.

I'd say $50 - $99 would make it more worthwhile.

Re: Polychart.js: An Interactive Charting Library

#50
post #25

Earlier quoted context omitted.

We'll be reviewing the licensing option per feedback from HN. Please send a note to team@polychart.com, would love to hear more about what you think would be reasonable :)

In a world of so many wonderful free open source graphing libraries, it's hard to see any reasonable licensing option for this. It might help if there was a page that listed features that a developer could not accomplish for $300 in flot, highcharts, or ndv3, or other popular options.

Highcharts isn't free either, at least for commercial use.
Post reply on HN