GitHub: http://github.com/whatacold
YouTube: https://www.youtube.com/@kenhuang-tech
Blog: https://whatacold.io
In case you don’t know it, we can use raw strings, like embedding JS code, in hiccup.
I just found out we can use `raw` to prevent strings from getting escaped.
I should’ve found this at the beginning, as it’s mentioned on the homepage, but somehow I missed it.
In case you don’t know it, we can use raw strings, like embedding JS code, in hiccup.
I just found out we can use `raw` to prevent strings from getting escaped.
I should’ve found this at the beginning, as it’s mentioned on the homepage, but somehow I missed it.
So you're more than excited to find out how #clojure thread macros can make code clean and concise, you just love it! But at some point you'll be trapped a bit as the threaded argument's positions are inconsistent using -> or ->>.
Luckily, you can use as-> (see the pic)
So you're more than excited to find out how #clojure thread macros can make code clean and concise, you just love it! But at some point you'll be trapped a bit as the threaded argument's positions are inconsistent using -> or ->>.
Luckily, you can use as-> (see the pic)
Example from github.com/functional-k...
Example from github.com/functional-k...
In #clojure, we can use comment for tests in development. However, since a comment evaluates to nil, you may run into surprising results/errors if you misuse it.
In these cases, you may tend to use ; to comment them out, but a better choice is to use the discard reader symbol #_.
In #clojure, we can use comment for tests in development. However, since a comment evaluates to nil, you may run into surprising results/errors if you misuse it.
In these cases, you may tend to use ; to comment them out, but a better choice is to use the discard reader symbol #_.
Even if we might not have the opportunity to code in #clojure at work, we can still use it for ad-hoc scripting or proofs of concept. I promise it’s a lot of fun, thanks to the interactive development approach. We can try out ideas, building stuff bottom-up or top-down.
Even if we might not have the opportunity to code in #clojure at work, we can still use it for ad-hoc scripting or proofs of concept. I promise it’s a lot of fun, thanks to the interactive development approach. We can try out ideas, building stuff bottom-up or top-down.
Having too many buffers isn't good for switching buffers in #emacs.
After finishing a project, we'd better close all its buffers. How?
1. C-x C-b opens up ibuffer
2. Click at the top to sort by that column, or hit s f
3. Mark them by m, then hit D to close them
Having too many buffers isn't good for switching buffers in #emacs.
After finishing a project, we'd better close all its buffers. How?
1. C-x C-b opens up ibuffer
2. Click at the top to sort by that column, or hit s f
3. Mark them by m, then hit D to close them
github.com/clj-python/l...
github.com/clj-python/l...
whatacold.io
whatacold.io
It turned out that there is an option in :ring, which somehow isn't mentioned in lein-ring's docs. I found out it thanks to this answer: stackoverflow.com/a/28759905
It turned out that there is an option in :ring, which somehow isn't mentioned in lein-ring's docs. I found out it thanks to this answer: stackoverflow.com/a/28759905
developer.chrome.com/docs/webstor...
developer.chrome.com/docs/webstor...