zlacker

[return to "Rama on Clojure's terms, and the magic of continuation-passing style"]
1. kamma4+QJ[view] [source] 2024-10-14 11:24:05
>>nathan+(OP)
I don’t want to be a party pooper, but from my very cursory look at the page, I don’t think this will go much farther than a very small community. I feel like you’re adding a lot of complexity compared to normal backhand/frontend/websetvices Scenario that everybody already understand.
◧◩
2. diggan+CN[view] [source] 2024-10-14 12:02:59
>>kamma4+QJ
With that mindset, should we just stop trying to improve anything regarding backend/frontend/webservices since "everybody already understand it"?
◧◩◪
3. kimi+1R[view] [source] 2024-10-14 12:32:24
>>diggan+CN
I second the OP - I'm not sure where the big prize is. I have a feeling that whomever wrote the article thinks there is a 10x (or 100x) improvement to be made, but I was not able to see it.

I find the syntax very clunky, and I have been programming professional Clojure for at least 10 years. It reminds me of clojure.async - wonderful idea, but if you use the wrong sigil at the wrong place, you are dead in the water. Been there, done that - thanks but no thanks.

OTOH I know who Nathan is, so I'm sure there is a gem hidden somewhere. But the article did not convince me that I should go the Rama way for my next webapp. I doubt the average JS programmer will be convinced. Maybe someone else will find the gem, polish it, and everybody will be using a derivative in 5 years.

◧◩◪◨
4. educti+KW[view] [source] 2024-10-14 13:18:54
>>kimi+1R
> It reminds me of clojure.async - wonderful idea, but if you use the wrong sigil at the wrong place, you are dead in the water.

Isn’t that how any programming works? If you call the wrong function, pass the wrong var, typo a hash key etc etc the whole thing can blow up. Not sure how it’s a knock on core.async that you have to use the right macro or function in the right place. Are there async libraries that let you typo the name of their core components? (And yes some of the macros are named like “<!”, is that naming the issue?)

◧◩◪◨⬒
5. synthc+I41[view] [source] 2024-10-14 14:17:06
>>educti+KW
The difference is in how easy it is to detect the cause of problems. Mistakes like wrong function names are mostly easy to find and fix. Mistakes when using core.async can be very hard to track down.
◧◩◪◨⬒⬓
6. educti+wu1[view] [source] 2024-10-14 16:55:01
>>synthc+I41
Not at all my experience. Do you have any examples?

OP called it "clojure.async." I question how much they've really used it.

[go to top]