Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Coast on Clojure

coast.swlkr.com

Post reply on HN
Print view View original

31–40 of 61 posts

Re: Coast on Clojure

#31

Post by swlkr »

0xferruccio wrote: post #24

Love to see Coast getting some attention again! I got my start into Clojure with it working with Sean on small web apps written in Coast. I even gave a talk about it at the Berlin Clojure conference https://youtu.be/24PRtDJGvW8 The first project we built together with it was called magehash, and it was an app to monitor websites for Magecart attacks (code injection stealing credit card data). That project ended up no…

So much fun working on that project!

Turns out it's really hard to beat the productivity of rails

Re: Coast on Clojure

#32

Post by ashes-of-sol »

giraffe_lady wrote: post #29
curuinor wrote: post #19

Earlier quoted context omitted.

I'm a year and change into my job at metabase (metabase.com) writing clojure all day every day and I am still terribly surprised that basically it is all that it's promised to be. That said, you do need to actually use the repl and be repling all the time because the startup times suck and the stack traces are gigantic all the time. That's pretty much it for complaints. You would expect things that aren't apparent in…

Oh wow yeah I forgot about the stack traces. Clojure was the second programming language I ever learned, after self-teaching ruby. lmao ruby does not prepare you for a 700-line stack trace full of java classes you've never even heard of because they're deep in the implementation. Does it still do that? I remember "better error messages" being a supposedly-coming-soon thing for the couple years I was using it. I event…

Error messages are much easier to parse now!

Re: Coast on Clojure

#33

Post by ARandomerDude »

Jonovono wrote: post #28
ARandomerDude wrote: post #21

Earlier quoted context omitted.

React and ReactNative in Clojure(Script) are amazing if you work in that area. Honestly, I'd never go back to a JS implementation. Reagent [1] provides a seamless interface for components, classes, hooks, etc. and ShadowCljs [2] is a fantastic build tool for the ecosystem. Re-frame [3] is a popular framework in this space. [1] https://reagent-project.github.io/ [2] https://github.com/thheller/shadow-cljs [3] https://…

This is exactly what I just set up! Super cool - coming from doing Redux sagas and hooks and redux and all that stuff on RN it's been really interesting. Would you recommend Shadow vs Krell? I have tried both and so far Shadow was the most seamless, but Krell seems the most lightweight. If you care to share, i'd love to learn what you are building with it.

I haven't used Krell, but Shadow has been great for me. Been on it a couple years now.

My company is in the smarthome/IOT space and we use React(Native) + Clojure and ClojureScript for all our apps, dashboards, servers, etc.

Re: Coast on Clojure

#34

Post by jtth »

phyrex wrote: post #20

I loved Coast and wrote at least one production app with it (and very quickly and pleasantly at that), but it needs to be said that swlkr is the only developer, and he seems to have mostly moved on to Janet ( https://janet-lang.org/ ). Case in point, the last real updates to Coast were 2 years ago, and - unlike other Clojure libraries - not because this project was /finished/.

biff (https://biffweb.com/) is a little more batteries-included but seems like a nice successor in this space

Re: Coast on Clojure

#35

Post by threatofrain »

phyrex wrote: post #20

I loved Coast and wrote at least one production app with it (and very quickly and pleasantly at that), but it needs to be said that swlkr is the only developer, and he seems to have mostly moved on to Janet ( https://janet-lang.org/ ). Case in point, the last real updates to Coast were 2 years ago, and - unlike other Clojure libraries - not because this project was /finished/.

I'm surprised to hear that Janet is still alive and kicking!

Re: Coast on Clojure

#36

Post by capableweb »

adamkl wrote: post #22
slowmovintarget wrote: post #16

Earlier quoted context omitted.

To quote Rich Hickey: "gem install hairball"

I like that quote, but it's the Rails idioms and conventions that make hairballs, not the fact that it includes a bunch of batteries.

Adopting any framework is quite literally adopting the framework's idioms and conventions so not sure how that is different.

Re: Coast on Clojure

#37

Post by capableweb »

ashes-of-sol wrote: post #32
giraffe_lady wrote: post #29

Earlier quoted context omitted.

Oh wow yeah I forgot about the stack traces. Clojure was the second programming language I ever learned, after self-teaching ruby. lmao ruby does not prepare you for a 700-line stack trace full of java classes you've never even heard of because they're deep in the implementation. Does it still do that? I remember "better error messages" being a supposedly-coming-soon thing for the couple years I was using it. I event…

Error messages are much easier to parse now!

(Seems your comment was dead, but I vouched for it as it's contributing to the discussion)

Yeah, with the arrival of clojure.spec, some error messages has indeed gotten easier to both read and parse (for humans and machines alike), although when you use Clojure JVM so still come across the odd huge Java stack-trace (or with ClojureScript, a pretty sizable JavaScript stack-trace).

Re: Coast on Clojure

#38

Post by LesZedCB »

jcadam wrote: post #26
cube2222 wrote: post #2

Slightly OT, but whenever I see Clojure projects I think: "I'd love to write something bigger in Clojure one day, experience it, and see if it's all it was promised to be." That said, I don't really have any good use case for it right now, whether at work, or among my side projects.

I did clojure as a hobbyist for years and have only recently taken a job where I'm working full time in Clojure on a large codebase (i.e., first time having to maintain somebody else's Clojure code). It's not a golden hammer by any means, but I'd definitely take it over Java (or Scala) any day.

any experience with rails or django to compare with?

Re: Coast on Clojure

#39

Post by exdsq »

phtrivier wrote: post #23

Unless I missed something in the doc, it seems like it's the "Fullest full stack framework" as long as you're only interested in the "handling web server request and reply with html" part of the full stack. Any reason why this should be used instead of cooking up ring / hickup / whatever ?

Someone elsewhere mentioned that this seems to be ring, hiccup, and a DB connection packaged as one. Pinch of salt needed, I’ve not used it :)

Re: Coast on Clojure

#40

Post by swlkr »

phtrivier wrote: post #23

Unless I missed something in the doc, it seems like it's the "Fullest full stack framework" as long as you're only interested in the "handling web server request and reply with html" part of the full stack. Any reason why this should be used instead of cooking up ring / hickup / whatever ?

This is mostly ring / hiccup, just a layer on top to make it easier for beginners.

I would say if you’re not new to clojure, roll your own.

Post reply on HN