Comment by dsego
5 years ago
Well, it's easy to get confused when you look at the professional looking website with a well crafted logo, a promo list of features and a copyright notice from the "The Actix Team". The community page even says "We're a welcoming community so don't be afraid to engage.". Ouch!
Huh nothing you said indicates it is a professional project. Sleek does not equal professional.
The easy way to tell is to remember if you're paying them or not.
Absolutely not. You can get professional (but not necessarily timely) support from me for multiple projects I maintain on GitHub, for free.
For many people, their personal interest in open source is writing code for fun and showing it off. For others, it's making a product that people can rely on. The second one is my motivation; don't take that away from me.
That’s fine. It’s even admirable if you to do that. But it isn’t and shouldn’t be mandatory.
1 reply →
The distinction between "amatuer" and "professional" is literally the motivation for the action, i.e. if you are doing it for enjoyment vs if you are doing it to get paid or advance your career.
If you are making products that people can rely on primarily because you enjoy it, you are literally an amatuer.
There are figurative connotations of quality and polish implicit with those terms, but I find those connotations unfortunate and in many cases unwarranted.
1 reply →
That's not true at all. You can pay for amateur bullshit, and you can get professional software and support for free (and free as in freedom).
You can get professional software and support for free, until you can’t. This “you’ve provided me free support once, so it’s your obligation to support me for free indefinitely whenever I ask” attitude has certainly contributed to my open source exhaustion as a maintainer.
1 reply →
You only have a right to complain about the amateur bullshit you paid for, though.
1 reply →
My Ethernet is stuck in ipv6, professionally tell me how to fix it, for free.
3 replies →