3 ms·
Diminishing returns? Let me do an inverse car analogy. I know how to write a complicated SQL query in SQL and in maybe a couple of different ORMs, because custo
by pmontra 4y ago
Diminishing returns? Let me do an inverse car analogy. I know how to write a complicated SQL query in SQL and in maybe a couple of different ORMs, because customers don't know SQL and want everything in (say) Ruby, Python, Elixir. Then the world inflicts us another ORM and I have to waste hours to learn all of it again only for the ORM to build my original SQL query and send it to the DB. Rolling eyes and WTF!
- tzs 4y agoThat reminds me of payment processors. They usually have SDKs for PHP, Ruby, JavaScript, and maybe others. Often these just end up doing a simple HTTPS post of name=value pairs. It is almost always easier and cleaner to use their HTTPS name=value post interface directly if they officially allow it and support it. Often you are going to get your payment information from the user in that format anyway, such as via a post from your checkout page, or as a row of named columns when you retrieve on file payment information from your database. In that case submitting name=value pairs mostly just requires translating the field names from your checkout page or column names from database to the names that the payment processor uses, plus adding a few more name=value pairs. Going through their language specific SDKs often requires building up some ridiculous object oriented mess.