3 ms·
> but the author should clearly state what they are doing is not meant to replace production quality solutions. If you know you need a load balancer you should
by JustSomeNobody 7y ago
> but the author should clearly state what they are doing is not meant to replace production quality solutions.
If you know you need a load balancer you should already know this.
- AdieuToLogic 7y ago> > but the author should clearly state what they are doing is not meant to replace production quality solutions. > If you know you need a load balancer you should already know this. If you know you need a load balancer, you go and look for one. If you happen upon one in a programming language you use, then it may be more appealing. Hence the need for an explicit disclaimer.
- cortesoft 7y agoBut if you don't do any research to find out if it is production ready, you aren't a production ready dev anyway. A disclaimer isn't going to save them.
- AdieuToLogic 7y ago> But if you don't do any research to find out if it is production ready, you aren't a production ready dev anyway. Seriously? Is victim blaming somehow more acceptable than just clearly stating that a project is not meant for production? And why is the suggestion of including a simple disclaimer so repugnant? What is so wrong with saying "this is an educational project and should not be used in production systems"?
- cglace 7y agoYes, if you will use anything that doesn’t say “NEVER USE THIS IN PRODUCTION. SERIOUSLY THIS IS FOR EDUCATIONAL PURPOSES ONLY” then you are going to get burned by a lot more than a LB.
- AdieuToLogic 7y agoThis thread, and most importantly your comment, only serve to reify the Go programming language community's toxicity.