Live data from Hacker News

On paying for software

seths.blog

271–279 of 279 posts

Re: On paying for software

#271

Earlier quoted context omitted.

Just noticed you're the primary author of CAMotics. I'd heard of it before, but haven't yet tried it out. I'll try to get time to do so, as I've recently started helping out a different CNC project (github.com/synthetos/g2). They kind of look like they might complement each other. Not 100% sure yet though. ;)

Yes, I'm friends with the Syntheos guys. It can work with CAMotics. You might also be interested in another project I work on, the Buildbitics Open-Source CNC controller.

Thanks. :)

Looking through the Buildbotics stuff now and some of the video's. Looks nifty!

Is the motion control done by TinyG2 or g2core? If so, would it be ok to add some appropriate links to our "Who uses g2core?" page?

https://github.com/synthetos/g2/wiki/g2core-in-use

Re: On paying for software

#272

Earlier quoted context omitted.

Yes, I'm friends with the Syntheos guys. It can work with CAMotics. You might also be interested in another project I work on, the Buildbitics Open-Source CNC controller.

Thanks. :) Looking through the Buildbotics stuff now and some of the video's. Looks nifty! Is the motion control done by TinyG2 or g2core? If so, would it be ok to add some appropriate links to our "Who uses g2core?" page? https://github.com/synthetos/g2/wiki/g2core-in-use

Ahhh, looks like something custom instead:

https://github.com/buildbotics/bbctrl-firmware

No worries at all. :)

Re: On paying for software

#273

Earlier quoted context omitted.

I'm not sure if you mean the prices themselves ($18/12) or the scheme "perpetual license + optionally updates for $x/year". Feel free to hit me up on twitter @m_herrmann.

I was thinking mostly about the $18 license. More generally though, your process on pricing in general would be cool to learn about. For instance - sources of inspiration from "the literature" (ex. Strategy and tactics of pricing), past experience, user price sensitivity testing etc. thanks - appreciate your response and its cool to see you building and selling your software!

I see. I arrived at the $18 through trial and error. It's very new though. It used to be $14, which was way too low. Following common startup advice, I raised to $28. Sales halved so there was no advantage. So now I'm trying $18.

Re: On paying for software

#274

Earlier quoted context omitted.

I was thinking mostly about the $18 license. More generally though, your process on pricing in general would be cool to learn about. For instance - sources of inspiration from "the literature" (ex. Strategy and tactics of pricing), past experience, user price sensitivity testing etc. thanks - appreciate your response and its cool to see you building and selling your software!

I see. I arrived at the $18 through trial and error. It's very new though. It used to be $14, which was way too low. Following common startup advice, I raised to $28. Sales halved so there was no advantage. So now I'm trying $18.

Right on -- thanks!

Re: On paying for software

#275

Earlier quoted context omitted.

Thanks. :) Looking through the Buildbotics stuff now and some of the video's. Looks nifty! Is the motion control done by TinyG2 or g2core? If so, would it be ok to add some appropriate links to our "Who uses g2core?" page? https://github.com/synthetos/g2/wiki/g2core-in-use

Ahhh, looks like something custom instead: https://github.com/buildbotics/bbctrl-firmware No worries at all. :)

We did start out using the TinyG firmware but have since replaced it with our own code.

Re: On paying for software

#276
post #190
post #189

Earlier quoted context omitted.

Maybe you can create a page on your software website "$softwarename key generator" or something like that. And on that page you can give away a free key for those that are going to pirate it anyway. Bonus points for having detailed statistics about the wannabe pirates.

Not sure, that might be too easy - maybe some potential buyer will use it as well?

That's indeed a possibility. But if the potential buyer is searching for cracks, I'd say the chances of him buying are very low. Maybe offer a heavy discount, or a non-commercial license.

Re: On paying for software

#277
post #143

Earlier quoted context omitted.

> Software doesn't need to be manufactured like physical goods do: the software construction step is fully automated by compilers and build systems. Source code surely is manufactured. I write it with my hands, using years of knowledge and experience, spending a lot of time on it.

>Source code surely is manufactured. I write it with my hands, using years of knowledge and experience, spending a lot of time on it. Right. We not only write it with our hands, but with our brains too, as well as with the effort we put in over years to gain the skills needed to write the software in the first place. Otherwise any newbie programmer could write any of the software in the world, including complex ones.…

Exactly. You're providing a service. The digital goods, once produced, can be replicated infinitely at extremely low costs. Nobody can create copies of you or your expertise.

In order to pay for your software development services and turn a profit, the digital goods you produce are made artificially scarce so as to enable their sale. However, that does not change the nature of those goods. Copying them is still trivial.

Re: On paying for software

#278

Earlier quoted context omitted.

> If you want your child who loves drawing to stop loving it, reward them. If you want them to stop learning, tie a reward to their learning. Is there a way to achieve the opposite? > Being able to receive sustainable income for doing what you love doing, is a different formula though. What is the difference?

To “achieve the opposite”: give up on your agenda for their relationship with drawing, or whatever interest of theirs you want to promote. Support it when requested, but give support only when requested. Think of your child as being driven by their enthusiasm and interest. They don’t control these forces and you do t either. Trying to force them kills them. Trying to direct them suffocates them. So, be there, celebra…

So, don't buy hours or drawings, but do buy pencils, paper, brushes and canvases, and show an interest, but don't say OMG what a gorgeous drawing every single time.

Re: On paying for software

#279

Earlier quoted context omitted.

To “achieve the opposite”: give up on your agenda for their relationship with drawing, or whatever interest of theirs you want to promote. Support it when requested, but give support only when requested. Think of your child as being driven by their enthusiasm and interest. They don’t control these forces and you do t either. Trying to force them kills them. Trying to direct them suffocates them. So, be there, celebra…

So, don't buy hours or drawings, but do buy pencils, paper, brushes and canvases, and show an interest, but don't say OMG what a gorgeous drawing every single time.

Exactly.

It’s their relationship, their art, their journey. Don’t try to become a main character in it. It’s OK to be a benefactor, but don’t try to amplify it or change its course.

Post reply on HN