GantMan

I have to say this article check-mates in 4. All the things that matter upfront. I appreciate the deep dive, too.

I also did one for desks. That's linked inside the article.

Also, 100% open source

JS: https://github.com/infinitered/nsfwjs MODEL: https://github.com/gantman/nsfw_model

More information about this can be found in my the accompanying blog.

https://shift.infinite.red/avoid-nightmares-nsfw-js-ab7b1769...

- Awesome

Facebook releases so fast. So when something is brand new and it's already not using the latest, I feel afraid.

The example project doesn't use the import syntax, it's using require, and feels like it's coming from ECMA5 in a brand new video. I just worry, can they keep up? Facebook releases breaking changes often so it's a valid concern.

I applaud effort. I just feel there's some glaring gaps that make alarms go off. I'm sharing those. I know this looks fantastic, but that's when I start checking for a venire. And when I do, those smells popped up.

Things I have to say:

* Background noise in your video is annoying.

* Why are you showing your face? I'd rather see your code bigger.

* Using require instead of module imports shows me that this product is going to have trouble keeping pace with FB, Babel, ECMA speeds.

* I'm not in love with adding another IDE

* hello http://getqwikly.com/ all over again

Sorry, but I'm not betting on this horse.

:+1: for writing it in RubyMotion

have you ever seen Cube 2, hypercube? They must have tried to go 4D

lrz promises fix by next version

https://groups.google.com/d/msg/rubymotion/x6-9c__IHH0/J7jYd...

I think "irrelevant" is a poor choice of words here.

It is VERY relevant that there is a workaround. Additionally, it's kind of unfair to point at 1 bug (that has a workaround) and judge an entire system on it.

https://yourlogicalfallacyis.com/composition-division https://yourlogicalfallacyis.com/no-true-scotsman https://yourlogicalfallacyis.com/the-texas-sharpshooter

Buying the book now, can't wait.

That's the attraction to phonegap, but what happens when your "nail" changes? Your client might ask for a small feature that the API doesn't support, which renders your entire solution useless, or cumbersome.

One of the points in the article is that the second you want something phonegap doesn't provide, you're stuck back-peddling, or over-engineering your fix. We've already come across such a situation with one of our upcoming projects that requires camera overlays.

Ultimately, it's important to compare options, whether they be frameworks, native, or toolchains. They're all avenues that need to stand their ground against other avenues.

jballac, excellent point. If you post this as a comment on the page, we'll approve it ASAP, so that viewers from all origins will see it.

buy a better monitor jj. Good point, we'll add an unstick on our todo list.