正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Mediabunny 1.42.0 is now out, adding THE most requested feature: full read/write support for HLS! 🚀 It's truly a game changer for client-side media processing. Here, I'm creating 5 renditions from a 40-second video in ~10 seconds, fully client-side, without a transcode server:

Vanilagy

3,384 subscribers

54,833 次观看 • 1 个月前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

In LiveView, we keep the state in one place - the server - and it simplifies a lot. But sometimes the state on the client is preferred, or even necessary, and we can't use LiveView for that part. Unless we have a LiveView that runs on the client 👀 Using Popcorn, we managed to run LiveView fully in the browser – here's a POC 🎉 The approach is to have a fully client-side LiveView rendered by a server-side one, and they can communicate with each other. Try it out:

In LiveView, we keep the state in one place - the server - and it simplifies a lot. But sometimes the state on the client is preferred, or even necessary, and we can't use LiveView for that part. Unless we have a LiveView that runs on the client 👀 Using Popcorn, we managed to run LiveView fully in the browser – here's a POC 🎉 The approach is to have a fully client-side LiveView rendered by a server-side one, and they can communicate with each other. Try it out:

Elixir by Software Mansion

13,509 次观看 • 5 个月前

🧵1/2 Socket Programming in C: Server-Side Basics - Set up a server using socket(), bind(), and listen(). - Accept client connections with accept(). - Send and receive data over TCP. Video 1: Server-Side in C! Video 2: Client-Side Programming will be uploaded soon—stay tuned! 🖥️

🧵1/2 Socket Programming in C: Server-Side Basics - Set up a server using socket(), bind(), and listen(). - Accept client connections with accept(). - Send and receive data over TCP. Video 1: Server-Side in C! Video 2: Client-Side Programming will be uploaded soon—stay tuned! 🖥️

trish

2,924,461 次观看 • 1 年前

❌ Avoid resolving a promise in a server component and block rendering. ✅ Resolve the promise in the client side with `Reac.use()`

❌ Avoid resolving a promise in a server component and block rendering. ✅ Resolve the promise in the client side with `Reac.use()`

George Moller

47,187 次观看 • 1 年前

🚀 BIG NEWS: I'm Going Indie & Launching My First Course! 🤩 After 7.5 amazing years WeTransfer, I'm leaving a truly special company and team. It's bittersweet, but going fully independent is a dream come true. Read my full story: 🌟 New Course: From Side Project to Going Indie 🌟 Are you ready to make your side project a success? Want to quit the 9-to-5 routine and endless meeting days to go independent? Perfect! This course is for you: #IndieDev

🚀 BIG NEWS: I'm Going Indie & Launching My First Course! 🤩 After 7.5 amazing years WeTransfer, I'm leaving a truly special company and team. It's bittersweet, but going fully independent is a dream come true. Read my full story: 🌟 New Course: From Side Project to Going Indie 🌟 Are you ready to make your side project a success? Want to quit the 9-to-5 routine and endless meeting days to go independent? Perfect! This course is for you: #IndieDev

Antoine v.d. SwiftLee 

35,637 次观看 • 1 年前

The client requested a parlour wedding decoration, wait for the result..

The client requested a parlour wedding decoration, wait for the result..

CHUKS 🍥

222,540 次观看 • 4 个月前

Just discovered Blockade Labs - what a game changer! Spent my night building a simple #WebXR client for it using #threejs and now I can spend hours exploring these marvelous worlds without taking off my headset. 🤯🚀 #VR #stablediffusion

Just discovered Blockade Labs - what a game changer! Spent my night building a simple #WebXR client for it using #threejs and now I can spend hours exploring these marvelous worlds without taking off my headset. 🤯🚀 #VR #stablediffusion

Felix Z

29,859 次观看 • 3 年前

Having ChatGPT edit in Xcode is a game-changer Can edit across multiple apps and works with 4.5. It's just missing the ability to read the codebase, write multiple files and agents. For now, Alex is a great alternative.

Having ChatGPT edit in Xcode is a game-changer Can edit across multiple apps and works with 4.5. It's just missing the ability to read the codebase, write multiple files and agents. For now, Alex is a great alternative.

Meng To

40,579 次观看 • 1 年前

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

Delba

43,989 次观看 • 2 年前

