Remember that you are comparing the time to write your purpose-built framework vs. adapting a general-purpose framework to your specific purpose.
This is a great point that I hadn't thought of. It's true, I don't think any of the options I'm currently aware of would have been drop-in replacements for what I'm putting together.
maintaining OSS is a drain of resources you could put towards solving novel problems.
It is a portfolio project, but I'm concerned about this anyway. I suppose worst case scenario is that I release and don't have time to maintain it and nobody uses it, which is more or less how many people currently use it...
You're training your brain to think and act like an software architect. It's time well-spent.
True enough. Time spent solving new problems is rarely if ever wasted.
I like your classifications - Mechanic-style work does seem up my alley interest-wise.
It is a portfolio project, but I'm concerned about this anyway. I suppose worst case scenario is that I release and don't have time to maintain it and nobody uses it, which is more or less how many people currently use it...
If it's a portfolio piece, then putting it out on your GitHub as OSS is a default place folks expect to find your portfolio pieces.
If nobody uses it or contributes then it is like 99.9999% of GitHub repos and an even larger proportion of portfolio repos.
If people do use or contribute then it is a better portfolio piece.
Wow, incredible response - thank you.
This is a great point that I hadn't thought of. It's true, I don't think any of the options I'm currently aware of would have been drop-in replacements for what I'm putting together.
It is a portfolio project, but I'm concerned about this anyway. I suppose worst case scenario is that I release and don't have time to maintain it and nobody uses it, which is more or less how many people currently use it...
True enough. Time spent solving new problems is rarely if ever wasted.
I like your classifications - Mechanic-style work does seem up my alley interest-wise.
If it's a portfolio piece, then putting it out on your GitHub as OSS is a default place folks expect to find your portfolio pieces.
If nobody uses it or contributes then it is like 99.9999% of GitHub repos and an even larger proportion of portfolio repos.
If people do use or contribute then it is a better portfolio piece.
Hah, fair enough :)
Also let me know if you do post to GitHub. I've been reading up on Rust lately and writing a PR would be nice practice.
Absolutely! Still quite underbaked for now but I will keep you posted.