This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-17
Channels
- # adventofcode (2)
- # beginners (153)
- # cider (14)
- # clara (9)
- # cljs-dev (8)
- # cljsjs (1)
- # cljsrn (4)
- # clojure (124)
- # clojure-dev (9)
- # clojure-france (18)
- # clojure-greece (22)
- # clojure-italy (11)
- # clojure-nlp (5)
- # clojure-russia (9)
- # clojure-spec (21)
- # clojure-uk (40)
- # clojurescript (82)
- # core-async (12)
- # cursive (3)
- # data-science (2)
- # datomic (225)
- # devcards (8)
- # docs (2)
- # duct (1)
- # emacs (18)
- # figwheel (2)
- # fulcro (117)
- # graphql (13)
- # hoplon (10)
- # jobs (7)
- # jobs-discuss (7)
- # keechma (8)
- # leiningen (4)
- # off-topic (16)
- # om (2)
- # om-next (3)
- # perun (11)
- # precept (4)
- # re-frame (24)
- # reagent (2)
- # remote-jobs (8)
- # ring (2)
- # ring-swagger (9)
- # rum (42)
- # shadow-cljs (8)
- # spacemacs (3)
- # specter (7)
- # uncomplicate (10)
- # unrepl (58)
- # yada (9)
Oh for a confirm();
JS dialog...
I'm used to writing let with each var on a separate line however, is
(let [a 2, b 3]
(+ a b))
perfectly idiomatic clojure code, using ,
instead of \n
to separarate let clauses ?That’s fine (although uncommon)
http://www.civilbeat.org/2018/01/hawaii-distributed-phony-image-of-missile-warning-screen/
Frankly, I expect most government software is like this. Different incentives, no accountability.
i dont just mean the software, but also the retweeting fake pictures of the software 😛
I expect nothing less than fake, too. It's practically in their job description 😛
This is the kind of scenario where it should be made public who the contractor was, in a "you'll never work in this town again" kind of way, lest this kind of thing ruin the reputation of all developers.
"Whatever the real interface looks like, it requires the employee to click through a second warning prompt before sending out the alert, according to state emergency officials."
So apparently they did have a confirm();
dialog