正在加载视频...

视频加载失败

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

I might have just figured out how to integrate Web Workers with TanStack Table V9... So... multi-threaded TanStack Table coming soon? This would theoretically unlock huge UI performance wins for specific large tables that use heavy client-side computations for filtering, sorting, aggregation, etc. In a normal setup, the UI... show more

Kevin Thomas Van Cott

3,214 subscribers

44,178 次观看 • 1 个月前 •via X (Twitter)

教育新闻政治科学技术

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

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

相关视频

JUST IN: President Trump tells Maria Bartiromo that an end to the conflict in Iran could come very soon. "If they're going to have a nuclear weapon, we'll be living with them for a little while. But I don't know how much longer they can survive."

JUST IN: President Trump tells Maria Bartiromo that an end to the conflict in Iran could come very soon. "If they're going to have a nuclear weapon, we'll be living with them for a little while. But I don't know how much longer they can survive."

Fox News

274,309 次观看 • 4 个月前

designers love to hate on raw, unfinished things. redesigning the whole ios/watchos/macos/... ui after a decade is a brutal challenge for any design team! almost impossible to satisfy the expectation. most haters around here have never designed in a large organization like apple and are not aware of challenges such as politcs, opiniated stakeholder, impossible deadlines, the list goes on... i empathise with the ui designers in apple. yes! os26 and liquid glass feels rough at the moment! so did the ios7 at launch. it evolved. this will too. i appreciate the brave direction apple has taken with this liquid glass ui. yes it comes with challenges including readability, compatibility and more... let's stop b*tching about it and contribute to solutionise these challenges.

designers love to hate on raw, unfinished things. redesigning the whole ios/watchos/macos/... ui after a decade is a brutal challenge for any design team! almost impossible to satisfy the expectation. most haters around here have never designed in a large organization like apple and are not aware of challenges such as politcs, opiniated stakeholder, impossible deadlines, the list goes on... i empathise with the ui designers in apple. yes! os26 and liquid glass feels rough at the moment! so did the ios7 at launch. it evolved. this will too. i appreciate the brave direction apple has taken with this liquid glass ui. yes it comes with challenges including readability, compatibility and more... let's stop b*tching about it and contribute to solutionise these challenges.

Oykun

347,810 次观看 • 1 年前

While working on a new video with solutions to the previous one, I found ChatGPT's new UI struggles even more with concurrent updates: entries lose state and stick around for too long (see video). If this was a LiveView app, we would be getting so much flak.😅 --- I believe part of the problem here is having separate mutate and fetch requests on every deletion. The first fetch is cancelled when the second one comes up, causing items to stick around for longer. Many said yesterday that you could do the mutation and fetch as a single request, but that leads to other problems, such zombie entries. For example, imagine you delete link1 and link2 within a brief period of time. There is no guarantee the deletion order in the database will match the order the client receives the response, so you may end up with this: 1. (client) request to delete link1 sent 2. (client) request to delete link2 sent 3. (server) deletes link1 and loads a new list (includes link2) 4. (server) deletes link2 and loads a new list (no link1 or link2) 5. (client) receives link2 response 6. (client) receives link1 response So if you choose to use the latest response (link1), you brought link2 back to life. If you say you will use the response from the last request, events 3-4 can be swapped, and now you bring link1 back to life. Another way to solve this is by basically not allowing concurrent requests at all but that can affect the user experience drastically in other ways. Next week I should publish a video explaining how LiveView tackles this. Stay tuned!

While working on a new video with solutions to the previous one, I found ChatGPT's new UI struggles even more with concurrent updates: entries lose state and stick around for too long (see video). If this was a LiveView app, we would be getting so much flak.😅 --- I believe part of the problem here is having separate mutate and fetch requests on every deletion. The first fetch is cancelled when the second one comes up, causing items to stick around for longer. Many said yesterday that you could do the mutation and fetch as a single request, but that leads to other problems, such zombie entries. For example, imagine you delete link1 and link2 within a brief period of time. There is no guarantee the deletion order in the database will match the order the client receives the response, so you may end up with this: 1. (client) request to delete link1 sent 2. (client) request to delete link2 sent 3. (server) deletes link1 and loads a new list (includes link2) 4. (server) deletes link2 and loads a new list (no link1 or link2) 5. (client) receives link2 response 6. (client) receives link1 response So if you choose to use the latest response (link1), you brought link2 back to life. If you say you will use the response from the last request, events 3-4 can be swapped, and now you bring link1 back to life. Another way to solve this is by basically not allowing concurrent requests at all but that can affect the user experience drastically in other ways. Next week I should publish a video explaining how LiveView tackles this. Stay tuned!

José Valim

22,976 次观看 • 1 年前

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

Avi Chawla

30,932 次观看 • 9 个月前

SplitPaneKit This is something I've wanted to componentize for a while. We've seen this pattern appear in a few apps now, I even use it at Abode. It has a couple "gotcha" moments with performance and optimisation while animating separate or child views with the drag and translation of the split views, handling breakpoints etc, I thought I'd put it into a nice package. I actually made quite a few optimisations from how I handle this with Abode in this package. So might need to implement it over there😅 As before, right now its UIKit only, but SwiftUI host will likely come over the next few days as I make improvements and final changes to the initial API from feedback. - Draggable split-pane interface - Custom breakpoints or built-in presets - Scroll view integration - drag from content or handle - Coordinated animations with pan-effecting views - UIKit

SplitPaneKit This is something I've wanted to componentize for a while. We've seen this pattern appear in a few apps now, I even use it at Abode. It has a couple "gotcha" moments with performance and optimisation while animating separate or child views with the drag and translation of the split views, handling breakpoints etc, I thought I'd put it into a nice package. I actually made quite a few optimisations from how I handle this with Abode in this package. So might need to implement it over there😅 As before, right now its UIKit only, but SwiftUI host will likely come over the next few days as I make improvements and final changes to the initial API from feedback. - Draggable split-pane interface - Custom breakpoints or built-in presets - Scroll view integration - drag from content or handle - Coordinated animations with pan-effecting views - UIKit

Joseph Smith

23,552 次观看 • 1 年前

I feel weird even bringing this up, but here we go. Subscriptions are open on my page. There is no graceful way to say that, so please take this with a kind heart. I know a lot of people are struggling financially, and I don’t want anyone stretching themselves for me. I have a great job. I’m just letting people know it exists because some of you asked. I’m not even saying I’m worth the money. I’ll be honest, I’m not the best person to subscribe to. I’m not an OnlyFans girl, I’m not teaching you how to get monetized, I’m not running a masterclass in anything. The subscriber section is literally just more personal, everyday stuff. It’s boring in a comforting way. You’re not missing anything. If you ever feel like hanging out with me on the quieter side of this app, it’s there. If not, all good. I just wanted to put it out there for anyone who might be interested. Pro tip: if you subscribe to anyone, please do it on a browser. If you do it through the Apple Store or the Google store, they take 30% and put it in their pocket. Those companies are rich enough. I have a real problem with them getting any money or subscribers. I didn’t know that when I first started subscribing to people. PS: if you are a current subscriber or a new subscriber, please go to my homepage and click on the subs tab. I post content there, but it doesn’t automatically show up in your feed. PPS: Please don’t be nasty to me in the comments if you don’t want to subscribe. I’m not a mean person. I can’t think of a humble way to tell people. This wasn’t easy for me to write.

I feel weird even bringing this up, but here we go. Subscriptions are open on my page. There is no graceful way to say that, so please take this with a kind heart. I know a lot of people are struggling financially, and I don’t want anyone stretching themselves for me. I have a great job. I’m just letting people know it exists because some of you asked. I’m not even saying I’m worth the money. I’ll be honest, I’m not the best person to subscribe to. I’m not an OnlyFans girl, I’m not teaching you how to get monetized, I’m not running a masterclass in anything. The subscriber section is literally just more personal, everyday stuff. It’s boring in a comforting way. You’re not missing anything. If you ever feel like hanging out with me on the quieter side of this app, it’s there. If not, all good. I just wanted to put it out there for anyone who might be interested. Pro tip: if you subscribe to anyone, please do it on a browser. If you do it through the Apple Store or the Google store, they take 30% and put it in their pocket. Those companies are rich enough. I have a real problem with them getting any money or subscribers. I didn’t know that when I first started subscribing to people. PS: if you are a current subscriber or a new subscriber, please go to my homepage and click on the subs tab. I post content there, but it doesn’t automatically show up in your feed. PPS: Please don’t be nasty to me in the comments if you don’t want to subscribe. I’m not a mean person. I can’t think of a humble way to tell people. This wasn’t easy for me to write.

