3 ms·
This seems in general misguided... > There is, however, a scenario where leaving a side project to die is not okay: when you make money from it. Whether you se
by diggan 11y ago
This seems in general misguided...
> There is, however, a scenario where leaving a side project to die is not okay: when you make money from it. Whether you sell it as a service or a product, the moment you accept any form of obligatory payment for your side project, there is a fundamental obligation you have to maintain it.
I do not agree with this. Just because you make money of something doesn't make you have a obligation to maintain it. Who are you to decide this? If my side project happens to be good enough that I can charge for it and some people pay, doesn't mean I want to maintain it for the rest of my life. Once I'm bored of it or feel I want time for other side projects, I'll stop maintaining it. Because I can't maintain everything.
Seems like the authors problem is that he assumed that side projects are solid projects that will be there forever and he payed for that assumption. Rather, research what you are paying for, before you make the payment. And if there is a real interest for the people behind it to maintain it, and they communicate that they will be around, THEN it's a bad thing to just drop it.
- kazinator 11y ago> Seems like the authors problem ... is that if he sold a bicycle on Craiglist, it would be "immoral" to just offer it as-is and never see it again. The fifty dollar deal would include free chain lubrication, brake pad changes and flat tire fixes for 18 months. Nutjob.
- Swizec 11y agoTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
- s73v3r 11y agoI believe the opposite. If you're making money off of it, then you do have a moral obligation to support it, at least to the point where they can use it under the original circumstances they were sold it under. The idea that one could charge for a product and completely disappear with the customer's money is extremely unprofessional, and quite frankly makes it much harder for the rest of us to sell software.
- diggan 11y agoSure, as I said in the comment before, agreeing to stick around and charge for a service then running away is clearly a dick move. Charging for something monthly and then one month decide you want to do other things, is not a dick move. If you pay me to clean your apartment for two months but the third month I decide to do something else instead, do I have to keep cleaning your apartment?
- markdown 11y ago> Charging for something monthly and then one month decide you want to do other things, is not a dick move. It most certainly is a dick move if you know you have customers who depend on the service. To avoid being a dick, provide your users more notice. > If you pay me to clean your apartment for two months but the third month I decide to do something else instead, do I have to keep cleaning your apartment? Of course you don't, but to avoid being a dick, provide adequate notice, with adequete being enough time to find a replacement. If I had a party on the 2nd day of month 3 with an expectation you'd be cleaning the apartment on day 1 only to be told on the 1st that you wouldn't be doing it, that would be a dick move. ------ Essentially it comes down to providing enough notice to find a replacement. The time needed to do that obviously depends on the service, but I can think of many cases where a months notice is less than acceptable.
- diggan 11y agoThe service is a side project. It's something half baked (maybe not always half baked, but often) you did because you thought it was fun to do. If someone is depending on my side project, I'm not gonna take responsibility for you making a bad decision to depend on a service that people make as a side project. Of course, if we're talking "real" projects/services, it's different. But now we're talking about side projects. Something you do on the side. I'm not against letting your users know that you're shutting down with a good amount of time before. What I'm against is that someone saying (the linked blogpost for example) that I HAVE TO maintain my side project because someone decided to depend on it.