Why having clojurescript in the classpath may lead to unexpected behaviour

Combining Java's promises with Clojure's laziness yields some interesting behaviour

A new version of the cross-platform date-time library has been released

A look at the trade-offs to be made when developing for the web, especially with respect to date/time APIs

Using dot-access vs goog.object vs something else

Using interop syntax with the java.time API is not wrong, but there is an alternative that is superior in every respect - and it just got much better

Javascript is getting a new platform Date-Time Library, called Temporal

Small but significant releases for npm and babashka users

Mostly about npm dependencies of course!

News since Clojure North 2019

Removing some boilerplate from async Clojurescript tests

My talk from Clojure/North 2019, https://www.youtube.com/watch?v=UFuL-ZDoB2U

Choosing and troubleshooting clojure.core/with-redefs

In many domains, writing code that runs cross platform is a big win. However, there's more to this than changing file extensions to .cljc. This talk explains the why and how of cross platform Clojure and demonstrates a new date/time library 'tick' that goes a long way to enabling cross platform programs.

A brief explanation of how to leverage your business logic code as much as possible it, with some specific tips for Clojure developers about using the cross-platform [tick](https://github.com/juxt/tick) date/time library.

A new 'web log' is born