3 ms·
Why the wording wasn't great, it is a valid concern. If you already have a server running Postgres, then maintaining a separate MySQL install really is a pain,
by adestefan 14y ago
Why the wording wasn't great, it is a valid concern. If you already have a server running Postgres, then maintaining a separate MySQL install really is a pain, especially when it comes to being up to date on security.
- jimktrains2 14y agoWhich is fine. It's the idea that software can "pollute" is absurd. Give reasons and arguments, not slander. Already having a python/postgres stack is a valid reason to want a piece of software that runs on it. Just saying php/mysql "pollute" is a terrible mindset. It's like saying "I won't pollute my mind with German" instead of "I have no use for German in my everyday life". One is very trollish, the other is a valid point.
- reeses 14y agoI think "pollute" conveys the idea much better than the German example. Yes, it can create an emotional conflict, as you've demonstrated. However, I would say that adding PHP and MySQL to a public server just increased the attack surface as well as operations management overhead. In my eyes, that is an increase in risk/cost/etc. for that server. That justifies "pollute", "infect", "degrade", etc.