open-props VS web_app_from_scratch

There's still some boilerplate, but I'm a big fan of Open Props[0] because it takes a hybrid approach. CSS isn't necessarily reinventing the wheel, but allowing for easier / more powerful approaches to difficult layouts or things that would otherwise require JS. Bootstrap is fine but troubleshooting advanced layout issues involves a lot of inspecting elements to see what styles are actually being applied (at least in my experience, YMMV) so I'd personally always bet on CSS.

[0] https://open-props.style/

I don't quite get the hate for having CSS in another file. Do you also put all your react stuff in one single file ? That same logic and argument can be applied against all modularization.

And really 20-50 tailwind classes in a single element is VERY hard to read and keep in mind. No - it does not make things clear or understandable. One tends to need to re-read and scan over from the beginning and eyes glaze over. Esp if some elements only vary with a few classes missing. I guess it works for people with very high attention to detail and high amount of working memory. I only find it personally frustrating.

Maybe tailwind css works for some bright people. I did try it for a couple of projects and only felt pain.

However, the "atomic css" philosophy behind tailwind is great. I find framewroks like https://open-props.style/ far better to use.

Open Props adds to the set by providing extra custom properties for things like easing functions or animations.

> If you wanted to actually solve theming, what you should work for is not a constrained helper function like light-dark(), but instead a shared token schema. Today nearly every company has their own token schema and different ways of naming things in the semantic token layer. If we had a shard language here, not only would it be trivial to add light/dark theming (just redefine a few variables that are already provided for you), code could be shared between sites and inherit the theming/branding.

Isn't that the idea behind https://open-props.style/ (and https://theme-ui.com/ in JS land)?

I think it's a great idea, but hampered by the lack of adoption incentives for the very people that need to adopt it for it to become successful (design system/component library authors). It introduces constraints, but the promised interoperability is not really beneficial to the people who need to work within those constraints.

I do think that the real value of Tailwind comes from the utility classes, rather than css-in-html paradigm. You could achieve the same, for example, with Pollen.css [0] or Open Props [1].

[0] https://github.com/heybokeh/pollen

[1] https://github.com/argyleink/open-props

If you choose to style with plain CSS you can add design tokens as CSS variables with Open Props: https://open-props.style.

Some time ago I discovered Open Props which provides a lot of design tokens as CSS variables and started using it in some of my projects.

CSS: Open Props (https://open-props.style/)

https://open-props.style/ gives you design tokens as CSS variables. It’s CSS only and not Svelte specific.

How do you mean Django is heavy? When I think about heavy, I think about how hard it would be to replace the framework with my own code in the future. So I don't like magic. Both, Django and Flask seem to have a similar amount of magic to me. But I might be wrong. I tried Flask only very briefly.

Me and other devs maintain this repo which shows how to get from a fresh Debian install to a running web app via different frameworks:

https://github.com/no-gravity/web_app_from_scratch

As you can see, it also has a Flask version.

Contributions are welcome!

Why using python3-django on debian instead of a venv and the last lts of django from pypi on your script[0] ?

[0]: https://github.com/no-gravity/web_app_from_scratch/blob/main...

I am building an open source web framework comparison.

The idea is to put together a project that gives an overview of how to set up a minimal viable web application from scratch via all the different frameworks.

For each framework the project features a self explanatory shell script that builds a web app with routing, templates and user accounts. So there is no ambiguity of how to reproduce the results. And it is even possible to just copy&paste the steps into a docker container and see the framework in action.

So if you want to compare how the frameworks do templating, you can look at the "Let's use templates" part and have a quick overview of how it is done in Django, Laravel, Flask, Symfony, NextJS...

So far, 5 developer joined and contributed.

Here is the repo:

https://github.com/no-gravity/web_app_from_scratch

I am building an open source web framework comparison.

The idea is to put together a project that gives an overview of how to set up a minimal viable web application from scratch via all the different frameworks.

For each framework the project features a self explanatory shell script. So there is no ambiguity of how to reproduce the results. And it is even possible to just copy&paste the steps into a docker container and see the framework in action.

The shell script for each repo starts from scratch and builds a web app with routing, templates and user accounts.

Here is the repo:

https://github.com/no-gravity/web_app_from_scratch

So if you want to compare how do you use a template, you can look at the "Let's use templates" part and have a quick overview of how it is done in Django, Laravel, Flask, Symfony, NextJS...

So far, I wrote the beginning of the Django script and two developers contributed Laravel and Symfony scripts. So far we have routing and templates. All three still need user accounts.

If you are experienced in a web framework, feel free to add to one of the scripts or a new one and send a pull request!