But I mean, if they’re gonna be component specific CSS, why even bother over just using tailwind?
About me on lionir.ca
But I mean, if they’re gonna be component specific CSS, why even bother over just using tailwind?
I mean, for me, the greatest pro I’ve heard for the usage of Tailwind is that it makes collaboration much easier. For example, a PR to add styling to a component is easy to read - you just see the new classes added. Not only that but you know that it only affects that element and that no CSS is still being kept in your CSS files that is no longer being used.
The cascade is seen by some as one of the most annoying parts of CSS at times because it can make debugging harder - and many will simply abuse !important
as a result.
For OTP, most people would recommend using TOTP. I don’t think there’s a solution for receipts.
I’m not sure AI would work for detecting spam using email contents so surely it would use other metrics… and if it does, it’s just become another email filter. I don’t think that solution would help much.
I think ultimately email failed as a federated service because in general people do not care about email. They just want to use it to login to services, get one time codes, receipts and maybe if they’re fancy - a newsletter.
Cool to see you here (seen your name before)!
Cool project!
Lemur is already the name of a Lemmy app that died :/
I don’t know why someone would want their bank account to be only accessible on an apple device… That said, the savings on it seemed good.