And I can’t really do a fallback in the case of @scope, a reverse @supports wouldn’t help me. Unsupporting browsers must not see the @scope block (guarded behind @supports). I think they would try to do something with it, not simply ignore it.
And I can’t really do a fallback in the case of @scope, a reverse @supports wouldn’t help me. Unsupporting browsers must not see the @scope block (guarded behind @supports). I think they would try to do something with it, not simply ignore it.
I’m not sure, but it doesn’t matter either way because even if that was the case by skipping progressively enhancing @supports browsers that would otherwise support @scope would skip it.
🫂🫂🫂
@scope is a very exciting CSS feature, and to provide a fallback for it (or to progress to using it) you'd need to use @supports, but the browser support for at-rules is worse than for @scope itself so that's fun 🤪
Quick DM/call?
Don't worry, I loved the joke, I'm sure everyone will get it.
Riiiight?! Oh my god.
Hope is incredibly painful when I have this big part of me that will be a deal breaker to almost everyone.
At this point I almost hate having feelings for people because I know I’ll have to walk them all the way back.
I know it’s not personal, it’s about poly… but it’s also not NOT about me.
Being polyamorous in a conservative country SUCKS.
The only poly partners I had were members of my own poly meetup.
The odds of meeting anyone here who is also poly (and isn’t just passing by) are very low — I’m most likely to meet someone who “doesn’t care”.
…until I meet another partner 🙄
I believe that every deliberate difficulty needs to give something in return.
It can be a horror movie, a disillusioning essay, an aggressive refactor…
The difficulty can be a powerful medium, but what does it give back? If the difficulty itself is the point, then it may not work.
Thanks, I'll try something like that, hopefully in the Vite space. Or find a project that I use that separates good first issues.
My OSS game is virtually non-existent, I wish I could pinpoint to what happened.
Overworked? Spending lots of time in job environments that don’t value OSS? Me semingly being one of the very few who interact with the source code of software we’re using?
Maybe there’s a way to swing back. Small PR.
Netflix search is one of the rare places with AI integration where that actually makes sense to me.
Most of the places I visit are "hey! we use AI all over the fucking place ✨", and I'm like "good for you, can I do my thing now?"
That's huge, I will finally able to migrate away from Library Mode ❤️
With git checkout you can accidentally lose unstaged changes by tapping into wrong muscle memory, by typing "." instead of the branch name.
Also, git switch and git restore are more deliberate, each of them have their own set of options related to what they're doing.
YES! What about Vite-specific “?inline” imports, I guess that won’t work, but I could write a plugin…?
So many people like to stick with git checkout, but it’s so scary because it does too much…
It’s good that you’re raising awareness about this.
Zed has Vim mode built in, good luck prying it open from my cold dead hands!
FaceTime doesn't work well with AirPods because input sources tend to get shuffled, and the only way to pick the intended one is inside a menu item dropdown.
This makes FaceTime, an app that has existed since forever, fundamentally flawed.
Do one thing and do it poorly.
Oh, I had no idea! Fortunately you can’t fire me 😌😌
What's wrong with that, if there's no Courier New it will fall back to any monospace font, and if there's no any monospaced font it will fall back to Consolas, which will fall back to…
Yeah…
Use responsibly, only use when creating new tests, drastically changing existing ones etc., when you're expecting a lot of failures and you need a fast feedback loop.
Otherwise these impatient tests might confuse you because you'll think something's not working when it was just an early timeout.
Default Vitest timeouts can really slow you down, sooo:
"scripts": {
"test:rapid": "cross-env RAPID=true vitest"
}
Test config:
testTimeout: process.env.RAPID ? 0 : undefined,
browser: {
enabled: true,
provider: playwright({
actionTimeout: process.env.RAPID ? 1_000 : undefined,
}),
}
Very cute! What do they eat, really worms or is that for something else?
Hearing about Cloudflare quickly reminds me of Brittany Pietsch's layoff video.
youtu.be/u7G7OpgKROw?...
Recording that and posting it was so brave, and had such a powerful impact for me that I keep thinking about it two years later.
I'm not aware of any redeeming public response.
PostCSS powers 0.5% of ALL web pages but only earned $300/month for 13 years. This story is not unique.
Your app likely has 550+ OSS dependencies. Most are one burned-out maintainer away from disaster.
This is the Nebraska problem. And here is the fix:
evilmartians.com/chronicles/s...
As to your Q, my only popular releases were small and accidental, so I never experienced what you’re feeling.
But that’s also when I was less scared to publish something right away, now I have this sad mindset “go big or go home”.
But what you described sounds different, maybe fear of success?
My web component library sucks, I want something to make it work, I’d like to try what you have cooking.
Btw, Elena is the name of my favorite person in the world, I sent her your landing page and she wanted to figure out what your library is about 😄😄
I'm fine where it is now, I just don't like using them. I wouldn't want more of them.
Why do tech bro CEOs always talk either like someone just woke them up or like they're trying to hide that they're high?
I've never heard a tech bro CEO sound like they've spoken in public before.