3 ms·
While this topic is fun, it smells like complete BS to me. Why? Because the problem of people choosing the wrong tool (not the tool "shepherding" the person in
by jt2190 7y ago
While this topic is fun, it smells like complete BS to me.
Why? Because the problem of people choosing the wrong tool (not the tool "shepherding" the person into using it) is older than programming [1].
We can do better than to (once again) make up an elaborate way of blaming our tools.
[1] https://en.wikipedia.org/wiki/Law_of_the_instrument https://en.wikipedia.org/wiki/Law_of_the_instrument
- Chris2048 7y agoWhat is the right tool in each of these cases? If you have a PERL codebase, do you take XML with a totally different language?
- leejo 7y ago2004-2008 I worked at The Press Association - we were processing gigabytes of XML a day, many of it in real time feeds pushed out to the likes of the BBC, large newspaper publishers, and betting shops. All of this was done with Perl. None of it was done with regular expressions - it was done through XML::LibXML, and thus libxml. Whenever I hear other perl devs complain about XML processing my answer is always the same - just use XML::LibXML. Choosing a different language might gain some advantages, but if you still choose the wrong libraries you're still going to have pain.
- Chris2048 7y agoBut if "choose the right tool" includes "use the right libraries", how does it differ from "write good code"? At that point arguing that you should use the right tool is arguing about being disciplined?