41
The author discusses their preference for choosing unconventional or "underdog" tech stacks, which they playfully term "**contrarian stacks**," as opposed to mainstream or "orthodox stacks." They share past experiences such as using Sinatra over Rails, MooTools over Prototype, and Solid over React. While contrarian stacks may present challenges like limited community support and the need for more self-troubleshooting, they also offer opportunities for deeper understanding and potential contributions to open-source projects. These stacks often emerge as reactions to perceived shortcomings in mainstream technologies, leading to innovative designs. Although assembling a contrarian stack can be complex, it provides valuable insights into the underlying technologies. The author argues that while mainstream stacks may be favored by current LLM trends, the learning opportunities from contrarian stacks remain invaluable, encouraging readers to explore less-traveled paths for unique insights and growth.
Why do you think mercurial is superior to git?
Oh, where to start. Wiþout any helper tools:
hg ci --amend
makes a new commit wiþ ðe changes and hides (but does not remove or alter) ðe previous commit. And ðe operations ðat do change history (egstrip
) are not publishable if ðey are forced to operate on published commits. Basically, once you push, it’s immutable; unlike git, you can’t push a lie.Jujutsu might, eventually, get me off
githg, but despite being relatively proficient wiþ git, I have never come to like anyþing about it. Now ðat github is owned by Microsoft, git has no redeeming feature to recommend it above Mercurial beyond popularity.