slack-ruby-client VS kit

Ah, I'm surprised Slack doesn't support Ruby, but to be fair they are pretty tight on official support with only Python, Node and Java.

Fortunately there's https://github.com/slack-ruby/slack-ruby-client, but it's not official. Although it seems to be a good example of a community driven library coming together. I haven't used it personally (I never interfaced with Slack in a Ruby app) but at a glance it looks like it has really good docs, a decent amount of contributors, well maintained, etc.. If I were building some Rails app that used Slack I'd likely reach for this and not feel bad about it.

Kind of a bummer on the other 2 tho. Thankfully I wouldn't be building too many apps using those tools, but I get the point you're saying. In the grand scheme of things I think this also shows at how much more popular Python is than Ruby.

Slack's Ruby client works well and is well organized: https://github.com/slack-ruby/slack-ruby-client

Clojure using for the server side https://github.com/kit-clj/kit

htmx for frontend, using the built-in kit htmx module.

I am not sure what a web framework is, to be honest. The choices for many parts of a web application are really domain-specific and I'm not sure a single "framework" would work for everyone.

As far as web-related components go, my app uses Rum (as an interface to React), ring, http-kit, pushy (for history manipulation), sente (for websockets), buddy (for authentication tools).

If you are looking for a batteries-included "I want to have some sort of webapp right away" thing, I think https://kit-clj.github.io would fit the bill, but the general feeling in the Clojure community is that unlike Python with Django or Ruby with Rails, the choice of app components is not predetermined by the language.

Luminus has, in theory, been superseded by Kit: https://kit-clj.github.io/ but even so it is still "an opinionated bundle of libraries" rather than a framework.

I learned by using https://luminusweb.com/docs/clojurescript.html to get me started. It gives you a plethora of sane starting points, and you can just work on switching it to your own business logic. Troubleshooting and adding functionality will usually lead you to understand how things work. The authors of luminus have moved on to build kit: https://kit-clj.github.io/ which is probably another good starting point.

The cljs stack I hear about a lot (and use) is ShadowCLJS with reagent (https://reagent-project.github.io/) and re-frame (https://day8.github.io/re-frame/). ShadowCLJS is more of a build tool, but is really well documented and easy to use. Reagent is basically react but a simpler API, and re-frame is a layer on top of that provides data subscriptions and event-handlers to manage app state. It's overkill for some apps but I find it's actually super easy to work with and not as much complexity as I thought.

For backend there is luminus (https://luminusweb.com/) or Kit (https://kit-clj.github.io/). They are basically project templates that wire together a ton of popular solutions for various things - database access, migrations, security, html templating, etc. Also includes frontend frameworks like re-frame if you want.

The component itself is just a thin wrapper for conman, you can see it here.

Here’s me: https://luciano.laratel.li/

I was happy I could get the domain! Pretty simple hand-rolled server-rendered site using the kit-clj[0] and neat-css[1]. Main backbone of the site is here[2]. I used to use a CLJS SPA but it was overkill and not as nice to use (load times particularly.)

[0]: https://kit-clj.github.io/