4 ms·
For individual play, exploration, and edification certainly do it, but sharing such software is careless. Consider keeping it to yourself, otherwise label it cl
by diimdeep 3y ago
For individual play, exploration, and edification certainly do it, but sharing such software is careless. Consider keeping it to yourself, otherwise label it clearly for what it is: an experiment, a joke, or a personal challenge. Otherwise it clutter the ecosystem, divert newcomers from battle tested tools, poses security threats, deludes perception of quality by sending message that thoroughness and quality control aren't essential, diverts community to spent time on "useless" projects instead of addressing real-world challenges.
- lasagna_coder 3y ago> clutter the ecosystem what ecosystem? > diverts community to spent time on "useless" projects what community? > addressing real-world challenges. what challenges? i'm curious to know what the criteria or thresholds are for releasing vs not releasing.
- deleted 3y ago[deleted]
- diimdeep 3y agoecosystem of packages, libraries, gems, crates or what the fuck people calling this things these days. community of programmers within different technology stacks. challenges to make software simpler, smaller and faster, to maintain software and prevent modern bloat from eating up gigahz of cycles on many cores.
- NoGravitas 3y agoHonestly, all those things sound cool and good. Anything that reduces the value of software to capital is great in my book.
- HeyLaughingBoy 3y agoOr there's my take: release early, release often, release everything.