4 ms·
> especially on those of us that don't want to break the $ barrier to learn or get into things. This could be solved with "developer licenses" whereas you can
by johnnyfaehell 9y ago
> especially on those of us that don't want to break the $ barrier to learn or get into things.
This could be solved with "developer licenses" whereas you can use it for free if you aren't using it for commercial reasons. I use such licenses on hobby projects in non-tech areas. But once I start using and making money, I also get some support. I want this on all dev tools. I suspect the quality of our tools and libraries would increase massive.
- kodablah 9y agoTo your original comment, they just won't get used while restrictionless alternatives exist. I for one don't want this on all dev tools, because I don't want to provide support on the things I give out for free (which may make it one of those "restrictionless alternatives" I mentioned). Rather, I go the complete other direction and make caveats like non-support and potential stagnation clear. I treat things differently though if it is code core to my business, but the ancillary code itself is not my business.