(webdev Tory) @worldsendless@qoto.org

I always mentally wonder about #TypeScript vs #ClojureScript, knowing that #Clojure's decision to avoid #types is very deliberate. But TypeScript is conquering the world; is that an ad populum sign that Types are really a better way to go? Or does ClojureScript offer other things instead? If so, what are they, and to do the benefits of each option find value in different situations?

https://swizec.com/blog/the-efficacy-of-typescript/?ck_subscriber_id=363186933&utm_source=convertkit&utm_medium=email&utm_campaign=The+efficacy+of+TypeScript%20-%2012297166

The language #Clojure and #ClojureScript languages are so stable, with breaking changes being frowned upon in the culture. But breaking in the (frankly, awesome!) tooling has been my difficulty as I maintain a dozen projects of varying ages. It is a real problem. #cider #nrepl #figwheel #piggyback

Wait... do you seriously mean to tell me that I've spent hours debugging #clojure the fact that `#js` is NOT recursive? So #javascript #clojurescript `#js {"authorizationParams" #js {"redirect_uri" (-> js/window .-location .-origin)}}` is NOT #js {"authorizationParams"v {"redirect_uri" (-> js/window .-location .-origin)}}`? I probably read this somewhere, but UGH!

And yes, I know that even fixed this equality wouldn't work because JS always breaks #CLJS equality... but the point is clear.

I made a #static site using #ShadowCLJS #ClojureScript . The last step was to remove the #CLJS. But I still use Shadow to start up a local server and explore my static site in-browser. It works nicely as a quick server. #clojure

The data coming through the pipeline on one view was missing a crucial piece. It was sweet to be able to add it to the back-end function that is gathering the data, evaluate the form, and boom! It was there for my front-end view as soon as I used my usual endpoint. #Clojure #ClojureScript #FullStack #repl

#ClojureScript #ShadowCLJS One of my projects for the past year has been converting an old PDF multimedia app into a static web site. Since #Clojure is better than raw HTML or CSS, I crafted it there before grabbing the output static stuff. It is 99% JS-free, except for optional media lightboxes, and is built to last as long as HTML does, and to run as simply as possible. #ClojureScript #ShadowCLJS

Hmm. I have a lot of respect for theller's work, but isn't shadowcss https://github.com/thheller/shadow-css just reinventing the wheel? I love using gardencss for #clojure #clojurescript #CSS gen, and it works great cljc. https://github.com/noprompt/garden

Last night I was too tired to clarify, but here is the project #ClojureScript #transcription #portuguese

Benefits to using your full programming language for your #css: I wrote code that determines whether my domain is subdomain or subpath and rewrites my resource paths accordingly, shared with both resource calls (like <img>) and css url functions (like `background: url(SOMEPATH)`). #gardencss #reitit #clojurescript

Great answers here
---
RT @fndriven
I still don't understand how to properly use JS promises in #Clojurescript. 🤷
https://twitter.com/fndriven/status/1539582431744909312

Honestly this is a big one of the reasons I choose #ClojureScript/#Clojure: maximum capability while maintaining a culture of low-turbulence, high stability, low junk
---
RT @iamaponte
Any Frontend developer who's been in tech for the last decade is like...
https://twitter.com/iamaponte/status/1534857190921490432

But syntax doesn't have to be hard. Enter #Clojure #ClojureScript, part of the "syntaxless" tradition where you can learn syntax and then it gets out of the way, even allowing you to compile down to those others (and many more)
---
RT @iambickky
JavaScript is Hard!
Python is Hard!
CSS is Hard!
Whole Programming is Hard !!
Yes, everything will be hard at first, but it will become easy once you start learning it and put your time and effor…
https://twitter.com/iambickky/status/1534783758658043904