3 ms·
I upvoted the post since I think it's a overall interesting technical discussion of git's downsides and some fossil upsides. But my response would be the same
by samspenc 3y ago
I upvoted the post since I think it's a overall interesting technical discussion of git's downsides and some fossil upsides.
But my response would be the same as what I argue in these React or other "popular-vs-other-frameworks" discussions that come: the alternatives may be better, faster, easier etc - BUT:
- The popular solution has the larger ecosystem, and there are more existing plugins or modules you can plug-and-play instead of having to build out your own solution for.
- If you hit any edge case or obscure issues with the popular framework, someone somewhere on the Internet has hit it and it's likely a QA on Stackoverflow / Reddit and similar (and hence ChatGPT and other LLMs as a result)
- People understand the popular solution more in depth and it's easier to learn about the architecture as well as its pros and cons.
- hotshiitake 3y agoCounterpoint - I get the same spiel from SEO marketing people trying to justify why every website in the org (including LoB web apps, intranet sites, etc.) needs to be a WordPress instance with 50 or so insecure plugins each. "But it's so popular!".
- duxup 3y ago>I upvoted the post since I think it's a overall interesting technical discussion of git's downsides and some fossil upsides. Agreed, I disagree with the other person's point of view, but I find it an interesting point / discussion.