fulcro
component
fulcro | component | |
---|---|---|
8 | 13 | |
1,518 | 2,068 | |
0.0% | 0.0% | |
8.3 | 0.0 | |
3 months ago | about 2 years ago | |
Clojure | Clojure | |
MIT License | MIT License |
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.
fulcro
-
Riff: A “mycelium-clj” for the Clojure ecosystem?
I definitely believe Clojure needs a rails. Not only will it help beginners get started, if it can help people get started faster and build fast like Django and rails do, I think it'll help more with adoption.
Biff and fulcro seems like they have a shot at this
Biff- https://github.com/jacobobryant/biff
Fulcro - https://github.com/fulcrologic/fulcro
- A History of Clojure (2020) [pdf]
-
Most commonly used libraries/frameworks in Clojure
A library that is a bit leaning towards a framework is Fulcro, a fullstack library to build SPAs http://fulcro.fulcrologic.com/
-
[ANN] London Clojurians Talk: Why you need Fulcro, the web framework to build apps better, faster (by Jakub Holý)
Fulcro (https://github.com/fulcrologic/fulcro) is my web framework of choice whenever I need to create any non-trivial web application thanks to its productivity. Its overarching design goal is sustainable development speed as time goes and code grows and it really shows up. It is developer friendly, with minimal boilerplate, and features you need for any serious application. And it is surprisingly flexible. Fulcro is based on a few simple ideas that combine powerfully to produce a multitude of capabilities, including its Rapid Application Development "add-on". Some people find Fulcro complicated and scary - but it doesn't need to be. Stop choosing "simpler" web frameworks - and ending up implementing half of Fulcro with much more effort and verbosity and much less value. I will present the minimalist way of learning Fulcro with its three corner stones and explain Fulcro's building blocks. After this talk, you will understand the design and value of Fulcro, be motivated to learn it, and equipped to do so quickly.
-
Electric Clojure second batch of tutorials - multiplayer chat, backpressure, component lifecycle, todolist
I am curious how this compares to Fulcro both from a conceptual and a usage perspective. Which advantages does this offer over Fulcro?
-
Libraries that join front and back end?
Fulcro has a complete "story" for data-driven UIs and backends. https://github.com/fulcrologic/fulcro
- What are some great Clojure libraries, as of 2021?
-
Looking for an example of server-side rendering and client-side rendering with Clojure(script)
We do that via Fulcro: render the first frame in CLJ on JVM, then continue with CLJS in browser. The code is a bit dirty and probably won’t tell you much (because I can’t share the whole app), but you can definitely do that.
component
-
A History of Clojure (2020) [pdf]
* Lifecycle management: Mount, Integrant or Component (https://github.com/tolitius/mount https://github.com/weavejester/integrant and https://github.com/stuartsierra/component)
-
Generic functions, a newbie question
When you start to have multiple stateful components (the database, the HTTP server, your Redis connection, a page cache, etc.), then you'll want to use a library like component that manages their (inter-)dependencies and provides a consistent notion of lifecycle.
- What makes Clojure better than X for you?
- Clojure needs a Rails, but not for the reason you think
-
[ANN] Reveal Pro 1.3.308 — sticker windows for system libraries (component, integrant, mount)
Today I released a new version of Reveal Pro — dev.vlaaad/reveal-pro {:mvn/version "1.3.308"} — that adds sticker integration for system libraries such as mount, component and integrant!
-
Printf(“%s %s”, dependency, injection)
I agree with the main sentiment from the article. Although I do think they are discussing Inversion of control more-so than dependency injection.
One of my first languages was .net and I was never able to really understand DI in that context that well.
Actually using javascript and ducktyping made me understand what it actually was.
I remember a .net job interview where I had to write a micro-service and opted to construct the dependency graph in the main function initialising "all" the classes there. Instead of discussing the pro's and con's of that approach they berated me for not using a DI framework (No I did not land that job, but in hindsight it was the most expensive job interview I've ever had. The room was filled with 8 developers going over my code).
The main thing the article glosses over is state. something people with a functional background hide from. But if you look at something like the httpclient in .net. I think it took the .net world like 10 years to start using the httpclient properly. Scope and lifetime of those kind of objects are important. managing connection pools, retry state, throttling or the incoming http request. DI does make that kind of thing easieR (I'm not saying it makes it better)
Look at clojure's component(https://github.com/stuartsierra/component), I'm not a clojure expert by far. But it is kinda DI/IOC in a functional language.
In closing we can agree that it is underused in the right places and overused in the wrong ones.
- Forcing engineers to release by some arbitrary date results in shipping unfinished code - instead, ship when the code is ready and actually valuable
-
How to pass components across functions
https://github.com/stuartsierra/component#no-function-should-take-the-entire-system-as-an-argument
-
There are a *lot* of actor framework projects on Cargo.
Yeah like I mentioned I'm not like super sold on the everything-should-be-an-actor paradigm, but I find value in DDD + a light implementation of Components (similar to stuartsierra/component).
-
Essential libraries?
https://github.com/stuartsierra/component for managing components lifecycles in projects
What are some alternatives?
electric - Local-first sync layer for web and mobile apps. Build reactive, realtime, local-first apps directly on Postgres.
integrant - Micro-framework for data-driven architecture
electric - a reactive Clojure dialect for web development that uses a compiler to manage the frontend/backend boundary
reitit - A fast data-driven routing library for Clojure/Script
malli - High-performance data-driven data specification library for Clojure/Script.
mount - managing Clojure and ClojureScript app state since (reset)
reagent - A minimalistic ClojureScript interface to React.js
ultra - A Leiningen plugin for a superior development environment
specter - Clojure(Script)'s missing piece
awesome-clojure - A curated list of awesome Clojure libraries and resources. Inspired by awesome-... stuff
jadak - Web-server for ClojureScript/NodeJS based on Yada
Luxon - ⏱ A library for working with dates and times in JS