3 ms·
I can somewhat sympathize, although I don't view these arguments as strong since they could mostly be fixed with minimal effort. On the other hand, it's just a
by yjftsjthsd-h 6y ago
I can somewhat sympathize, although I don't view these arguments as strong since they could mostly be fixed with minimal effort. On the other hand, it's just a personal blog, so if you don't feel like sharing then that's cool too.
* The unpublished posts would require a different workflow; you could easily keep a private repo and a public repo, and publish by pushing from private to public.
* I don't really see a problem with copycats, personally. I personally feel like theme/design is just a minor style thing on top of the content and not even something that you "take credit for". Like, if someone wants to copy everything but the content of my blog, more power to them.
* The security angle is basically adding obscurity, which is a reasonable additional layer, however thin.
- bellyfullofbac 6y agoYeah, what a weak post. My flippant TL;DR: "Because I'm too lazy to separate code and content."
- yjftsjthsd-h 6y agoI think that's a touch uncharitable; a lot of it is "because I'm not willing to put in the effort to make the code public-worthy". The security concerns, for instance, boil down to wanting the extra layer of security through obscurity. Besides... it's a personal blog. I don't really agree with the reasons, but it's their blog, so it's not like they owe anyone anything, including source code /shrug
- 3np 6y agoTBH that's a perfectly valid reason in itself.