Sovey

21,268 次观看 • 9 个月前

Honestly, I don't get why Vgen still doesn't have basic price sorting or filters in 2026 😩 You're telling me I have to click into every single commission listing just to find out the price... and half the time it's way out of my budget? To solve this: I developed VGENUnlocked. It fixes the BS: 1. Prices show automatically as you scroll through commissions 2. Hover over "mature" images → they unhide instantly 3. Set a min/max price range and everything outside it gets filtered out automatically 4. Sort by price, rating, or review count. Actual useful controls. If you hunt for commissions on Vgen, this is about to make your life 10x easier.

Honestly, I don't get why Vgen still doesn't have basic price sorting or filters in 2026 😩 You're telling me I have to click into every single commission listing just to find out the price... and half the time it's way out of my budget? To solve this: I developed VGENUnlocked. It fixes the BS: 1. Prices show automatically as you scroll through commissions 2. Hover over "mature" images → they unhide instantly 3. Set a min/max price range and everything outside it gets filtered out automatically 4. Sort by price, rating, or review count. Actual useful controls. If you hunt for commissions on Vgen, this is about to make your life 10x easier.

✨ 𝗗𝗔𝗥𝗞 ✨ Shitposter Detective

253,495 次观看 • 2 个月前

So often when discussing training / dryfire / shooting its like we are speaking 2 different languages. There are key concepts that some people are either unaware of, or choose to ignore that preclude having a productive discussion. For example if I were to say "slapping or smashing your trigger is perfectly fine for most shots" a bunch of people would be up in arms, talking about slowly working to the wall, letting the shot surprise you, etc. Experienced, performance-focused shooters will know that with a good grip or mount, I am right, and that how you mechanically move the trigger isnt super important. When you get to low %, or distance shots, you are increasing your level of confirmation of your dot or sights, and the trigger pull is maybe 10-15% slower. This is a video of me, absolutely smashing the trigger with 2-3x the force needed. Its not as stable as i would like, but im also having to straddle 2 tripods to get this shot lined up...🤣

So often when discussing training / dryfire / shooting its like we are speaking 2 different languages. There are key concepts that some people are either unaware of, or choose to ignore that preclude having a productive discussion. For example if I were to say "slapping or smashing your trigger is perfectly fine for most shots" a bunch of people would be up in arms, talking about slowly working to the wall, letting the shot surprise you, etc. Experienced, performance-focused shooters will know that with a good grip or mount, I am right, and that how you mechanically move the trigger isnt super important. When you get to low %, or distance shots, you are increasing your level of confirmation of your dot or sights, and the trigger pull is maybe 10-15% slower. This is a video of me, absolutely smashing the trigger with 2-3x the force needed. Its not as stable as i would like, but im also having to straddle 2 tripods to get this shot lined up...🤣

Havoc 2-1

35,672 次观看 • 1 年前

(Yes i know the movement is exaggerated, its just to show the motion, it also doeant move like jello when in vr) -Left is before, Right is after- Ok wall of text time for the nerds Literally everything is the same on both sides except the position of 1 bone (made sure that even after adjusting, the collider would still be in the same spot) The reason for this change is because she wanted to be able to clap her ass in vr, and last time i did this all i did was add a toggle for a hidden bone that moved, and its angle would trigger the sound. Which was because that with my previous position, the cheeks could never really meet in the middle when in motion unless you just pushed them together with your hands, and i wanted to just have the sound actually be triggered by them colliding with each other This is also the first time ive used endbones to help drive the movement, so now thanks to that and all my previous experimenting with squishing as well, I can now get bones to move exactly how i want them to move when in natural motion. And i know a lot of people are gonna ask me to teach them how or explain my thought process but i literally just go off feeling lmao. Like, i just kinda visualize in my head how i want the motion to look, and then i just kinda know where to put everything, so im not even sure how to even start explaining rip. I have the things that artist want where they can just make the shit in their head exactly how they envisioned it lol I have a few more ideas i want to try, so we'll see if theyre good enough to get a tweet lol Thank you for coming to my ted talk

