Only "epic" fury? Not "legendary"?
Only "epic" fury? Not "legendary"?
today, we're announcing our โฌ3,8M ($4.5M) seed financing round, led by byFounders with participation from Bain Capital Crypto, Antler, Thomas Dohmke (former CEO of GitHub), Avery Pennarun (CEO of Tailscale) among other incredible angels.
read more on what's next: blog.tangled.org/seed
How do you eat a mash with chopsticks? ๐ค
Officially stated reasons are very vague and fluid and seem to change from news conference to Trump social media post, but roughly: we want regime change, stop nuclear program, stop supporting extremist groups, especially the ones fighting Israel, oil.
Damn, Czechs are playing well ๐ฌ
I started out before React was a thing, so letting HTML and CSS do what they do best is deeply ingrained in my brain and helps me write better React code. I'm so tired of this "if you use React, you automatically write bloated JS" narrative. 90% of the work I do would be a nightmare without it.
I'll also accept "year of the bald eagle on fire"
First, us Westerners should copy the whole "year of the animal" thing, because "firehorse" sounds badass.
Second, we should call this year, and every year since COVID, the year of the trash panda, because *gestures vaguely at all the things in the West* you know...
But not in Linux
Looks like there's support for building Chromium, thank god
bsky.app/profile/yoav...
Isn't using the default OS renderer one of the pitfalls of Tauri?
Haven't had a haircut in 6 months and shit's getting out of control.
> it's about an environment that was never created
Agreed, I think this is it ๐ฏ
Maybe we get there by blurring the lines between engineers and designers/PMs.
Or maybe we get designer/PM collectives that roam OSS projects, contribute for a while, then move on. ๐ค
But I'm not convinced that that's appealing to that many designers/PMs. The OSS bug seems to mostly affect engineers
So I think realistically, the only way to get all of these folks to work together is as part of a team/collective that works in a specific app. And it would need to be a big enough project for a team, which rules out most "useful small specific tool that grew into big general tool" projects.
Even if you codify, say, a design system, and open it up to anyone, you still need engineers to implement it before it's truly reusable, and a lot of it will need customization for a given application.
This is even worse for product, where there are at best trends, and almost everything is custom.
I wonder how much of this comes down to "here's free work I did, use it however you like" never really making it into design and product land. There's a bit via blog posts and shared design files, but code lends itself to reuse much more easily than e.g. "good checkout UX".
If you're not familiar, her channel is great. E.g. youtu.be/suhEIUapSJQ
How do we get @juxtopposed.bsky.social to help fix all the OSS apps ๐
Dear France, we're sorry, we still love you.
"We won't leave NATO; we'll just sabotage it from within."
Highly recommend catching a rocket launch from there if you can.
Aussies got it right with mandatory voting
BitWarden CLI is a decent alternative to Vault for key management ๐
100% agree
Folks out there, living their dreams
Damn, Canada is not messing around ๐จ๐ฆ