jozzy-james

well, the way i understand it is that the NFT signature would prevent that. granted, i've only recently been looking at NFT and general blockchain custody stuff at work - so i might be missing some key parts on how it all works.

edit: unless you meant the forgery was the first to NFT - which is why i mentioned that i only see it as viable for newly created works that have not already been sold.

sure, i guess the thought is if you break the NFT chain then you essentially devalue your investment. it's an interesting use-case, but don't see it widely adopted in the art market any time soon.

I work in the industry dealing with art/design, and the only thing I really see NFT being useful for is a chain of custody to prove authenticity - but that only applies to newly created works, as with historic pieces you're already at a crapshoot on specialists validating stuff correctly.

edit: i use the term 'historic' loosely, i just mean stuff that has been circulating for a while.

nobody does

I worked at a UPS hub before Amazon was much of a thing, and I can say that what you're describing is nothing new or specific to Amazon. Logistics companies, especially in the warehouse/sorting areas, are abjectly horrid to work for.

edit: and that was a union gig.

forced, no - but in some areas it is the only viable place to work for many (speaking of warehouse)

text-red-500 isn't the same as color=red, and you can override which shade of red that is (or make it green/brown/whatever...tho that would be silly). but you can also define brand-centric names for stuff and they apply to anywhere you'd be able to use a color (text, border, shadow, etc). there's also the notion of having a design system, rather than a prescriptive framework...tailwind comes with some sensible defaults on these things, but it's built in a way that you can override it all to suite your org's look and feel.

with that said, it's an internal tool - who give a hoot?

i mean, tailwind kinda does a very simple version of that...`/` is not a valid class character, but it's parsed correctly on compile.

sure, if you have "a" heading component - but what about when you have 30 heading components?

i'm trying to find it in the docs - but how do you apply a different border on mobile, tablet and desktop via tachyons?

not exact, but from one of my buttons

flex bg-black text-white px-8 py-4 font-bold cursor-pointer items-center justify-center

edit: more characters needed, but IMO makes more sense as to what it's doing.

there is nothing stopping you from using @apply in custom classes if you really want to - or using data attributes for targeting, depending on your use case.

it's different in specificity for one. you can also extend the config and create a color called `branding-primary` for example, then use that for anything you need to apply a color to. can do similar with css custom properties or sass/less variables

even just using the element classes option in dev tools makes for rapid prototyping

purgecss and customizing the config will reduce any file size concerns you have (plus gzip, etc) - from an execution perspective, since you're only using a fixed set of class names, the parsing is quite fast.

great documentation, good 'outreach' presence around the interwebs from the team, sensible class naming (tachyons can get a little...eh, imo), the build possibilities are quite nice (tho may be as flexible in tachyons...haven't used it in quite some time), responsive everything (mostly), the laravel bump as mentioned - all in all an evolution of previous attempts that resonates better i guess.

have yet to try it out myself actually, but it's on the short list once i get some time at work :)

not related to the article at all, but figure I'd share this thing that was recently released (no affiliation, just a fan of marcel's work) : https://usewindy.com/

that's more on your leasing company sadly...they get bundle discounts for referrals, but you still get screwed

i blame the half-assed infrastructure. finally got a solid fiber line, so i'm good now - but prior it was nothing but hell. every tech out would just say, welp - i don't know why they sold you this, we don't support it...even tho they buried the dang lines. and fwiw i'm in the middle of a decently sized metropolitan area...not out in the sticks

and i totally get where you're coming from - i'm the point guy on validating any new integrations for what we do. i was just commenting on the cost/benefit of having someone fix a home rolled version vs their managed and if it'd save money

i guess i really don't understand what separates a startup from enterprise...i know my particular company is nowhere near enterprise level...at least as far as i know of it, but i also know we're not a startup.

edit: in this sense...i know the fundamental differences otherwise

edit #2: we're also not a SaaS, but a B2C

not sure why the downvotes, i said most people - not most HN readers

maybe it's the managers that are autistic

weeps in '1 minute remaining' apple update progress

not OP, nor do we use airflow (not sure there is a fit for us) - but $300-500 for something that could cost our modest company an equivalent half day of human time to mitigate, with possible tens of thousands in lost revenue if it occurs at the worst possible time, seem like a win-win peace of mind proposition.

i grind php daily, and am aware of them

i will provide one bit of anecdotal reasoning tho, within my company - the exchange server will _not_ work on anything other than paid for linux clients, but works flawless on apple's standard mail app. sure, they could set up the server a different way, but...why?

depends on what you do, for most people - chromeOS would be plenty fine for 'getting stuff done'

don't own ams/zzounds (ams split off after a separate acquire iirc)