(Yes i know the movement is exaggerated, its just to show the motion, it also doeant move like jello when in vr) -Left is before, Right is after- Ok wall of text time for the nerds Literally everything is the same on both sides except the position of 1 bone (made sure that even after adjusting, the collider would still be in the same spot) The reason for this change is because she wanted to be able to clap her ass in vr, and last time i did this all i did was add a toggle for a hidden bone that moved, and its angle would trigger the sound. Which was because that with my previous position, the cheeks could never really meet in the middle when in motion unless you just pushed them together with your hands, and i wanted to just have the sound actually be triggered by them colliding with each other This is also the first time ive used endbones to help drive the movement, so now thanks to that and all my previous experimenting with squishing as well, I can now get bones to move exactly how i want them to move when in natural motion. And i know a lot of people are gonna ask me to teach them how or explain my thought process but i literally just go off feeling lmao. Like, i just kinda visualize in my head how i want the motion to look, and then i just kinda know where to put everything, so im not even sure how to even start explaining rip. I have the things that artist want where they can just make the shit in their head exactly how they envisioned it lol I have a few more ideas i want to try, so we'll see if theyre good enough to get a tweet lol Thank you for coming to my ted talk

Pixel

27,240 次观看 • 1 年前

Rumor has it I’m still swimming… 😂 Lol, but hey, I’m about to get real for a second. There have been many moments recently where I’ve felt like the currents have been too tough to swim through… All I wanted to do was throw in the towel and come up for air. But it’s in moments like this where I remind myself that I CAN swim… and I’m actually a damn strong swimmer at that! I may have to hold my breath for a little longer, or paddle a bit harder, but I always make it to the other side. So this is your reminder to just keep swimming. If I can do it, so can you. Whatever it is, you’ve got this ❤️ #mentalhealth

Rumor has it I’m still swimming… 😂 Lol, but hey, I’m about to get real for a second. There have been many moments recently where I’ve felt like the currents have been too tough to swim through… All I wanted to do was throw in the towel and come up for air. But it’s in moments like this where I remind myself that I CAN swim… and I’m actually a damn strong swimmer at that! I may have to hold my breath for a little longer, or paddle a bit harder, but I always make it to the other side. So this is your reminder to just keep swimming. If I can do it, so can you. Whatever it is, you’ve got this ❤️ #mentalhealth

Janna Breslin

35,598 次观看 • 2 年前

I always wondered "What if I port my three.js game to Rust? Will it improve performance?" I finally ported it to both Rust Desktop and Rust WASM (that runs on the browser) Comparing the three.js version with the Rust desktop I had a clear winner: Rust desktop. But now I took the time to port it to the web using Web Assembly (WASM) And my conclusion is... A tie! Both versions averaged 42FPS (60FPS if running one at a time) So if your goal is to ship a web game, it doesn't even matter the tech you use. (Three.js is recommended because the ecossystem is huge though) As long you optmize well (Web workers, reduce triangles, draw calls, etc) you should be good to go. But in the event you want to ship a native game to publish on Steam a system language (Rust, C++, etc) will be better for you. Now I want to port the three.js game to Desktop using Electron and see the results. I'll let you know. Btw, I'm open to new freelance projects. If you have anything for me, my DMs are open!

I always wondered "What if I port my three.js game to Rust? Will it improve performance?" I finally ported it to both Rust Desktop and Rust WASM (that runs on the browser) Comparing the three.js version with the Rust desktop I had a clear winner: Rust desktop. But now I took the time to port it to the web using Web Assembly (WASM) And my conclusion is... A tie! Both versions averaged 42FPS (60FPS if running one at a time) So if your goal is to ship a web game, it doesn't even matter the tech you use. (Three.js is recommended because the ecossystem is huge though) As long you optmize well (Web workers, reduce triangles, draw calls, etc) you should be good to go. But in the event you want to ship a native game to publish on Steam a system language (Rust, C++, etc) will be better for you. Now I want to port the three.js game to Desktop using Electron and see the results. I'll let you know. Btw, I'm open to new freelance projects. If you have anything for me, my DMs are open!

André → andreelias.dev

19,531 次观看 • 2 个月前

Sharing some more UI previews for Superlogical, this time the "tab peek." If you three-finger swipe down, you can "peek" at the other session tabs. These are live-updating, metal-rendered previews including splits. If you keep dragging, you enter a "mission control" style mode. This is one of those UI patterns that once you get used to, you mindlessly find yourself doing it ALL THE TIME. It's a great way to quickly take a look at everything thats going on. You aren't reading the mini text of course, but the shape of it tells you a lot about where things are. The peek pushes the terminal down off screen, it doesn't resize it, so it doesn't force any weird reflow or anything either. There's a lot more to talk about, especially about how this interacts with how we expose what needs attention so you can easily find the terminals/sessions/etc. that require your attention. Of course, you'll be able to drive this with the keyboard too. :) As always, a disclaimer: this is all early work subject to change, just trying to share some of what we're building in public. A lot of the UI experiential design is almonk so follow him for more updates too!

Sharing some more UI previews for Superlogical, this time the "tab peek." If you three-finger swipe down, you can "peek" at the other session tabs. These are live-updating, metal-rendered previews including splits. If you keep dragging, you enter a "mission control" style mode. This is one of those UI patterns that once you get used to, you mindlessly find yourself doing it ALL THE TIME. It's a great way to quickly take a look at everything thats going on. You aren't reading the mini text of course, but the shape of it tells you a lot about where things are. The peek pushes the terminal down off screen, it doesn't resize it, so it doesn't force any weird reflow or anything either. There's a lot more to talk about, especially about how this interacts with how we expose what needs attention so you can easily find the terminals/sessions/etc. that require your attention. Of course, you'll be able to drive this with the keyboard too. :) As always, a disclaimer: this is all early work subject to change, just trying to share some of what we're building in public. A lot of the UI experiential design is almonk so follow him for more updates too!

Mitchell Hashimoto

345,987 次观看 • 11 天前

Hello artists, I have a problem! I'm looking for a way to fix this issue in Clip Studio Paint: As you can see in the video, my shadow layer is clipped to my base color layer, but it's still stretching the color to the edges of the base color. I've tried looking for an option or something to fix this, but haven't found anything. I've changed my brush settings, created a new brush, etc., but nothing works. I went back to Paint Tool SAI and saw that when I make a selection, it doesn't do this in Paint Tool SAI. So I tried it in Clip Studio Paint, and unfortunately, the problem persists. It spreads the color to the selection edges where Paint Tool SAI doesn't. If anyone has a solution, a better-programmed brush, an add-on, or anything that can fix this problem, I would be very grateful!

Hello artists, I have a problem! I'm looking for a way to fix this issue in Clip Studio Paint: As you can see in the video, my shadow layer is clipped to my base color layer, but it's still stretching the color to the edges of the base color. I've tried looking for an option or something to fix this, but haven't found anything. I've changed my brush settings, created a new brush, etc., but nothing works. I went back to Paint Tool SAI and saw that when I make a selection, it doesn't do this in Paint Tool SAI. So I tried it in Clip Studio Paint, and unfortunately, the problem persists. It spreads the color to the selection edges where Paint Tool SAI doesn't. If anyone has a solution, a better-programmed brush, an add-on, or anything that can fix this problem, I would be very grateful!

Aniu

51,316 次观看 • 9 个月前

Officially moving on from Tech game after I get this thought off my chest. I more than welcome anyone smarter than me in regards to the football to chime in. I truly, truly, truly cannot wrap my head around the thought process here. These two plays I'm sure anyone with brain can agree officially sealed KU's slim chances in having a chance to win this game. The play calling to me seems like completely flipped in logic at best? First one, you are down 4, on your own 30 so you are not going to go for this. Ignoring that we were getting dominated in the trenches in this game and that the 'obvious' play is a run, I don't get why we make the decision in a must get spot to take the ball out of our QB's (who at the time was rolling) hands. Jalon Daniels is our best player. In an absolute must get/need, we should be relying on him to make a play. Then the second one. I obviously don't know the answer here, but I feel somewhat confident that the reason we didn't run here was because of how the earlier 3rd & 1 run went. While I don't necessarily agree with the premise of decision making on this alone, I can appreciate the recognition that we are going to struggle to gain a yard in an obvious run situation. But the thing is, we are in go for it range so the one thing you absolutely cannot have is a massive negative play. Literally anything else is okay (obviously not a turnover). I truly don't think there's a good chance we run the ball on this attempt and get a yard. But THIS situation gives you a free shot at it if you want to take it. I think this play call would have worked if we didn't let their best player run at our qb freely but I'd just argue this play had a ton of potential risk that wasn't necessary. Hell even a play action pass out of out shot gun or something rolling JD out to the left would have given us a good shot at first down with an escape route to bail out on the play if something went wrong. I'm once again for the millionth time saying I know and understand that this entire staff knows more about football in their pinky than I do. But I do think the game has evolved and game + clock management doesn't really require football knowledge/have a direct correlation to one's football knowledge. It's not as simple as ESPN's graphic says GO so you should go etc, there are variables and human behavior etc to deal with and I understand that. But we are just getting these situations downright wrong. We are flipping a coin that has a 20 pound weight attached to the heads side and calling tails almost every single time. S/O anyone who read all this but would just love some insight if there's anyone who disagrees and is a lot smarter than I!

