Hacker News new | past | comments | ask | show | jobs | submit | butt_hugger's comments login

Oh shut up fascist.


We've banned this account for breaking the site guidelines and posting unsubstantive and flamebait comments. You can't vandalize the site like this, no matter how wrong other people are or you feel they are.

If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html.


Most of the stigma just comes from people on HN. Start by fixing that.


I mean, I don't think anyone would mind that. Or advertisers for that matter.


Don't use Tailwind, it's garbage.


Personally I’m not in favor of CSS in classes, so I wouldn’t use tailwind given the choice. But tailwind does look like a perfectly fine framework if you are into that sort of thing. I don’t claim to understand people that want to write all their styles in the class attribute. But if you do, I don’t see a reason why Tailwind would be garbage. In fact it looks like a perfectly fine tool for a workflow that I personally don’t use.

Do you have a personal experience you would like to share?


Can you please elaborate?

Personal anecdotes, development experiences that made you feel that way.


I really don't like how it handles responsive design, but that could also be because I work more on apps than marketing sites. First, fixed device breakpoints doesn't seem like the way to go, I find I need more customized breakpoints that are based around the UI rather than having general phone/tablet/desktop breaks. Then because you are applying styles to each element for each breakpoint, its very hard to look at and comprehensively think about a single breakpoint's layout. I can see where this works for making minor changes here and there, but major layout changes with breaks are almost impossible to keep in your head.

Then with flex box it lacks a great deal of customizability when it comes to controlling how space is distributed across elements.

And somewhat bigger picture, I'm looking to use less tooling and preprocessing, not more. CSS has come a long way to where we can now get rid of SASS, but instead Tailwind is replacing that step with fullying buying into the whole webpacker tool chain. If you're already really into webpacker that's not a huge issue, but brining along node and webpacker just for a CSS library is a bit much.


That's a hot take


So hot it's almost 20 years old!


Care to provide any reasons?


The "subset of people" known as "good developers." Lately they haven't been creating and maintaining web apps because of things like Tailwind.


Pretty sure ‘good developer’ wasn’t the discriminating factor.


Wow, what a moron.


Doubtful since they have an option for at-rest encryption.


It's just that, an option, not the default. People tend to use the defaults.


It's really sad to see novice developers rediscover and revisit arguments from decades ago, but that's really the curse of software development, isn't it? Why does Tailwind CSS even have some kind of brand name? It's just bad CSS. It doesn't need a name.


The CSS specification says nothing about how to map styles to classes. So when you say "bad CSS", maybe you mean bad methodology? Bad for what? Bad for whom?

You probably weren't alive yet, but the CSS methodologies that originated from the CSS Zen Garden made sense in an era when XML was supposed to take over the world. But it didn't, and there's no sense hanging on to those promises.

ps. Media queries were not a thing twenty years ago.


The reason XML didn't take over the world, and we're left with this mess of garbage for a front end, is because of bad developers like you. Mistakes in the past are no reason to continue making mistakes in the future. From your example, the obvious solution would be to write better markup instead of writing worse styles.


Don't feed the troll


One great feature is that when you add images in FairEmail, it removes metadata, renames the file and other privacy-preserving data.


Unless that is optional, it's a bug, not a feature. Attachments should never be manipulated unless asked.


It prompts you every time and can be configured to have a default option.


Wild that software that was developed for guided missile destroyers has " Do not murder. ", " Love your enemies. ", " Hate no one. " etc. in their Code of Ethics.


>No one is required to follow The Rule, to know The Rule, or even to think that The Rule is a good idea. The Founder of SQLite believes that anyone who follows The Rule will live a happier and more productive life, but individuals are free to dispute or ignore that advice if they wish.

>The founder of SQLite and all current developers have pledged to follow the spirit of The Rule to the best of their ability. They view The Rule as their promise to all SQLite users of how the developers are expected to behave. This is a one-way promise, or covenant. In other words, the developers are saying: "We will treat you this way regardless of how you treat us."

Nothing wrong with having an ideal to strive for, even if you aren't always living up to it.


Consider what thin gruel an ideal would have to be if you could always live up to it!


You are being transparent. SQLite was developed _for_ war machines, with that as its foundation. The code of ethics is merely an attempt to whitewash its history. The founders are shameful for their lack of self awareness.


Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: