Joe Donnelly @JoeSloth

@rauchg React compiler 🤠

@mattpocockuk @_baxuz @turborepo We disabled it because you can’t copy the stdout text. It also gets messed up when you have non-turbo tasks running in parallel

My talk from @Vercel Ship! I share how we ship desktop-level interaction performance on the web @Frame_io. youtube.com/watch?v=T1N8jh…

Introducing Restyle 🌈 A new CSS-in-JS library for React - Zero-runtime - Atomic class names - De-duplicates styles - Works in Server and Client Components - Supports `css` prop - Loads styles on demand - Allows shipping CSS in NPM packages reactstyle.vercel.app

After 4 long years of work we are so proud to announce Frame.io Version 4. I’m so grateful to work with such amazing individuals that relentlessly brought this vision to life. You all have set a new bar in design, quality and performance. This is one badass piece of software 🦾💜

Frame.io @Frame_io

3 years ago

It's here. The all-new Frame.io Version 4. Now in beta.

28 51 461 150K 215

Introducing Frame.io version 4, a revolutionary new creative management platform. This release is pure heart and soul. It was crafted with the utmost care and unrelenting determination to make something truly special.

@emerywells Maybe that’s too pessimistic. It will be quaint.. ignored until socially valuable.

@emerywells Ignored.

as a longtime fan of Conway's "Game of Life" algorithm i never once considered visualizing the time axis physically -- this is breathtaking and elegant to me credit: instagram.com/reel/C2hoRnFsm…

V6 of our website is live 🚀 ❄️ activetheory.net

New drop from our @Frame_io brand crew. I'm super proud of this one. It’s the best motion graphics piece we've ever done. Goes HARD!

the perfect site doesn't exist... infiniteflowers.net

Cleaning a bit and came across my @jeresig autographed copy of jQuery 1.4.2.

Visual Studio solves the second hardest problem in computer science - naming things. Coming soon...

I get asked about this a lot (especially since the launch of Epic Web), so I've written it down. Here's why I won't use Next.js: epicweb.dev/why-i-wont-use…

One misunderstanding is that this way of working leads to some tech debt: I don't think it does, if the designers/engineers know what they are doing. No-one is going to create a new button component because it's 1px larger than what exists in the code. So we have components, color, type, animation system in code, called Orbiter which uses story book. The whole @linear app supports custom themes which impossible to do if don't build in a systematic way. Most apps I know if don't support that outside if IDEs). The point is that it's not worth it to try to have some canonical design files for every view or component we have. We deploy new code multiple times a day and there are new things every week. (Our latest changelog from the past 2 weeks had 6 major changes, 50 smaller changes). The app is always the canonical source of truth. So the workflow is to design with the canonical source, have new design as a reference, then as we go to build stage, we align things with the existing system if possible and extend if not possible. So by the time the feature is launched, the initial design is probably already outdated. It's pretty classic design process of "diverge->converge". You start with wide explorations, refine the design and as we built, it gets more tuned in to fit in the overall system. Why this also work for us is that our way of working is letting people "close to the metal" - design/eng drive the project at all points, and have agency when it comes to decisions around product features or how they work. Which we can do because explicitly hire for that skillset.

keyboard_arrow_left Previous keyboard_arrow_right Next

Karri Saarinen @karrisaarinen

3 years ago

Primer on how we design at @linear: The main point is that the design is only a reference, never any kind of deliverable itself, so the way it's constructed doesn't really matter. 1. We screenshot the app and design on top of 2. Simple design system that has mostly colors,

keyboard_arrow_left Previous keyboard_arrow_right Next

80 189 3K 1.2M 3K

PM deciding how much of the backlog they’re going to commit to this quarter’s roadmap

Today I got called out by the legendary @garrytan for some unfortunate bugs he’s been experiencing in Frame. Oof, he was right. Because of that, I decided it’s time to let you all in on a big secret. If you’ve been observing Frame.io from the outside, you may have noticed our product updates have slowed down and have wondered what’s been going on. I’ve witnessed this myself with other products I’ve been a customer of. A once innovative company you love seems to quietly fade off. It often means they’ve lost their steam or frankly stopped caring. Is that what’s happening to the Frame product? Hell to the no! Secretly, internally, we’ve had a roaring engine of innovation and we’re building the BEST stuff in the 8 year history of Frame. If you could walk inside the virtual Frame office, you’d feel the heat immediately because the team has been COOKING. For the past 3 years we’ve been working on a brand new version of Frame.io, truly redesigned from the ground up. It’s the most important work of my professional life and we plan on sharing it with all of you sometime early next year. We didn’t think it would take this long but alas, here we are. We’ve set insane goals for ourselves on not only the product features we’re delivering but also around product craft, quality, and reliability. When it comes to truly delightful products, we’re striving to set a new bar for the industry. I love how products like @linear and @arcinternet are continuing to drive up our expectations of great software and we fully expect the next version of Frame to to live amongst them. Because we’ve been dedicating SO much time and energy into the new version of our product, I acknowledge it’s led to an increase in bugs of our existing product. We have a swat team working to reduce some of those pesky bugs and ultimately I’m confident this will all be worth it. Today, we’re smack in the messy middle. As I write this message, we have hundreds of designers, engineers, and product people who are tirelessly working to bring this mission to life. Huge shoutout to all the Frame team who are reading this. I also have to say, our colleagues at Adobe have been SO supportive. What an incredible company to be a part of. There’s a lot of exciting work we’re doing with Frame, across Adobe Creative Cloud. In many ways, I think Frame was a pioneer in high quality creative software on the web and I have to tell you, the new frame is fucking awesome. To all the old and new Frame supporters out there, we’ve been building this new version for you. Thank you 🤍🤍

Whoot! I just learned you can use animatable CSS grid rows to transition an element's height from 0 to auto! Toggle a class and see the magic happen. Thx to @chriscoyier for sharing this little gem. 💯 chriscoyier.net/2022/12/21/thi… Video alt: Exampe showing an animated height.

@jaredpalmer @vercel Built in storybook.. but better