Officially moving on from Tech game after I get this thought off my chest. I more than welcome anyone smarter than me in regards to the football to chime in. I truly, truly, truly cannot wrap my head around the thought process here. These two plays I'm sure anyone with brain can agree officially sealed KU's slim chances in having a chance to win this game. The play calling to me seems like completely flipped in logic at best? First one, you are down 4, on your own 30 so you are not going to go for this. Ignoring that we were getting dominated in the trenches in this game and that the 'obvious' play is a run, I don't get why we make the decision in a must get spot to take the ball out of our QB's (who at the time was rolling) hands. Jalon Daniels is our best player. In an absolute must get/need, we should be relying on him to make a play. Then the second one. I obviously don't know the answer here, but I feel somewhat confident that the reason we didn't run here was because of how the earlier 3rd & 1 run went. While I don't necessarily agree with the premise of decision making on this alone, I can appreciate the recognition that we are going to struggle to gain a yard in an obvious run situation. But the thing is, we are in go for it range so the one thing you absolutely cannot have is a massive negative play. Literally anything else is okay (obviously not a turnover). I truly don't think there's a good chance we run the ball on this attempt and get a yard. But THIS situation gives you a free shot at it if you want to take it. I think this play call would have worked if we didn't let their best player run at our qb freely but I'd just argue this play had a ton of potential risk that wasn't necessary. Hell even a play action pass out of out shot gun or something rolling JD out to the left would have given us a good shot at first down with an escape route to bail out on the play if something went wrong. I'm once again for the millionth time saying I know and understand that this entire staff knows more about football in their pinky than I do. But I do think the game has evolved and game + clock management doesn't really require football knowledge/have a direct correlation to one's football knowledge. It's not as simple as ESPN's graphic says GO so you should go etc, there are variables and human behavior etc to deal with and I understand that. But we are just getting these situations downright wrong. We are flipping a coin that has a 20 pound weight attached to the heads side and calling tails almost every single time. S/O anyone who read all this but would just love some insight if there's anyone who disagrees and is a lot smarter than I!

Bryson Stricker

33,876 次观看 • 10 个月前

This is Bertha - and this is exactly the situation I have been struggling with. She was my first cow purchase. Bought her as a milk cow and then soon learned she was mostly past time for being a good milk cow. She’s about 14 or 15 years old. Still gives a calf each year but her time for a natural end is coming quickly. Many would take her to the sale barn, receive some money for her. It’s difficult to explain but that feels wrong - it’s not, but it feels terrible. So at this point she will likely live her life out here, she’ll serve as a lead cow (she’s really not great for that either), but she will do okay. She means a lot to me and I just don’t want to think of her at auction or otherwise being transported somewhere away from this farm. So for now, and likely until her very end, she remains here.

This is Bertha - and this is exactly the situation I have been struggling with. She was my first cow purchase. Bought her as a milk cow and then soon learned she was mostly past time for being a good milk cow. She’s about 14 or 15 years old. Still gives a calf each year but her time for a natural end is coming quickly. Many would take her to the sale barn, receive some money for her. It’s difficult to explain but that feels wrong - it’s not, but it feels terrible. So at this point she will likely live her life out here, she’ll serve as a lead cow (she’s really not great for that either), but she will do okay. She means a lot to me and I just don’t want to think of her at auction or otherwise being transported somewhere away from this farm. So for now, and likely until her very end, she remains here.

