edge
shadow-cljs
edge | shadow-cljs | |
---|---|---|
1 | 20 | |
502 | 2,207 | |
0.0% | - | |
2.6 | 9.1 | |
over 2 years ago | 4 days ago | |
Clojure | Clojure | |
MIT License | Eclipse Public License 1.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
edge
-
Clojure needs a Rails, but not for the reason you think
I totally respect that, and Clojure could invest more in offering frameworks or even no-code platforms or such features, but the truth is it doesn't. The language very much targets the software/information engineer category in my opinion, where by that I mean, the people who are interested in not just the functional requirements, but also the non-functional requirements of performance, scale, architectural runway, future extensibility, operations, maintainability, correctness, re-usability, etc. Especially, Clojure targets those who believe a balance between all these and functional requirements is the holy grail. That's why it won't be the most correct, the most performant, the most productive, but a pragmatic balance of all these in almost equal parts.
Maybe it should also embrace the people looking to get a product out by simply using a framework, and I'd say there's more of that in Clojure today than ever before, but the community I think is more composed of the former people that I describe, which is why you don't see any attempted framework take hold in the community, because most current members are not in the group that "just want to build the product using an established framework".
I think the community has settled, ounce again, on a bit of a balanced approach, Kit (https://github.com/kit-clj/kit) and Edge (https://github.com/juxt/edge) are such hybrids. And some more direct viable frameworks have come along like Biff (https://biffweb.com/) and Fulcro (https://fulcro.fulcrologic.com/).
That said, since the community is more composed of people like me, you don't see a mass move of every Clojurian switching to one of those.
So it creates some questions?
1. Is it a problem that the language targets engineers more interested in a balance between non-functional and functional?
2. Should it be mutually exclusive, or can Clojure equally serve both niche? And if so, should it, why?
3. Is the claim that you can be as productive and it is just as easy to build a product without using a framework in Clojure true? Does this apply to everyone, or only certain personalities or people with certain amount of lower level knowledge?
4. Is Clojure's marketing misleading? Are people looking to just "build the product using an established framework" mislead in thinking Clojure will offer them salvation?
5. Where do most developer fall in, if they don't fall in the category Clojure currently targets, than does that mean Clojure cannot become mainstream? To go mainstream does it mean you have to target frameworks because there are more developers looking to just make a product using a framework?
I don't have answers to these, I'm just trying to define the current state and what the problem with it might be, or if it even is a problem.
shadow-cljs
-
A History of Clojure (2020) [pdf]
* Single-Page App: shadow-cljs for the build concerns (https://github.com/thheller/shadow-cljs), Reagent with Re-frame for complex/large app (https://reagent-project.github.io and https://github.com/day8/re-frame). Even if we now prefer using HTMX (https://htmx.org) and server-side rendering (Hiccup way of manipulating HTML is just amazing, https://github.com/weavejester/hiccup).
-
Supercharge Your JS/TS Project with ClojureScript REPL
Now, add shadow-cljs.
-
[ANN] Malli 0.11.0 is out - a data-driven data specification library for Clojure/Script
Work with latest shadow-cljs (& closure compiler) #890
-
Cherry: ClojureScript to ES6 Module Compiler
You can already develop with ClojureScript on the back-end. A popular ClojureScript compiler, Shadow-CLJS (https://github.com/thheller/shadow-cljs) has a target for Node among many others.
-
Why metabase and circle are not using cljs (mostly)?
Hi, I'm looking at Clojurescript again after not having paid attention to it after several years. Are you saying that shadow-cljs does something to deal with the, "I have no idea if this library I want to use works with the Google Closure compiler," problem? If so, what? I'd really like to know.
- Clojure needs a Rails, but not for the reason you think
- shadow.css - CSS-in-CLJS
-
Rich Hickey β open-source is Not About You
I don't know, the community in general tend to use macros that are well written. I keep seeing core.async being used (`go`) in Clojure projects, and also various macros for writing HTTP servers (compojure being a popular one which main code interface is a macro `defroutes`).
ClojureScript projects also routinely add support for making asynchronous code look synchronous (like `async/await` in vanilla JavaScript) via macros. shadow-cljs's `js-await` being one of the well-written ones: https://github.com/thheller/shadow-cljs/blob/49fb078b834e64f...
Usage:
(defn my-async-fn [foo]
- Finalmente, depois de dois aninhos no ventre, minha empresa nasceu πΆπ
-
ClojureDocs β Community-powered documentation and examples for Clojure
Unclear what "rendering a webpage" entails exactly.
If you want to do frontend development, you can give shadow-cljs a try, the quickstart is pretty quick: https://github.com/thheller/shadow-cljs#quick-start
If you want to just render server-side HTML, something like compojure (HTTP routing) and hiccup (Clojure data -> HTML) is pretty easy and quick to get started with (https://gist.github.com/zehnpaard/2071c3f55ed319aa8528d54d90...).
If you want to generate HTML files to serve with nginx/whatever, you can just use hiccup and `(spit)` the resulting HTML to files on disk.
What are some alternatives?
yada - A powerful Clojure web library, full HTTP, full async - see https://juxt.pro/yada/index.html
helix - A simple, easy to use library for React development in ClojureScript.
luminus-template - a template project for the Luminus framework
reagent - A minimalistic ClojureScript interface to React.js
paos - Clojure SOAP client
biff - A Clojure web framework for solo developers.
bidi - Bidirectional URI routing
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
ripley - Server rendered UIs over WebSockets
re-frame - A ClojureScript framework for building user interfaces, leveraging React
lein-figwheel - Figwheel builds your ClojureScript code and hot loads it into the browser as you are coding!
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.