This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-03
Channels
- # beginners (167)
- # boot (22)
- # chestnut (3)
- # cider (9)
- # clojure (107)
- # clojure-berlin (1)
- # clojure-greece (3)
- # clojure-italy (6)
- # clojure-losangeles (6)
- # clojure-russia (8)
- # clojure-spec (71)
- # clojure-uk (42)
- # clojurescript (186)
- # community-development (1)
- # core-async (12)
- # core-typed (1)
- # css (15)
- # cursive (29)
- # data-science (11)
- # datomic (8)
- # defnpodcast (28)
- # duct (2)
- # fulcro (169)
- # graphql (6)
- # hoplon (3)
- # jobs-discuss (1)
- # kekkonen (5)
- # leiningen (11)
- # lumo (7)
- # off-topic (14)
- # om (1)
- # other-languages (14)
- # portkey (7)
- # re-frame (27)
- # reagent (14)
- # remote-jobs (1)
- # ring-swagger (5)
- # rum (15)
- # shadow-cljs (52)
- # spacemacs (59)
- # specter (78)
- # test-check (3)
- # vim (9)
- # yada (23)
https://blog.acolyer.org/2017/10/30/occupy-the-cloud-distributed-computing-for-the-99/amp/
Another interpretation more meaningful is that DevOps are kingmakers for infrastructure solutions.
VCs are kingmakers
<-- though I disagree with the statement, I can see how someone would argue that. DevOps ?
>>> Therefore, a simple function interface that captures sufficient local state, performs computation remotely, and returns the result is more than adequate.
@qqq I suppose it mean that only those who can correctly programmatically setup all the required cloud infrastructure benefit from it.
Another interpretation more meaningful is that DevOps are kingmakers for infrastructure solutions.