Levin Rickert

@zeddotdev Will right-click actions like "Cherry pick" and similar be added?

🚀 We just shipped v.0.231! Git graph is finally here: Open it from the git panel or the command palette (git graph: open).

@pie6k Also this version has too much movement for my taste.

Version with reduced motion

Experimenting with the new screen.studio captions rendering engine. I quite like it, but I'm a bit worried that effects like motion (with motion blur) will reduce readability.

@pie6k That's way too noisy due to the animated movement. It's fancy, yes, but I can't follow well.

@pie6k @Larkef As long as the new one also gets such a cool animation as the current one on the homepage... 😅

@Larkef is cooking a new screen.studio logo. We have a deal - we like our current logo, and we will only replace it if the new one somewhat resembles it while being much better. I think we will replace it.

@lochieaxon @nilsonsfj @alexvanderzon Same for me. I'm on the latest Android Chrome version.

@nilsonsfj @alexvanderzon should be getting haptics with the navigator.vibrate() API. can you check browser version against the compatability table here? 🤔 developer.mozilla.org/en-US/docs/Web…

It's time to bring Haptics to the web 🫨 Create custom tactile patterns with strengths + durations for your web interactions. Make your app feel as good as it looks ✨ → haptics.lochie.me

@pie6k Sadly the demo doesn't work on mobile. Apparently no touch handlers 🥲

So simple, so beautiful

@marvr_ @pie6k I don't think WebGL is locked to 60 fps max.

@pie6k Is it because it's Electron or a browser in general and not native? I mean even with Tauri and Webkit it's locked to 60 FPS. Maybe it's just not capable of more work without letting the fans spin, so going all native is the only way. But that's another issue 🫠

It is quite ironic learning. TLDR: Sometimes you might not want better performance. We had a GPU memory bottleneck. It means the editor was sometimes waiting for memory, resulting in lower FPS. I did dig quite deep, and while torturing my brain quite a lot, I managed to resolve this. FPS went up to even 120 FPS at times, with motion blur and everything running in real time. It allowed the GPU to do more work in less time, as it is not waiting for memory, but it means it heats up more and uses more energy. As a result, you have a better editor experience, but you also hear this uncomfortable noise, which I know for sure will annoy users (me included) a lot. Not sure how to approach this.

@AL8ATROS @pie6k Can the license somehow be transferred so I can buy another year of updates?

@AL8ATROS @pie6k Different question on that topic: I had a lifetime license registered through my previous employer. I'm gone, the license was attached to my work mail address. I would like to personally continue using it but the subscription isn't something for me.

Coding quite hard rewriting the screen.studio rendering core from scratch. It unlocks a lot of new possibilities, like fully fully dynamic layouts, split-screen mode, and many more. Also polishing it to cultivate our philosophy - "never let users create ugly videos."

@devongovett It was super useful to build my own Timeline component which would collapse the middle items and replace them with a button to expand if over a certain amount.

@devongovett Documentation of RAC's Collections API and how to build your own components on top of it. I already did but I had to look a lot at how RAC uses it internally to fully understand it.

What do you want to see from React Aria this year? Anything from small fixes, API nits, DX improvements, feature suggestions, new components, etc. No promises but send me your wildest dreams. 😀

@devongovett Where is the documentation of the hooks? I can't find it anymore. And could we also get the internal Collections API documented? I found it super useful to build my own Timeline component but had to dig through the source code to figure out how to use it.

Introducing the new React Aria docs! 🎉 All-new content and search experience. Interactive CSS and Tailwind examples to get you started quickly – just install with shadcn. New guides and full example apps. MCP server and AI integrations. Check it out! react-aria.adobe.com

@MarcJSchmidt @codewithdavid I almost used Deepkit at work but there were concerns about maintenance from higher up because at least publicly it seemed to be just you behind it. Also low activity in the repo was a factor. TBH I don't think that's important but yeah. And also: Reach. That is missing.

@codewithdavid shit

ok serious talk, why was deepkit not a wild success, and why has it not replaced nestjs yet? what do we need to improve? what is missing?

@MarcJSchmidt Unsure why but I think you were lacking reach and also NestJS was already established. Still I think Deepkit is great! Maybe also SEO stuff? The name sounds like ML stuff, not a backend framework.

I wanted deepkit to replace nestjs, to be what Spring is but in TypeScript. it seems to be failing, and I don't fully understand why. docs are not good, I agree, my skill in writing docs seems to be extremely bad, but is it that bad?

@theo On the other hand, if the backend can handle the traffic, why not send a request on each keystroke. It won't hurt.

@theo Calls to "check-name" seem to be denounced. The call that happens on every stroke is to "check-rule-state-for-proposed-repository". TBH I have no idea what it does. As it only takes the name as input it's definitely related to that but why isn't it denounced as well?

How exactly do you expect this to be implemented?

@adnansahinovich Drop me a DM. I'm currently looking for a new job.

Hiring is broken in 2025. I asked for one @react dev with real apps, but I got flooded with low-effort pitches and offshore teams with zero track records. We’re building fast, growing 10x a year, and need someone who’s shipped serious work. Remote-first. Berlin-based. Relocation costs included and amazing builder energy. Know someone legit? Tag them right now, let’s talk.

@GregHoarau @devongovett Maybe aria-labelledby on the 2nd column pointing to the first?

@GregHoarau @devongovett How to layout this is clear. I was wondering about the accessibility-aspect here.

New React Aria release! 📜 Infinite scroll in ListBox, GridList, Table, and Tree ⚛️ React 19 actions automatic form reset 🐲 Virtualized Tree drag and drop 🤝 Opened API to DOM events – improved integration with other libraries 📆 DatePicker autocomplete 🚀 And TONS more!

@devongovett I also thought about this but how do you simulate the 2 columns? Just 2 divs is probably not the best accessibility-wise?

@levrik_io I’d use a GridList for this if you won’t have the column headers.