I truly can’t tell what this is. I also had never heard of Deno before so that context didn’t help.
At first glance it seemed to be a next gen way to build interactive UIs in the Slack app, compared to the callback nature we built our app with.
But digging a bit deeper, it seems to be more narrowly focused on their “workflows” feature, which is one of the few things in their platform we haven’t used.
I’d love to learn more, but also if anyone from Slack is reading: your platform is pretty complex and announcements like this don’t help folks like me.
https://www.infoq.com/news/2021/02/deno-compiles-native-bina...
Ok. So they want me to be able to write commands that go between slack and my app, and I assume get results back in to slack.
Do I want this?
I don’t have to open a terminal window if I’m already in slack, and I assume the real thing here is I can get complex actions right? IDK, maybe it’s another thing I just don’t get.
I'm not very enthusiastic about writing any more integrations or apps.
Slack on Chrome supports notifications, thus slack supports Fedora.
I'm sorry but that's not what CLI are supposed to be, they should be self-contained with the least amount of dependencies possible and the smallest possible, otherwise it completely defeats the purpose