Loading video...

Video Failed to Load

Go Home

This simple trick will make your Livewire apps 10x faster with zero JavaScript 🏎️💨 Whenever you have a selectable element, you might be tempted to write something like this in your classes: {{ $selected ? ‘bg-blue-500’ : ‘’ }} This is very slow, that class will only get added...

26,151 views • 1 year ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Today’s TikTok tip : Setting up your phone I’ll continue from where I stoped yesterday When setting up a new phone , when you get to the screen where you are asked to enter your Apple ID Don’t ever enter an Apple ID that has been used to formerly create an account before , you are likely to get banned if you create TikTok from it Tap on create a new Apple ID , if it proceeds to the next screen , you are safe , if it does not , you will get a message that you can’t create Apple ID, this happens when you have used the phone to create too many Apple ID Just leave the phone for a month and come back to it or get a new phone For the first name and last name , i use the name of my account that I want to name Also when creating passwords , don’t use the password that consist of any of the names you added , it won’t work, I don’t know why After that enter your email address, don’t use a spam email or an email with + somerhing , Apple knows how to catch this well, you want to use a fresh email address , for this I use some of the emails I have already instead , we will use this email to verify the phone later Now to the phone number side , for numbers, purchase as from juicysms and smspva for Apple number purchase , tried some other ones before but you just need a disposable number for this to verify that Apple account that’s all. By now if you follow this guide you will be able to setup your phone I’ll continue tomorrow , I’ll talk more about candy crush game in the iPhone setup, it’s one trick I learnt 🤣🤣🤣🤣 Feel free to ask any questions

Pixel_builder

11,338 views • 3 months ago

Apparently, I saw this video online and I decided to share. What this worker is applying is called bitumen, or what many of us know as bituminous coating. Most people think a wall is a solid, impenetrable block, but in reality, it is more like a sponge. Concrete and blocks have microscopic pores that pull water from the earth through a process we call capillary action. This thick black substance is the shield that stops that water from climbing up into the house. It is not about making the wall look good because this part will be buried under the dirt forever. It is about creating a skin that water cannot breathe through. When do you need to do this? The need for this arises because the soil is a very aggressive environment. Water is not your only enemy.. The ground also contains salts and sulfates that want to eat away at the cement. If this moisture finds its way to the steel bars inside the columns, those bars will start to rust. And when steel rusts, it expands, and that expansion is what cracks the concrete from the inside out. This coating is the only thing standing between your foundation and that kind of slow destruction. Thats is why if you see wet patches at the bottom of your walls inside your house, it usually means someone skipped this step or did it poorly during construction. You can apply this anytime you are building parts of a structure that will stay in contact with the ground. It is common in areas where the water table is high or where the soil stays damp for most of the year. This is a one-shot opportunity. Once you backfill the soil, you can never go back to fix it without a lot of expense and a lot of digging. It is about having the foresight to protect the heart of the building while it is still exposed. Please don’t ignore this if you need to. If you ignore it now to save a bit of money, you will be funding the future decay of your own home. I hope this helps.

A.Y.O

75,399 views • 5 months ago

this is the worst local ai will ever be. it only gets better from here. if you are not expanding your mind with these small models you are missing what's happening right now 99 percent tool call success rate. when steered well with the right skills and a framework like hermes agent the node becomes a cognition layer. not a chatbot. not a toy. an extension of how you think. i was cranking this node at 35 to 50 tok/s all day on personal experiments and now after all the work is done qwen 3.5 9B is iterating on its own code. the game it created. fixing its own bugs autonomously. and the part you should probably not miss is that all of this is happening on a RTX 3060. not an H100. not an A100. the card most of you have sitting in a drawer right now. if you just open that drawer and put that intelligence to work every tensor core on that card should be running for you. your work. your experiments. your thinking. you all have it but because nobody told you what this hardware can actually do in 2026 you never tried. the day it unlocks is the day you test your workload, understand the tradeoffs, debug the loops, and then decide if you need to scale the hardware. there is no point buying 3 mac studios when things done well you can squeeze a similar level of intelligence from 9B compared to 70B. but only when you create the right environment for your model through the right harness. and let me tell you i have tried claude code as a local harness. i have tried opencode. i have tried various others. somehow i landed on hermes agent and never left. there is something magical going on at Nous Research. the tool call parsers, the skills system, the way it handles small models natively. nothing else comes close for local inference. own your cognition. your AI. your agent. your prompts. your experiments. why give them away for free. those are who you are and they don't belong on someone else's servers being monitored. just give it a shot with your existing hardware. you run into a problem the community will help you. and if you are migrating from openclaw to hermes i will personally help you make the switch.

Sudo su

58,717 views • 6 months ago

The gold standard fluid interactions on iOS are built using in-process client animations (like SwiftUI does it) and not render-server animations (like CoreAnimation does it). This is common knowledge inside of Apple’s UI framework and system experience teams. A close inspection of iOS’s evolution reveals the gradual upgrading of system experiences written using render-server animations (that often disable user interaction) with ones using client animations (that are interruptible and interactive). The app switcher for iPhone X, the Dynamic Island, and Liquid Glass bars are prime examples of this trend. The other thing that makes these experiences feel so fluid is their use of spring animations that preserve velocity, rather than Bézier curve easing functions. To get velocity preservation, you need to be able to interrupt a spring animation and retarget it or drive it with a gesture. That’s a lot easier to do when the animation is running in the same process as the event handling. When we were first pitching SwiftUI, two of our go-to demos were a recreation of the iOS 9 navigation and Home Screen interactions which were fully interactive and interruptible, at a time when the actual implementations of those experiences in the OS disabled user interaction and ran server-side animations. CoreAnimation is great and the framework does much more than animation. You can build a fine app using its server-side animations. But if your UI framework can’t do efficient main thread client animations, there’s a ceiling to the quality of the experience your app can provide.

Kyle Macomber

192,621 views • 12 days ago