Well, that's great and all but be careful not to be to flippant about it.
Well, that's great and all but be careful not to be to flippant about it. It's a very different business model, with different advantages and disadvantages that are very hard to compare directly. It's not an easy decision to make. My current project was Closed Source for a year and a half and has now been Open Source for a year. Open Source was always something I thought about, and sometimes people asked, but the thing that made me flip over was the realisation one morning after some bad sales meetings that with either a Open Source or Closed Source project, making a project that users both actually want and you can get some money for was very hard work, and if I was going to do all that work anyway I may as well do the one I personally preferred. So I Open Sourced it, and I feel I did so from a position of strength. It's been a great year for the project, and I don't regret it. I've also been on the flip side of that; Open Sourcing a project from a position of weakness. We had talked about Open Sourcing it from the start but never did, then the project never took off and in the final stages before we finally killed it we Open Sourced it. It never gave us or anyone else that I know off any benefit, and was a waste of time. Thanks nirvdrum for a honest and good post - I'm actually talking about Open Sourcing my project in a week and would like to quote your blog - with a link and credit, of course. Good luck for the future ...
Posted by jarofgreen on Nov 22, 2014, 10:16 AM
Tags
Related issues
- C++ is the "just here to deliver" language.
- He is not weirdly political, he has just more normal views, I know that is something hard to grasp for some tech bro.
- Of course you don't have a right to murder anyone.
- Unify Control and Container nodes, allow children to pick the behavior
- I was talking about this the other day with someone - broadly I agree with this, they're absolutely fantastic for getting a prototype so ...
- In theory you could express most things as a flowchart but the complexity of doing that quickly escalates.
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
ux (EdTech)
C++ is the "just here to deliver" language.
He is not weirdly political, he has just more normal views, I know that is something hard to grasp for some tech bro.
Of course you don't have a right to murder anyone.
Unify Control and Container nodes, allow children to pick the behavior
I was talking about this the other day with someone - broadly I agree with this, they're absolutely fantastic for getting a prototype so ...
In theory you could express most things as a flowchart but the complexity of doing that quickly escalates.
It's not really hard to onboard new engineers with Scala, Clojure or even Ruby backgrounds.
Very understanding (or even no) partners is probably a large percentage of it!
Well, that's great and all but be careful not to be to flippant about it.
Well, that's great and all but be careful not to be to flippant about it. It's a very different business model, with different advantages and disadvantages that are very hard to compare directly. It's not an easy decision to make. My current project was Closed Source for a year and a half and has now been Open Source for a year. Open Source was always something I thought about, and sometimes people asked, but the thing that made me flip over was the realisation one morning after some bad sales meetings that with either a Open Source or Closed Source project, making a project that users both actually want and you can get some money for was very hard work, and if I was going to do all that work anyway I may as well do the one I personally preferred. So I Open Sourced it, and I feel I did so from a position of strength. It's been a great year for the project, and I don't regret it. I've also been on the flip side of that; Open Sourcing a project from a position of weakness. We had talked about Open Sourcing it from the start but never did, then the project never took off and in the final stages before we finally killed it we Open Sourced it. It never gave us or anyone else that I know off any benefit, and was a waste of time. Thanks nirvdrum for a honest and good post - I'm actually talking about Open Sourcing my project in a week and would like to quote your blog - with a link and credit, of course. Good luck for the future ...
Comments (0)
No comments yet. Start the discussion.