Hacker News Reader

I'm sorry to read that. Unfortunately, it isn't an uncommon story.

> if you utilize a third-party API for the core of your app, you are at their whim.

That's the money quote, there. I avoid using third-party APIs like the plague. I have written backend aggregators and facias, to avoid having to use the API.

I Just. Will. Not. embed an opaque codeball into my app. I'm a cranky old bastard, I know, but I sleep well at night.

View on HN

"Opaque codeball" is a very large category. Are you saying you won't use any 3rd-party libraries at all?

Almost none, but “at all” is also a very large category.

Open-source libraries aren’t opaque. Third-party web APIs are. The latter should only be used if they are non-critical, easily replaceable, or contractually bound to sufficient assurances.

Amen. Doing the wrong thing is easy. Doing the right thing is hard. These are thermodynamically-mandated rules that cannot ever be circumvented by cleverness or money or hard work.

Therefore, doing the easy thing is wrong.

Usually. If you are doing the easy thing, so can your competitors. Your competition usually can't do the hard things.

Not necessarily. p=>q does not mean q=>p, after all.

It does when !p=>!q.

!p=>!q is exactly q=>p, and p=>q has nothing to do with that.

I feel like you should read the original comment again.

Reply on news.ycombinator.com