Загрузка видео...

Не удалось загрузить видео

На главную

Introducing Tamagui 3. Now the fastest and highest coverage Tailwind style library there is, free or paid. Tamagui is now 100% open source, I’ve made Takeout and Bento OSS as well. A rewritten compiler in rust now makes native even faster, plus a new C++ native runtime avoids re-rendering....

42,954 просмотров • 4 дней назад •via X (Twitter)

Комментарии: 30

Фото профиля Rbto
Rbto4 дней назад

We’ve loved using tamagui for and look forward to moving to v3.

Фото профиля Nate
Nate4 дней назад

It’s a big change but also a big upgrade

Фото профиля AndreaMic
AndreaMic4 дней назад

Great Nate! I might try to work on an update on the Figma file, which is still anchored at 1.2.1

Фото профиля Nate
Nate4 дней назад

That’s be great. I bet AI could automate generating it.

Фото профиля Sachin
Sachin4 дней назад

Making Takeout and Bento open source is a big deal for anyone shipping React Native and web from one codebase. Going to try Tamagui 3 on my next Next.js project.

Фото профиля Dhanji Bhagat
Dhanji Bhagat4 дней назад

Open-sourcing it is a big move. A Rust compiler and C++ runtime for a React-style UI library is an interesting combination. Curious to see how it performs in real projects

Фото профиля Hirvesh
Hirvesh3 дней назад

I am excited! Tamagui helped me build @habit_pixel_app and now v3 is going into building my second app! Can't wait 😁

Фото профиля gee
gee4 дней назад

brilliant job nate. so excited for this one for the next project. cheers.

Фото профиля John Jeong
John Jeong4 дней назад

awesome stuff

Фото профиля peterferguson.eth
peterferguson.eth3 дней назад

Nice the styling api was a deal breaker for me before Looking forward to trying this out

Фото профиля Anton wester
Anton wester4 дней назад

This looks amazing! Will migrate my web projects to it as well to try out.

Фото профиля nnft
nnft4 дней назад

Brilliant! I love the competition. Going to look into this

Фото профиля Eelco Wiersma
Eelco Wiersma4 дней назад

Looks like the best of both worlds, nice approach. Congrats on the release!

Фото профиля Dan Flanagan
Dan Flanagan4 дней назад

Going to have to upgrade one of my smaller projects and see how easy it is to convert. Been loving these libraries and all my projects use them

Фото профиля Celestial Rose
Celestial Rose4 дней назад

THIS IS THE WAY TO GO !!!! BRAVO!!!

Фото профиля Pavit Chhabra
Pavit Chhabra3 дней назад

👀 been a while since I've tried Tamagui

Фото профиля Yamin
Yamin4 дней назад

Looks good! Glad to see RSD isn’t dead

Фото профиля Danny Wilson
Danny Wilson3 дней назад

This is absolutely fantastic

Фото профиля Guillem Puche
Guillem Puche3 дней назад

Congraaaaats!!!

Фото профиля Jssl
Jssl4 дней назад

Whoa 😯

Фото профиля ༼ ◕_◕ ༽
༼ ◕_◕ ༽2 дней назад

lol this is like 4 major versions in one. congrats @natebirdman excited to give it a try.

Фото профиля Neon.tsx
Neon.tsx4 дней назад

So excited for this, been long I heard from Tamagui.

Фото профиля Brjan | AI Builder
Brjan | AI Builder3 дней назад

the shift to Rust for the compiler could cut down build times significantly

Фото профиля Hasira 🍁🪴
Hasira 🍁🪴4 дней назад

Bro, just use native css, it’s not that hard

Фото профиля Axiom 🔬
Axiom 🔬4 дней назад

Tamagui 3 sounds like the kind of release where agents need a migration receipt: input component, generated CSS/native output, compiler version, runtime path, and perf delta. Then a coding agent can refactor UI without treating style output as magic.

Фото профиля RedMan
RedMan4 дней назад

Keeping completions useful while a file is half-written is a thoughtful detail. The tree-sitter choice matters because that’s exactly when someone learning the new style syntax needs help.

Фото профиля felix negentropy. weallareeuropean
felix negentropy. weallareeuropean3 дней назад

so now everyone doing rewrite

Фото профиля rahulvramesh ⚡
rahulvramesh ⚡3 дней назад

menu ui seems broken

Фото профиля Nate
Nate3 дней назад

Thanks, fixed

Фото профиля Taha Muhammad
Taha Muhammad3 дней назад

@sebastienlorber People don’t have issues with the performance, we have issues with the usability and functionality. It is a nightmare to be able to accurately use the interaction pattern is bad

Похожие видео

Introducing Aval - a new open source format for interactive video on the web. It has a built-in state machine, frame accurate transitions, and packed alpha transparency. This is probably the craziest thing I’ve ever built with Codex. I’d been dreaming about this technology for years. Before AI, building it would have taken months of work. I could never justify that investment for a noncommercial open source project. Then, a little over a year ago, Airbnb created Lava for almost exactly the same purpose. That gave me hope. But Lava was never released as open source. So I decided to build my own, with AI. Aval comes with a compiler and a web renderer. Together, they give you: • a deterministic state graph - named states, authored triggers, and routing where the latest trigger wins. • frame accurate routes with transitions that begin on authored content frames using portals, finishes, cuts, and reversals. • small file size and low CPU overhead, perfect for small icons designed and animated in Blender. • seekless loops so the decoder timeline keeps moving forward across loop seams instead of seeking. • packed alpha transparency. transparent prerendered motion composited with WebGL2. • a web native runtime: decoding with WebCodecs and rendering with WebGL2. • progressive fallback: Host-owned fallback markup remains available for unsupported and reduced motion contexts. Now it exists, it’s open source, and it’s available today as a technical preview. I’ll be polishing it further over the next few days.

Alex Barashkov

277,909 просмотров • 3 месяцев назад

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.

Gergely Orosz

52,395 просмотров • 4 месяцев назад