edge
reitit
edge | reitit | |
---|---|---|
1 | 14 | |
502 | 1,378 | |
0.0% | 0.4% | |
2.6 | 8.7 | |
over 2 years ago | 7 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.
reitit
- A History of Clojure (2020) [pdf]
- Elixir for Cynical Curmudgeons
- Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
-
Help finding a webdev framework that works out of the box
I would build the CLJS for your game logic. Then I would build the backend server separately with API endpoints your front end to talk to. https://github.com/metosin/reitit is a pretty good option.
-
The hard way or the easy way?
A significant feature of reitit is that routes are composed of simple vectors and maps. That means you can pre-process that data structure however you want before building the router.
- how to get body of request on reitit
- Clojure needs a Rails, but not for the reason you think
-
Web dev stack in Clojure
You might look at the examples on the Reitit page. Reitit seems to be the emerging library for routing, and it does get you most of the way there, no matter which direction you are looking to go..
- Was sind zwei schöne Momente, die ihr heute schon hattet?
-
Malli 0.6.0 is out - performance, instrumentation and dev-tooling
for runtime validation & coercion, you can use the pedestal-utilities from reitit which support all of spec, schema and malli. For dev-time var instrumentation (static & dynamic), there are several ways to add those to existing or 3rd party codebases.
What are some alternatives?
yada - A powerful Clojure web library, full HTTP, full async - see https://juxt.pro/yada/index.html
malli - High-performance data-driven data specification library for Clojure/Script.
luminus-template - a template project for the Luminus framework
swagger-ui - Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.
paos - Clojure SOAP client
ring-oauth2 - OAuth 2.0 client middleware for Ring
bidi - Bidirectional URI routing
re-frame - A ClojureScript framework for building user interfaces, leveraging React
ripley - Server rendered UIs over WebSockets
component - Managed lifecycle of stateful objects in Clojure
lein-figwheel - Figwheel builds your ClojureScript code and hot loads it into the browser as you are coding!
hiccup - Fast library for rendering HTML in Clojure