React tip: "use client" misconceptions (1/5) 🚫 You need to mark EVERY individual file with "use client" to ensure it is a Client Component. ✅ You only need to mark each client entry point ONCE. Modules imported into a "use client" file are already part of the client bundle. (0:05) Adding "use client" to `3.js` marks the file as a client entry point, including it in the client bundle. (0:11) Importing `d()` into `3.js` (a client entry point) also includes it in the client bundle. (0:14) Adding "use client" to `4.js` has no additional bundling effect on `d()` because it is already part of the client bundle. (0:23) All modules (and their dependencies) imported to `3.js` are included in the client bundle. (0:26) Removing "use client" from `3.js` moves it and its dependencies into the server bundle.

React tip: "use client" misconceptions (1/5) 🚫 You need to mark EVERY individual file with "use client" to ensure it is a Client Component. ✅ You only need to mark each client entry point ONCE. Modules imported into a "use client" file are already part of the client bundle. (0:05) Adding "use client" to `3.js` marks the file as a client entry point, including it in the client bundle. (0:11) Importing `d()` into `3.js` (a client entry point) also includes it in the client bundle. (0:14) Adding "use client" to `4.js` has no additional bundling effect on `d()` because it is already part of the client bundle. (0:23) All modules (and their dependencies) imported to `3.js` are included in the client bundle. (0:26) Removing "use client" from `3.js` moves it and its dependencies into the server bundle.

Delba

157,319 次观看 • 2 年前

Server authoritative movement with client prediction and rollback/replay support. In this example, the client exploits by moving a wall out of the way. But the server owns the movement. The client has failed predictions due to the exploit, and rolls back. #RobloxDev

Server authoritative movement with client prediction and rollback/replay support. In this example, the client exploits by moving a wall out of the way. But the server owns the movement. The client has failed predictions due to the exploit, and rolls back. #RobloxDev

sleitnick

20,016 次观看 • 1 年前

Watch BurpAI find and exploit a Server Side Template Injection bug. Video by Tib3rius, for the full video check out 👇

Watch BurpAI find and exploit a Server Side Template Injection bug. Video by Tib3rius, for the full video check out 👇

Burp Suite

11,556 次观看 • 4 个月前

"I'm here to win the game. It's a special moment for me." Darrell Clarke is excited for his Barnsley side to face Manchester United at Old Trafford in the Carabao Cup 🤩

"I'm here to win the game. It's a special moment for me." Darrell Clarke is excited for his Barnsley side to face Manchester United at Old Trafford in the Carabao Cup 🤩

Sky Sports Football

61,122 次观看 • 1 年前

For those who didn't see the end of this game, here is the 5 second calls side-by-side: you can see how drastic the difference in cadence was

For those who didn't see the end of this game, here is the 5 second calls side-by-side: you can see how drastic the difference in cadence was

Mike Jagacki

110,349 次观看 • 2 个月前

I've finally published a new version of next-international, my fully typesafe i18n library for Next.js This release adds initial support for the App Router, with both Client and Server Components:

I've finally published a new version of next-international, my fully typesafe i18n library for Next.js This release adds initial support for the App Router, with both Client and Server Components:

Tom Lienard

42,459 次观看 • 2 年前

You can now try client-side rendering in Remotion!

You can now try client-side rendering in Remotion!

Jonny Burger

76,698 次观看 • 5 个月前

Liberals are now admitting Obamacare is a failure without even realizing it, and trying to blame the Republicans. Rather than blaming themselves for creating the mess, they’re blaming the other side for exposing what a mess it is. These people truly are a lost cause.

Liberals are now admitting Obamacare is a failure without even realizing it, and trying to blame the Republicans. Rather than blaming themselves for creating the mess, they’re blaming the other side for exposing what a mess it is. These people truly are a lost cause.

One Bad Dude

126,093 次观看 • 7 个月前

Just shipped this VSL ad for a client Made most of the B roll with VO3 Such a game changer Can you tell which scenes are AI vs real clips?

Just shipped this VSL ad for a client Made most of the B roll with VO3 Such a game changer Can you tell which scenes are AI vs real clips?

Salif Sibane

24,179 次观看 • 10 个月前

New video! ChatGPT's new UI has plenty of UX/latency bugs and here is why client-side frameworks are not a silver bullet:

New video! ChatGPT's new UI has plenty of UX/latency bugs and here is why client-side frameworks are not a silver bullet:

José Valim

131,693 次观看 • 1 年前