Water.css
reagent
Our great sponsors
Water.css | reagent | |
---|---|---|
33 | 41 | |
8,184 | 4,716 | |
- | 0.3% | |
0.0 | 1.1 | |
3 months ago | 5 months ago | |
CSS | 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.
Water.css
-
Where Is Noether's Principle in Machine Learning?
Thank you!
In the beginning, I used kognise'z water.css [1], so most of the smart decisions (background/text color, margins, line spacing I think) probably come from there. Since then it's been some amount of little adjustments. The font is by Jean François Porchez, called Le Monde Livre Classic [2].
I draft in Obsidian [3] and build the site with a couple python scripts and KaTeX.
[1] https://watercss.kognise.dev/
[2] https://typofonderie.com/fr/fonts/le-monde-livre-classic
[3] https://obsidian.md/
-
Ask HN: Experience Starting a Blog
Thank you!
I must give credit to Kognise though, the style is simply their formidable water.css layout. It saved me a lot of time and anguish when I was about to get my blog started.
https://watercss.kognise.dev/
- CSS for readability
-
No CSS Club – because no JavaScript was not hardcore enough
https://watercss.kognise.dev/ I would argue classless css is the way to go, you just include a single css file, then write your html without touching any css anymore, all related tags in html are inherently css-ed for you. a nice trade off for me sometimes.
- Filenames and Pathnames in Shell: How to Do It Correctly
-
Classless.css – Less Classes. Less Overhead
Like the previous submitter ( https://news.ycombinator.com/item?id=30885700 April 2022 ) I found clasless.css while investigating semantic html-oriented css libraries and this one stood out to me as having a good balance. I'm not ideologically opposed to using classes, but using them for every bit of styling seems off and I'd rather see good default styles for regular semantically structured html. For example, classless.css uses the "card" class for cards which don't have a clear analog in among standard html tags: https://developer.mozilla.org/en-US/docs/Web/HTML/Element
Other libraries:
Water.css: https://watercss.kognise.dev/
MVP.css: https://andybrewer.github.io/mvp/
Missing.css: https://missing.style/
-
Ur Go-To on UI with Flask?
WaterCSS, very basic but good-looking UI in my opinion
- О заметках в markdown файлах
-
Looks great on my machine
Slap this on it and you're good: https://github.com/kognise/water.css/
-
Show HN: Neat, the Minimalist CSS Framework
- https://watercss.kognise.dev/ Small size (< 2kb)
reagent
-
Ludic: New framework for Python with seamless Htmx support
Generating `HTML` from lisps has poisoned any other approach for me, see for example https://www.neilvandyke.org/racket/html-writing/, https://reagent-project.github.io/, and https://edicl.github.io/cl-who/
-
Produce HTML from S-Expressions
Hiccup syntax for Clojure uses hash maps (curly braces) for attrs, e.g. `{:style {:background "red" :margin "1em"}`
See Reagent which uses Hiccup synta: https://reagent-project.github.io/
(defn simple-component []
-
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).
- Leaving Clojure - Feedback for those that care
-
Clojure is a product design tool
The API documentation lists the most commonly and rarely used parts before going into detail and there are many usage examples.
Reagent has a nice intro tutorial (classic todo-app): http://reagent-project.github.io and many other helpful tutorials and resources for beginners: https://cljdoc.org/d/reagent/reagent/1.2.0/doc/documentation...
However, since Reagent is still stuck with class-components for more complex behavior and relies on Hiccup, which is nice but has a performance cost compared to pure React, I am unsure about its future. Like some others in the Clojure community, I have moved to thin React wrappers like Helix and use Refx to integrate those with re-frame. It may be a bit confusing right now for beginners since there is no “golden path”.
Also, unfortunately, many smaller libraries are poorly documented and it seems like it is expected from the developer to dig into the source code to find out what’s going on.
What I found the most difficult as a beginner was how to setup a project in ClojureScript in the first place, like all the configuration in shadow-cljs, how it interacts with deps.edn, how it integrates with npm, the REPL, etc. But dev/build config has always been a weak spot for me, so it might be just that.
Overall, I still very much enjoy working with Clojure(Script), more than in any other language. Anyone who likes Lisps and functional programming should give it a try (and be sure to watch Rich Hickeys amazing talks!).
-
Ask HN: How can a BE/infra developer handle the FE side of personal projects?
have you tried cljs and reagent? it’s a different vibe.
my bootstrap: https://github.com/nathants/aws-gocljs
the project: https://reagent-project.github.io/
- What are the enduring innovations of Lisp? (2022)
-
Building a website like it's 1999... in 2022
Clojure people have been doing this for a decade or so. It’s really so much better to work with. All started with Hiccup and when React came along you got Reagent and many more developments building on the idea.
-
React.dev
> But Reagent supports functional components as well, with hooks and all.
I addressed this already: while reagent is able to emit function components, there is a performance penalty to this.[1]
> I also very much like Hiccup, and so do many of us, because code is data and data is code, and Helix has decided not to support that.
Hiccup is convenient to write, but it is a constant run-time cost and a significant storage cost given that you have to store long series of constructors to cljs.core.PersistentVector in your bundle, have the JS runtime actually construct the vector, then pass it through a Hiccup interpreter to finally produce DOM nodes and throw away the persistent vector, only to repeat this entire process again on re-render.[2]
> Helix has decided not to support that.
That is simply not true. From the Helix documentation[2],
> If you want to use libraries like sablono, hicada or even hx hiccup parser, you can easily add that by creating a custom macro.
These are all Hiccup interpreters you can readily use.
IME there is very little difference between using the $ macro in Helix and writing Hiccup. I do not really miss Hiccup when I use Helix, and you still have data as code ;)
While this is from an unrelated project, there are benchmarks[3] done against Reagent that demonstrate the sheer overhead it has. In practice it is not a big problem if you rarely trigger a re-render, but otherwise it is a non-trivial cost, and if you want to use modern React features (like Suspense), there is a lot of r/as-element mingling going on, converting cases, etc. that simply make Reagent feel more tedious to use than Helix.
Also, the newer UIx2, which largely borrows from Helix, is "3.2x faster than Reagent" according to one of the contributors.[4]
I think it'd be worthwhile to benchmark all of these libraries against each other and record the data in one place. Maybe I'll get around to doing it this weekend :)
---
[1] https://github.com/reagent-project/reagent/blob/master/doc/R...
[2] https://github.com/lilactown/helix/blob/master/docs/faq.md#w...
[3] https://github.com/roman01la/uix#benchmarks
[4] https://github.com/pitch-io/uix/pull/12
-
React is a fractal of bad design
Reagent is peak React. All the good stuff without any of the hook and readability problems the article describes.
No affiliation, happy user for years.
https://github.com/reagent-project/reagent
What are some alternatives?
classless-css - A list of classless CSS themes/frameworks with screenshots
helix - A simple, easy to use library for React development in ClojureScript.
pico - Minimal CSS Framework for semantic HTML
re-frame - A ClojureScript framework for building user interfaces, leveraging React
Rust Language Server - Repository for the Rust Language Server (aka RLS)
shadow-cljs - ClojureScript compilation made easy
hyperscript - Create HyperText with JavaScript.
fulcro-rad-demo - A demo for Fulcro RAD using either SQL or Datomic databases.
prism-themes - A wider selection of Prism themes
storybook.js-with-shadow-cljs
sakura - :cherry_blossom: a minimal css framework/theme.