It’s the difference between residents and citizens being eligible to apply. Actually, restricting non-resident citizens from applying could violate their rights.
I have the opposite problem: I’m dependent on my job’s salary but know exactly what I want to do instead. Unfortunately the job makes my life so drained I can’t pursue my true callings.
I think SQLite columns for SQLite would be superior to SQLite’s JSON columns whose operators are a whole ‘nother query language you need to learn and seem comparatively limited.
I don’t know much about typography but was schooled to be a grammar perfectionist, and this seems great to me. It’d probably help out machine translators too.
Dentists always tell me insurance requires annual xrays in order to cover anything else, even just a cleaning. So it seems like it’s really not up to them.
When there’s feature parity, what’s the next differentiator for you? For me, performance.
Though I admit another important aspect is community adoption. If your 3rd-party dependency uses zod internally, well now you’re bundling in both, and the added network latency probably negates any performance improvement you were getting in a web app. That’s why I wish libraries would use something more generic that allows you to dependency-inject what you’re already using, like https://github.com/decs/typeschema
Anyone know of a community where you genuinely try each other’s stuff and give feedback? Sometimes lose motivation aimlessly guessing what people want without having users to give actual feedback.
Didn’t they have every opportunity to conduct a trial given they started outside the US in Prospera, an autonomous zone of Honduras?
“So to start, they’ll be selling Lumina in Prospera, a libertarian charter city in Honduras. Prospera allows the sale of any biotech product under an informed consent rule: as long as the company is open about risks and the patient signs a waiver saying they were informed, people can do what they want.”
I use the same principle as pico but from scratch with tailwind. It does too much magic and it’s far too complex and undocumented to be able to modify a piece of it you need to change. In my global stylesheet I style inputs all one way and target aria and state selectors for more specific styling. I still use inline styles for more unique cases.
They are two different techniques that can work together well. If I’d make any comparison, it’d be between pico and tailwind’s typography plugin specifically.
I had verified its points myself and I wanted to be honest and cite it instead of pasting or paraphrasing what it said without doing so and therefore plagiarizing.