andrewferk's comments

andrewferk | 6 years ago | on: Credit cards have a privacy problem

Credit card issuers don't pay for the cash back, it's the merchant. The merchant's are charged a credit card transaction fee that includes a fixed/percent fee determined by the negotiated contract with their bank (the acquirer), a small fixed/percent interchange fee that goes to the credit card payment networks (Visa, MasterCard, etc.), and finally a fee to the credit card issuer that provided the credit card to the consumer.

The credit card issuer fees can be the worst because of these high reward credit cards.

I'm very aware of this when shopping at a local small business. I'll pay either in cash or with my debit card, because the credit card fees are seriously squeezing small merchants.

andrewferk | 7 years ago | on: I Miss Rails

I've been using LoopBack 3 in production for 18 months.

> added no value

It gives you an API explorer, routing, ORM, validation, error normalization, authentication, authorization via ACL, and more out-of-the-box. I'd consider this value.

> had lots of obvious vulnerabilities

I'd like to know more about this. The only thing I can think of is bypassing ACLs via fetching records and including relationships. I don't know of any framework or combination of libraries that doesn't have this vulnerability.

> LoopBack 3 was terrible - complicated

This is probably true. LoopBack 3 essentially uses a single model to represent your API and data model. This is the single responsibility principle taken to the extreme opposite. It's a complete nightmare at times. If you have an exact one-to-one mapping of your API to database, this may not be a problem.

> unless the entire team and philosophy behind it has been replaced

Loopback 4 seems to be the same team, but I believe they have learned a lesson on coupling. https://loopback.io/doc/en/lb4/Crafting-LoopBack-4.html

> Models are overloaded with multiple responsibilities, such as data representation, persistence, and mapping to REST.

They have a way to go to reach feature parity with LB3: https://github.com/strongloop/loopback-next/issues/1920.

BTW, I also miss Rails.