This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-02
Channels
- # adventofcode (76)
- # announcements (1)
- # asami (1)
- # babashka (31)
- # beginners (302)
- # calva (3)
- # cider (1)
- # clj-kondo (1)
- # cljdoc (1)
- # cljfx (63)
- # cljsjs (2)
- # clojure (36)
- # clojure-europe (29)
- # clojure-gamedev (2)
- # clojure-nl (5)
- # clojure-sanfrancisco (2)
- # clojure-spec (2)
- # clojure-uk (71)
- # clojurescript (19)
- # conjure (21)
- # core-async (10)
- # core-matrix (1)
- # cryogen (4)
- # cursive (12)
- # datomic (22)
- # emacs (4)
- # events (1)
- # figwheel-main (7)
- # fulcro (9)
- # graalvm (1)
- # jobs (1)
- # kaocha (17)
- # lambdaisland (1)
- # meander (7)
- # mount (2)
- # nrepl (12)
- # off-topic (35)
- # re-frame (15)
- # reagent (17)
- # remote-jobs (1)
- # reveal (41)
- # shadow-cljs (13)
- # spacemacs (2)
- # tools-deps (24)
Slack CEO Stewart Butterfield:
"the opportunity we see together is massive … as software plays a more and more critical role in the performance of every organization, we share a vision of reduced complexity, increased power and flexibility, and ultimately a greater degree of alignment and organizational agility. Personally, I believe this is the most strategic combination in the history of software, and I can't wait to get going."
It seems he couldn’t quite figure out how to work the words “synergy” and “nimble” in there.zoom has often been better in that calls usually worked
Ok, this is legit funny. https://twitter.com/slack/status/1333886283689709569
Surely by now they have offered him a not-insubstantial sum for that handle
any general opinions on using Clojure foreign function capability (interoperable) with Python, as well as Clojure Script?
I am trying to think of the trade offs between directly calling foreign code… versus using a message broker like Kafka
process boundaries are a fine place to build a stronger abstraction
don't need kafka for that
shell invocation, http, all kinds of ways to handle that, some of which are slower and simpler, some are faster.. some sync vs async
in short, I think you will spend as much time trying to call a python runtime properly from JVM
as you would building a cleaner interface between processes, or subprocesses
I would never ship clojure in jvm calling python runtime BTW
you have to go thru clojure -> java -> JNI -> Python runtime ...
so many abstractions and translations, best to just output spit and slurp some JSON over a socket or stdin 8^)
OTOH https://github.com/clj-python/libpython-clj is well-supported and fairly heavily used by the data science folks -- it's grown out of that community.
That said, I would probably only bother going across that sort of boundary if I had a lot of experience in both languages and there were some critical libraries I needed to use in the non-Clojure ecosystem 😐
https://adventofcode.com/ day 2 is starting in 10 min, time to warm a REPL.
yes, I was looking at the new clojure-python lib… Sounds like I should only experiment with that… not on production… maybe just for fast AI/Data type experiments.
I have used foreign functions on Ruby/Java… and yea… sometimes there’s a hiccup… 1 little incompatible call
@timok fun / scary version: analyze interactions between managers and employees to train an AI middle manager :D
criminal version: train a model to correlate slack activity and stock price of that company
end to end encryption would be possible in a group messaging scenario, but transcript maintenance and search is in tension with those goals
Salesforce Slack will start doing the same stuff Microsoft was doing last week with the "engagement metrics"
the (global) security implications of Slack are terrifying to me without the Salesforce acquisiton
Irrational valuation of collaboration technology which is seen as table stakes for SalesForce to play
in the "converged collab" space
aka, docs, storage, wiki, internal resource mgmt, comms etc...
maybe I'm just jaded watching middling exec teams try to buy their way into a story about the next big market trend
given that collaborative tools become the source of truth about a company's workflows and internal knowledge, I don't think it's undervalued, perhaps just not exploited yet
the "rational" thing would be to make it as cheap, simple, and flexible as possible, until it's impossible to migrate out of, then the terms are changed
which sounds like something salesforce would do, to me
at the startups where I've worked, I'd estimate that losing access to data in salesforce (not to mention the salesforce specific workflows) would be more disruptive than losing 3/4 of the sales team