Previous proposalDeploying and Managing CSP: the Browser-side Firewall
Next proposalBuilding for developer experience
If you are going to transpile JS, why not use ClojureScript?
Build Up/ Problems
Situations that led me to question my toolkit & introduced me to Clojure/Script
Clojure/Script Crash Course
Understanding the Clojure/Script syntax and functional/immutable model
Google Closure Compiler & Closure Library
Google’s way of writing JS and how ClojureScript depends on it
How ClojureScript allows you to plugin to the existing state of the art
REPL Driven Dev - Developing inside the Runtime
Tools that accelrate your dev workflow to light speed
spec - Ensuring Type Safety
Types make large systems predictable and Clojure’s optional spec library helps you with types and generative testing
The current state of art and things you need to bootstrap a ClojureScript project
Existing React wrappers in ClojureScript
Conclusion & QA
A general understanding of the JS ecosystem. Some experience in shipping/ maintaing a web application, API, or a mobile app.
Shivek has been building (and breaking) enterprise applications for more than a decade. His carrier began at a young age of 14 and largely consisted of unpaid work at Startups & SMEs. Over the years, he was lucky to find exceptional teachers, who helped him mature as a system architect. In this long journey, he has touched all parts of the stack, from Frontend to Backend, Data Pipelines to DevOps.
Since 2013, his focus has been on Frontend Development using React. He has built systems that are used by 0 to over 12 million users. This experience has shaped his ideas about how to grow and maintain complex applications and his preference for Clojure/Script.
When it comes to software, he’s an expert at avoiding shiny new things, and focusing on the old and boring. He firmly believes that all code is liability and the best piece of code is the one that was never written.