That's a bad example. There are apps where you absolutely not know. It's not even a "subjective issue".
As long as you have either
a) wrapped native widgets with the same look and behavior as native (or a fully skinned app vs a fully skinned native app)
b) response times below some objective, determined by human physiology, threshold
Then it doesn't matter if it's a higher level framework doing some wrapping, you don't know it at all.
Slack is the second-worst offender. It feels less native than many websites do.
The other is Rubymine, which on Mac now includes its own embedded Java runtime. It's significantly worse, but they are neighbors on the spectrum. Slack suffers less because it's mostly just chat, which can be done even in a Terminal window (e.g., IRC) without suffering that badly. But when you try to do anything in Slack other than just chat, the non-native kludge factor quickly becomes obvious and irritating.