jozzy-james

or you might just be working on stuff where the abstractions don't provide a lot of benefit.

your vanilla CSS doesn't actually work the same since the second transform overrides the first one

cool, not sure how that works in PHP tho

1. Being able to run a dev build (with no PurgeCSS) and use the .cls area of dev tools to quickly throw together TW classes to get stuff sorted, then carry over to the final resting place is wonderful. Compared to manually typing each property and value on the element and then copypasta'ing from there.

2. If you need to use the same group of utility classes over and over, extract to a class - either with @apply (if you want to keep the flexibility of config updates) or vanilla.

3. I'm not sure I'm following here - if you're changing the value of a tailwind class, you should do that via the config

4. I've found the naming differences easy enough to follow - line-height vs leading makes sense if you come from a design background. I think the biggest gotcha I had early on was everything is mobile first by default - so sm:* is actually _larger_ than the default.

5. the JIT is a wonderful addition, but does come with overhead currently - so that's why it (i assume) isn't just the default way of doing things.

6. not a problem i've run across, but why would a component config supersede an app config?

to your last point, we use tailwind in conjunction with a fair amount of legacy sass to do what we need (many small nuances, spread across 4 different sites, that are otherwise the same) - I would urge against mixing tailwind and SASS if only for the build speed, PostCSS should be able to do everything you need there and it'll just make the builds a bit faster.

tho I feel like what myself and my team works on is a far cry from your standard HN web app - so my experiences are probably very different.

it isn't really _designed_ for JS based applications, but if you're not at least running vite/webpack/etc with PurgeCSS then your builds will be rather bloated and you lose out on customizing the settings - if you really just don't care, then you can run the default CDN build

without even touching the pseudo selectors, your example is roughly this with vanilla css (didn't check the exact values from the TW config, just for illustration purposes)

  input {
    margin-top: 1rem;
    width: 100%;
    padding: 2rem 3rem;
    background-color: white;
    border: 1px solid slate;
    border-radius: 25%;
    font-size: 1rem;
    box-shadow: rgba(0, 0, 0, 0) 0px 0px 0px 0px, 
                rgba(0, 0, 0, 0) 0px 0px 0px 0px,
                rgba(0, 0, 0, 0.1) 0px 10px 15px -3px,
                rgba(0, 0, 0, 0.05) 0px 4px 6px -2px

  }

now, most of that is pretty straight forward - but you're just going to end up with a whole lot of copypasta when you need to implement outline/focus/shadow/etc state on many elements. and maybe on some specific instances of them you don't want that, so then you have to create a class just to override your global defaults

> two 576MP cameras

my model must be defective :(

Indianapolis - state legislature here really hates the idea of us having functional public transit or roads that aren't crumbling

our city council tries to do some stuff occasionally - but usually just ends up with the state legislature (90+ other counties) deciding they know best for our city.

haven't noticed any performance issues on mine (edit: relative to other apps in that ecosystem) - tho is a newer model. the UHD for in-house productions is pretty darn atrocious tho (looking at you, goliath)

edit: HDR, not UHD...tho have only noticed it predominate on their originals vs purchases.

kudos for putting some stuff out there, but not really seeing a real benefit over more established libs like intercooler, htmx, alpine or petite vue. also seems like your anchor tags in the intro section of your docs aren't working correctly

ah yes, the coronavirus...the thing that made everybody not use the internet

and before you ask...100 year old house and no money

i mean, i'm on an electric stove - and i have a cloud of oil/smoke when i properly sear stuff, given i have no ventilation outside of a small window. can't imagine that's too good.

- Cooking is insanely bad for the air in your house, even with an outside-venting hood.

weeps in searing steaks with no hood at all :'(

team ansible as well, tho our 100 some odd servers probably doesn't warrant much else.

tbf, if you have a 1000 row table in html - you might have other problems.

> not layout

email would like a word.

gap only applies to the inner contents tho - so still need to (potentially) handle outer margins. still, css grid is wonderful...just waiting for sub grids so i can do away with some hacky js height calculation i still need to do.

ie 5...mac edition :shudder:

my point being i did some stuff on 'x' available, hurry now - and went. and they never had them, but the difference is that i traded a quantifiable unit (human life expectancy) vs those online that just annoyed people

apply it to physical stores, see how far it goes

to be fair, there is nothing other than safari on iOS...despite the window dressing.

honestly if 'fast' is your metric - they'd not be on windows

no, they just do it horribly - there is no reason to tank perf. it's a system built by consultants, for consultants - aka the people that don't know how to actually do it.

sure, but it's an extra layer over what is currently in place.

i see them as a chain of custody that accentuates an already broken system of 'in-depth verification' as you put it. but again, i'm only recently looking into the validity of using such a thing. more accountability should be good, overall.

don't have the answers on that one, but i would imagine it would come with a shift in how stuff is currently done.

physical art/design

how so? again, i'm pretty new into researching this for physical works - but i would assume with the provenance/etc that goes into cataloging a piece, it should be...well, at least better than what we currently have.