Mathew with Cottage Pastures

2,103,549 次观看 • 5 个月前

Samsung's One UI 8 for the Galaxy S25 Ultra has added a new feature—the adaptive lock screen clock. The principle is that when an object's outline is detected, the clock automatically extends or contracts to adapt to the shape. Actually, Samsung could have easily achieved a depth effect without the need for this elastic adjustment. But now you know why they didn’t—because this trend was pioneered by Apple. Samsung wants to create its own distinctive feature. While everyone else follows Apple’s lead with depth-effect clocks, Samsung opts for a transforming clock, deliberately choosing to stand out.

Samsung's One UI 8 for the Galaxy S25 Ultra has added a new feature—the adaptive lock screen clock. The principle is that when an object's outline is detected, the clock automatically extends or contracts to adapt to the shape. Actually, Samsung could have easily achieved a depth effect without the need for this elastic adjustment. But now you know why they didn’t—because this trend was pioneered by Apple. Samsung wants to create its own distinctive feature. While everyone else follows Apple’s lead with depth-effect clocks, Samsung opts for a transforming clock, deliberately choosing to stand out.

Ice Universe

194,533 次观看 • 1 年前

Mike Vrabel on coaching against his former team this upcoming Sunday: “…Think I’d file it under the category of, is it interesting or important? And I would probably say this would be very interesting, but in the end not very important to our preparation or what we need to continue to try do to improve as a team. “But having spent 6-7 years there, I think it’ll be nice to see some people that I haven’t seen in a few years that helped us win, players and staff. But we’ve got a huge job here to do as we prepare for them.” WEEI #NEPats

Mike Vrabel on coaching against his former team this upcoming Sunday: “…Think I’d file it under the category of, is it interesting or important? And I would probably say this would be very interesting, but in the end not very important to our preparation or what we need to continue to try do to improve as a team. “But having spent 6-7 years there, I think it’ll be nice to see some people that I haven’t seen in a few years that helped us win, players and staff. But we’ve got a huge job here to do as we prepare for them.” WEEI #NEPats

Tom Carroll

219,843 次观看 • 10 个月前

While I have premium I definitely want to do a long post breaking down the main scene from this show that I obsess with. There's so much that I feel could be learned from it. Not just for expansion animators either. There's honestly a LOT that can be learned from how this show directed its expansion scenes that can be applied to even safe for work animations. Obviously yes, the expansion alone is really good. What makes it so good though is just the fact that there's things you pick up on that you likely don't even realize until you re-watch. I'm using this scene as an example as it's not AS good I would say, but it still has a lot going for it. One thing I've always loved from it that I want to use in my own animations someday is that the expansion sort of comes in waves as opposed to one consistent growth. In a way, it makes it feel more natural while also selling how tight the top is getting. It could have been accompanied by showing the knot getting tighter or smaller with each growth. It's a small part of the animation but just that one thing already adds another layer to appreciate. It's not like most expansion scenes where there's very little outside of just "growing" on its own. There's a bunch of little things that subtly improve it without being obnoxious. The first expansion scene has WAY more that I want to talk about honestly. Far more than this one has. It will probably be a really long post now that I think about it...

While I have premium I definitely want to do a long post breaking down the main scene from this show that I obsess with. There's so much that I feel could be learned from it. Not just for expansion animators either. There's honestly a LOT that can be learned from how this show directed its expansion scenes that can be applied to even safe for work animations. Obviously yes, the expansion alone is really good. What makes it so good though is just the fact that there's things you pick up on that you likely don't even realize until you re-watch. I'm using this scene as an example as it's not AS good I would say, but it still has a lot going for it. One thing I've always loved from it that I want to use in my own animations someday is that the expansion sort of comes in waves as opposed to one consistent growth. In a way, it makes it feel more natural while also selling how tight the top is getting. It could have been accompanied by showing the knot getting tighter or smaller with each growth. It's a small part of the animation but just that one thing already adds another layer to appreciate. It's not like most expansion scenes where there's very little outside of just "growing" on its own. There's a bunch of little things that subtly improve it without being obnoxious. The first expansion scene has WAY more that I want to talk about honestly. Far more than this one has. It will probably be a really long post now that I think about it...

FancyPlanks 🐀

16,420 次观看 • 8 个月前