12 ms·

I don't think either approach is an anti-pattern - different use cases will be useful for different users. I've found combining application instances to be qui

• thesuperbigfrog 4y ago
  >> I don't think either approach is an anti-pattern - different use cases will be useful for different users. That's why I prefaced it with 'for me'. Other people can use works best for them. I know what works best for me.
  • munk-a 4y ago
    In my personal lexicon "anti-pattern" is a pretty universal term - X isn't an anti-pattern for Alice but not Bob - it's either an anti-pattern for everyone or it isn't an anti-pattern. So I think in my comment above I mostly just automatically omitted the "for me" when reading your original remark.
    • thesuperbigfrog 4y ago
      >> In my personal lexicon "anti-pattern" is a pretty universal term - X isn't an anti-pattern for Alice but not Bob - it's either an anti-pattern for everyone or it isn't an anti-pattern. I agree. svnpenn's comment characterized "Never combine" as an anti-pattern, but it is my preferred configuration. Perhaps it would have been more accurate to just say that "Never combine" is not an anti-pattern since many users prefer it for various reasons.