pizzeriafrida

I wouldn't say those doses are micro. 25mg of psilocybin is equivalent to almost 3 grams of mushrooms.

I feel the same way, but also understand what folks are saying in the replies to this, but I'm more coming at it from an API standpoint preferring something like https://github.com/workframers/wonka (albeit in Clojurescript). But there I get to use inline styles with 'special' values that could mean something in my theme like `padding: my.theme/container-padding`, and it's also just data so I can merge them etc.

This seems preferential over a single string with various syntax. I could be wrong in that my linked approach is not the same.

Translating a dose in mg to the equivalent amount of dried mushrooms you would likely come across recreationally is quite difficult, but I believe 25mg equates to something like 4-5g of dried mushrooms which would be a full on trip beyond surfaces flowing like water :sweat-smile:

There was a great interview between Peter Attia and David Nutt on the research and effectiveness of psychedelics on various disorders https://peterattiamd.com/davidnutt/

He touches on the history of governments banning various drugs through junk science and propaganda (mostly from the US which influences the rest of the world). The scheduling system for drugs is a joke.

Also interesting that the inventor of AA credited LSD for his ability to quit drinking.

Edit: David Nutt authored this study in the NEJM https://www.nejm.org/doi/full/10.1056/nejmoa2032994 which pitted psilocybin against lexapro for the treatment of depression and it showed the same effectiveness (more nuanced than that but you'll have to read or listen). Peter talked about how he is very familiar with Lexapro and it's side effects (libido, a blunting effect on life) in his patients and remarked that what was most exciting about that study is that it showed it could be as effective as Lexapro with less side effects.

This is where I'm at with it. "Develop apps like you do now, with a centralized app db, but now the app db (in the browser, most likely a giant Map) is an actual database with a sophisticated query language, an upgrade!"

It does seem a bit convoluted after going through it a couple of times, but I'm down to try it if my reagent React interop still works, e.g. `[:> MyJsComponent {...}]`.

I would say that I am very happy with the FE stack of reagent / reframe at the core. I have long chased the dragon of co-located queries ala GraphQL instead of basic re-frame subscriptions, or redux.connect and pulling fields off a map. Obviously having the ability to be more expressive with data queries is great, but in reality I have come to settle on basic subscriptions into maps, syncing data into my db via events. It's not super pretty but it scales!

This seems like it's trying to push the needle, and I will it.

I had a great time pairing with a few individuals from my past, and I'd describe the sessions as playing a coop game with friends. It was fun to team up and figure out a problem and build something; the shared joy of overcoming some hurdle.

Similarly had good experiences 'mob' programming, 7 of us in a conference room focused on building out some new thing. But again, it felt more like hanging out with friends and playing a coop game together.

> use of Hooks, which are well-known not to be the best solution to the problem of state management within React.

I swear the introduction of Hooks threw such a monkey wrench into the ecosystem. They're just powerful enough to seem like an okay thing to use 100% of the time...

I thought we all agreed that React's ultimate destination was obscurity while it quietly became the runtime target and developers just had to return dom structures as data from functions. But they got greedy, and didn't want to go down like that, and now we have a worse version of redux instead of building on top of react-redux.

Perhaps my perception is wrong, in which case apologies and I'm happy to learn and listen.

core.async is great, but admittedly I haven't needed to reach for it on the client (when building SPAs). I'm not sure if it's because re-frame is the focus for event driven workflows or what, but...

Since this thread/Clojurescript is getting some love I'd like to express something to a hopefully receptive audience:

There was a point where Clojurescript and Javascript sort of walked hand-in-hand during the advent of when React started to make sense in the minds of the community[0].

It felt really exciting because of the cross pollination that was happening between the two languages, Redux felt very familiar, and we have re-frame for clojurescript.

There was a ton of promise with Apollo.js and an improvement on the `connect` functionality by upgrading to a proper query language for getting state into a component versus wrapping functions around multiple `state.some.path` `state.some.other.path`.

David Nolen built om.next around that very idea, it was basically Apollo.js lite, and it was very exciting scientifically but never quite caught on because maybe it was a little clunky. But using datomic pull query syntax to fetch state for use in a component was thrilling. (if you got this far and decided you hate me and your eyes are rolling so hard I get it lol)

And this was all years ago now. All that excitement and progress and effort seems to have been trapped inside of Typescript, and React hooks, and did everyone forget?

0: https://swannodette.github.io/2013/12/17/the-future-of-javas...

I just saw the original developer is now focusing on a fork of ocaml's bucklescript so I'm not sure how much more work it's going to have.

Yea it's funny how much is in there, between it and the Clojure standard library you basically don't need to go searching for third party libraries.

I needed a debounce the other which was just importing

`[goog.functions :refer [debounce]]`

Absolutely, shadow-cljs is all you need, it's not coupled to the Clojure ecosystem, it uses NPM. I'm actually working on a project that uses clojurscript on the backend which is just a `:node` build target in Shadow.

The question is funny because on the the list of advantages that Clojurescript offers the syntax / language is quite low on the list imo.

Clojurescript has the best client-side build tool I have used in https://shadow-cljs.github.io/docs/UsersGuide.html and everyone uses it.

Clojurescript targets/outputs Google Closure compatible code which is easily the most sophisticated JS compiler out there. The reason no one uses it is because writing compatible code by hand is a nightmare.

Clojurescript's front end libraries are incredible, they are basically a better expression of Redux because the Clojure language has constructs that enable a more expressive API https://day8.github.io/re-frame/re-frame/

Clojurescript's JS interop is actually insane, boosted by the quality of Shadow-cljs. You can write 1:1 javascript in clojurescript if you need to. A trite example would be npm installing lodash and writing some code that uses it, I have done this and it just works.

Clojurescript's developer experience with the browser repl is next level. I know a lot of the stuff I'm saying sounds hyperbolic, but I've written a ton of Javascript and react and I really like it still, but using a browser repl to manipulate application state in my editor and reload functions without a full refresh is great.

And I guess lastly, yea the language is awesome. It's basically my perfect version of Javascript. No need to fumble with libraries like immutable.js, no need for additional libraries like ramda or lodash because the standard clojurescript library has everything+.