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.

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

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

Also, 100% open source

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

- Awesome

This product may die, however I believe competition and the fire to get what you want is more valuable than king making through bad reviews (whether intentional or unintentional). Tbh, Im not going to look at the product because Im more interested in terminal editors at the moment. But criticism should be used to enhamce a product, not degrade the blood sweat and tears that went into it

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.

Not the best feedback but not sure it's downvote-worthy

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

What does that mean?

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.

Facebook, as well as most of the code out there, is still using CommonJS, since there are very real issues with ES6 modules that are still unresolved[1]

[1] https://twitter.com/sebmck/status/692443162804092928

It seems like you are jumping to conclusions.

:+1: for writing it in RubyMotion

Agreed. Picked it up recently, and it's awesome.

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

You basically just said "No, you" and then posted some links to logical fallacies. Care to address my argument more directly? The key problem here is that while this bug that may have a workaround (and that workaround is questionable to even work in all cases), it's that the bug does not manifest itself in a development environment, and occurs when you write code naturally. So, you are likely to introduce the bug, but you don't get to know you have crash issues all over your app until you ship it to a lot of users. This, combined with the App Store review delay process, results in a situation where this platform is not tenable for professional software developers to use.

edit: Laurent (RubyMotion lead) has chimed in and raised the priority of this issue, this is great news

Buying the book now, can't wait.