For someone new To Clojure and ClojureScript it can seem like a bit of a "gotcha" to know when you need to use the apply function and when you don't. Hopefully in this post I'll clear up any confusion about how to apply apply! Let's lay the foundation for this discussion by looking first at some simple examples.
Once again I'm saved by friends in the Clojurians slack channel! This time it was viebel who answered my question in the klipse room. I really love the simplicity and ease of app.klipse.tech because it gives you an instant Clojurescript scratchpad at your fingertips. My only issue was that I didn't know how to add other ClojureScript libraries. Viebel opened my eyes to the fact that it's actually incredicibly easy to add other Clojurescript libraries, and here's how you do it!
Today is Thanksgiving, and as we close out 2017 currently especially thankful for all of these great programming languages and tools that have been created and shared. It is really incredible that anyone with (admin) access to a computer can get started with any programming language literally right now. It's just a google away. ;) Anyway, since you've come to this post I'll assume you're interested in using ClojureScript, and I won't have to bore you with how amazingly awesome and mind-expanding learning ClojureScript is because of how data-focused and simple your code becomes without the overhead of modern OOP imperative syntax. So, hold onto your keyboards because in this post I'll show you that it's not hard at all to get started with ClojureScript!
I've been using the twit NodeJs library that calls through to the twitter api, and I was having trouble searching for a combination of multiple keywords in a tweet. Luckily, I found this great page that they call basic search operations:
If you know me well then you probably know how in love I am with serverless backends, cloud functions, lambdas, and whatever other fancy names they can give for basically a pay-only-for-what-you-use server. I'm also pretty fond of the Serverless Framework (https://github.com/serverless/serverless) which let's you easily scaffold out a new project meant to be run on a serverless architecture. Although I've only been using it for AWS Lambda, I recently made a little mistake that turned out to be a great discovery, and in this post I'll tell you all about it!
The posts on this site are written and maintained by Jim Lynch. About Jim...