Live data from Hacker News

Polychart.js: An Interactive Charting Library

polychartjs.com

31–40 of 72 posts

Re: Polychart.js: An Interactive Charting Library

#31
post #3

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

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 me to quantify the cost in terms of the value it provides to my business rather than how many developers I have.

Re: Polychart.js: An Interactive Charting Library

#32
post #28

This looks quite awesome! As a quick suggestion, the wiki ( https://github.com/polychart/polychart2/wiki ) recommends using github as the CDN which I thought was highly discouraged. However I can't find any official stance on this anymore..did it change?

Take a peek at the headers: $ curl -I https://raw.github.com/Polychart/polychart2/develop/polychart2.standalone.js You will see Content-Type: text/plain; charset=utf-8 X-Content-Type-Options: nosniff This is a deadly combination: browsers may reject script tags with incorrect MIME types if nosniff is set.

Ah, that solves that :) I've seen recommendations of using Github Pages instead, but again I can't find any official Github stance on it. I'm guessing they reserve the right to cut you off if you start using large amounts of bandwidth.

Re: Polychart.js: An Interactive Charting Library

#34

i would say not bad but the fact you are asking me to pay to use it when i can have something like d3 is a bit of a joke

why is everyone these days so afraid of investing time? d3 is well worth the time invested learning!

It's not about being afraid of investing time, but rather assigning more value to time than the licensing fees.

Re: Polychart.js: An Interactive Charting Library

#37
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 :)

On the other hand, do I get a price break if I contribute to the GitHub project? What if I am a company?

Re: Polychart.js: An Interactive Charting Library

#40
post #3

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

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 lots of silly infringements.

If you don't like anything resembling that form of licensing, perhaps you're projecting a preference for everything-should-be-free culture onto commercial development where someone has to pay the bills? Unfortunately, sometimes that just doesn't work.

Having a per-user or per-machine licence where the licence is not transferrable seems crazy to me, though. We consider such licensing conditions toxic, because all it takes is someone to leave or a hard drive to crash and you've lost your investment, so usually seeing that will end our interest immediately.

(For completeness: We will make a grudging exception for software that is essential to our business and can't be had any other legal way or replaced with any better alternative. However, you don't buy software like that with a quick web site download anyway, and if we get screwed on that kind of deal lawyers are involved. Obviously a charting library is nowhere near this level, though.)

Post reply on HN