scoop-clojure
malli
scoop-clojure | malli | |
---|---|---|
3 | 33 | |
113 | 1,419 | |
- | 0.8% | |
8.7 | 9.3 | |
8 days ago | 3 days ago | |
PowerShell | Clojure | |
MIT License | Eclipse Public License 2.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.
scoop-clojure
-
Any resources for "current best practices and learnings?"
Also while java based programs are advertised as "run anywhere", developing clojure on Windows still seems like the dark arts. I was only able to get things up and running with this super useful repo utilizing the spoon installer, and even with that there are gotchas like certain things have to be double quoted on Windows: https://github.com/littleli/scoop-clojure
-
Getting Started
Getting started and TL;DR version under the Getting started VERY QUICKLY section.
-
How to go about learning web dev with clojure/clojurescript?
Are you using Windows or Mac/Linux? Installing Clojure on Windows is a bit tricky. You can either use the WSL Windows Subsystem for Linux 2 WSL2, or install right on Windows. The only way I got things working on windows was using the instructions to install it using a tool called Scoop: https://github.com/littleli/scoop-clojure
malli
- A History of Clojure (2020) [pdf]
-
Critique of Lazy Sequences in Clojure
Clojure's lazy sequences by default are wonderful ergonomically, but it provides many ways to use strict evaluation if you want to. They aren't really a hassle either. I've been doing Clojure for the last few years and have a few grievances, but overall it's the most coherent, well thought out language I've used and I can't recommend it enough.
There is the issue of startup time with the JVM, but you can also do AOT compilation now so that really isn't a problem. Here are some other cool projects to look at if you're interested:
Malli: https://github.com/metosin/malli
Babashka: https://github.com/babashka/babashka
Clerk: https://github.com/nextjournal/clerk
-
[ANN] Malli 0.11.0 is out - a data-driven data specification library for Clojure/Script
BREAKING: walking a :schema passes children instead of [id] to the walker function #884
-
Generic functions, a newbie question
When you get to larger, more complex validations, I'd recommend checking out Malli or Spec.
-
Any resources for "current best practices and learnings?"
for specs, you can try malli - feels pretty well supported and full featured: https://github.com/metosin/malli (i'm not 100% sure how popular it is for others, but I use it on my personal projects)
- Single-file scripts that download their dependencies
-
Clojure Turns 15 round table video
Have you tried malli: Data-driven Schemas for Clojure/Script?
-
Clojure from a Schemer's perspective
All that being said, I particularly use malli and I don't find anything to complain about. There is a very nice and sound ecosystem being built around it (malli-ts is one of my contributions to it, but still in early development stages). I highly recommend reading its README, very informative stuff.
-
Clojure 15th Anniversary: A Retrospective
Any large codebase can be broken up into small isolated components that can be reasoned about independently. This is how you structure Clojure projects if you want them to be maintainable. Clojure inherently encourages doing this by defaulting to immutability. The contract between components is the data being passed to the component and returned by it. Using Malli schemas at the edges of the components is a typical approach to documenting their APIs https://github.com/metosin/malli
I see the fact that people often end up creating large and tightly coupled monolithic codebases in static languages as a negative aspect of static typing. Such codebases are difficult to reason about even if you have guarantees that the types align. Ultimately, you need to understand the relationships in code, and how they relate to business logic. The more coupling an application has the harder it becomes to reason about it as a whole.
Ideally, I think applications should be structured as a bunch of Lego blocks that can be composed together. Each component should encapsulate some functionality, and then the flow of the business logic should bubble up to the top and expressed in how these components are chained together.
-
Worrying comment from HN on Building a Startup on Clojure
Uhhh spec has existed for a long time and before that, schema Nowadays we also have the excellent malli. If his codebase is full of functions where the shape of the data isn’t obvious, isn’t documented and isn’t specified in a specific/schema, that’s on him and his bad coding practices and really no different from passing data in other dynamic languages. A class by itself (without additional effort) only gives you field names.
What are some alternatives?
bb-web - Scripting React-ive web apps in Clojure without installing it.
clojure - The Clojure programming language
tools.deps.alpha - A functional API for transitive dependency graph expansion and the creation of classpaths
schema - Clojure(Script) library for declarative data description and validation
clj-msi
babashka - Native, fast starting Clojure interpreter for scripting
clip - Light structure and support for dependency injection
reitit - A fast data-driven routing library for Clojure/Script
system - a dependency injection library for Clojure and ClojureScript 🍩 [Moved to: https://github.com/donut-party/system]
honeysql - Turn Clojure data structures into SQL
Shovel-Ash258 - Personal Shovel bucket with a wide variety of applications of all kinds.
fulcro - A library for development of single-page full-stack web applications in clj/cljs