You are preaching to the choir. Even the most diehard tailwind adherents are fully aware that the class syntax is disgusting. The Tailwind marketing page literally used to open with “if you can suppress the urge to retch for long enough…”.
For many, the benefits outweigh the drawbacks. It is completely unproductive to beat this dead horse any further. The path forward is “post a better solution or gtfo”. I have already argued in favor of mine (scoped styles), and I welcome others to do the same.
Lol did you actually try searching for this?
Because it produces more even colors (perceptually), the problem that the Tailwind colors were previously solving (by hand). If you want to learn more just look it up, there are tons of resources on the topic.
Yes of course I know what I’m saying. I was refuting a specific point (that Tailwind is popular due to LLMs) which is obviously untrue. I don’t see how going off on a tangent about ELIZA or whatever has anything to do with my post.
This is unfortunate but my solution is to delete all of that stuff and never use the generators (shrug).
I did not remember or not know it at all. Does it work if I want to replace just a single file or do I have to copy-paste entire priv directory?
Edit: I read about that already! Just completely forgot it …
If we put one or more customized template files in priv/templates/MIX-TASK-NAME/ then the mix task will look for the file in our project first. Any files we don’t include there will fall back to the Phoenix generator.
Whatever works for you, but I disagree with that statement.
And how does the Tailwind solve that? Naming scheme is up to you, and with semantic styling you do not have names that can conflict.
And I do not find Tailwind configurable that much. With proper CSS I can make everything super configurable just by using some CSS variables without problem.
That is no problem for me, as I prefer semantic styles in single place, so whole sytem is consistently styled in one place. And I do not know what is so bad about <style>, especially with new @scope rule.
I do not get what is the problem there. I use slots and I do not care how it should be styled, because that is not my concern when I write content.
Why? I can do stuff like oklch(from red l c calc(h + 90)) to change hue by 90 degrees. That allows me to setup whole colour scheme using single variable (main colour) and it will compute all derivatives for me. No need for checking out Adobe Kuler or stuff like that. And Tailwind do not solve that problem either. It picks some colours for you, that is true, but that doesn’t change the fact, that you still need to find proper colour pairings, Tailwind doesn’t fix that. Especially it doesn’t fix the problem of a11y, as the values do not provide you a way to think about contrast in any way.
But the only reference for that scale is itself. I cannot relate it to any other value in my design. It is just floating in the void.
Font size at the root, em is font size for the element. I do not care about exact pixels (especially that CSS px is not 1 physical pixel either), but I care about relations with other components (especially text). Tailwind 1 relates to nothing except of itself for me. Especially when fonts are defined using different units.
That do not change my statement that it seems like designed for it. Still, for me it is attribute styling once again, just with cryptic names.
It never did work properly, as default component will be generated with Tailwind cruft anyway, irrelevant to the provided flags. This mean that I still need to go through whole generated codebase with broom to sweep it from unwanted dust.
And if I need to do that, it reduces the initial usability and just causes irritation.
Another big downside of Tailwind is that it requires compilation step to do tree shaking of styles. Especially when you use custom values like bg-[light-dark(var(--color-white),var(--color-gray-950))]. With “just CSS” I can just place files in repo, and I do not need any bundler or anything. It will just work. I do not need any browser tooling to analyse what does the classes names mean, I can just by hand edit there, and then just copy paste styles from browser dev tools to my project.
I get why people are using Tailwind - they are just lazy, and shushing everything into glorified style= attribute is their way of lazying around. It is simpler to just slap bunch of classes and call it a day. Semantics of my content? What the hell is that? I want to make it pretty and if someone is visually impaired, then it is their problem, not mine.
I simply learned how to live without Phoenix generators, because these always produce more noise than useful code for me. The only generator I use is for Ecto migrations (but it is Ecto generator, not Phoenix) to not need to deal with filenames.
Generators are the weakest and the most irritating part of Phoenix out there. It is just not worth the hassle.
You can just put in a single file. So if you just want to edit the index.live you only need to add:priv/templates/phx.gen.live/index.live.
The generators call Mix.Phoenix.generator_paths to get all roots, then use that to call Mix.Phoenix.copy_from which greedily copy a template if it exists at a root. By default generator_paths returns [ “.”, “phoenix”].
I agree, that is why I decided to roll my own flavor of Phoenix. Heavy use of generators to take out all the hassle of adding assocs to forms or changesets and tests. Now everything works nearly out of the box and I can just run all the generators to have a working CRUD app. Adding EctoSync and I have real-time updates propagated to all the sessions.
LOL so needlessly combative and generally false. Effin’ up a11y is not a Tailwind-specific problem, it’s a “90% of people who do web design” problem, regardless of the tech they are using. And the lazy argument is needlessly insulting. That’s certainly not how I approach Tailwind-use.
Absolutely. The only ones I use are phx.new, phx.gen.auth, and ecto.gen.migration. I don’t really see a point in using any of the others other than for prototyping. They seem like they are made more with showing different features of LV than something you would actually want.
