This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-02
Channels
- # announcements (15)
- # aws-lambda (1)
- # babashka (2)
- # beginners (25)
- # calva (2)
- # cider (6)
- # cljfx (6)
- # clojure (24)
- # clojure-boston (1)
- # clojure-dev (2)
- # clojure-europe (31)
- # clojure-uk (2)
- # clojurescript (48)
- # community-development (4)
- # conjure (1)
- # datahike (4)
- # datascript (10)
- # datomic (1)
- # deps-new (1)
- # fulcro (10)
- # juxt (1)
- # malli (7)
- # missionary (1)
- # nrepl (2)
- # off-topic (2)
- # other-languages (5)
- # polylith (4)
- # random (1)
- # react (2)
- # shadow-cljs (9)
- # tools-deps (21)
I think I love Javascript.
Try evaluating this:
!"" == !"text"
If you like that, you might also enjoy this: https://www.destroyallsoftware.com/talks/wat
It's not that I like that. But what the implications of this are.
Because it retains the type but it's still an empty string. And in Clojure empty string is truthy.
I was doing something in JS and I was wondering why it wasn't allowed to have a empty string as a route name (long story) for a handler.
And for some reason the authors check whether the string is !routeName
and then throw an error (and they also write that they don't want empty strings there).
Yes, I know about the batman thing and that JS has some quite strange quirks.
But then you also have null
and undefined
... why. If empty value is falsy, why even have any concept of null
...