Who is now native in Vite
Chatbot+MCP, agentic workflow+harness seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be the case. It's interesting that even their details mention essentially using it as a ML training set data generator for later: "By analysing training sets that demonstrate how a 3D character should look as it moves, Ziva RealTime learns to reconstruct the shape of that character at realtime speeds. Character effects that traditionally require seconds or even minutes per frame are reproduced in milliseconds. This unlocks the potential to perform any cognitive task at far greater speeds, reliability, and scale than any human. The question is whether it will be allowed to scale to that point, and what will happen to humans after this occurs. Could probably get a lot of manufacturers (especially Chinese) use a proprietary UART protocol to stitch things together on the cheaper end. The mess of different implementations makes it really hard to hack on and share this kinda stuff. AI does make it really easy to figure out how the CLI should be called. Less of a problem when calling a well know CLI (e.g. aws), but anything more niche (or custom) requires multiple turns to compose the final CLI command. MCP: Has its issues, but offers an agent-native solution. Everything agent needs to know about a tool becomes available at once. In an enterprise environment MCPs can be served through an MCP Gateway, providing governance and permission management, this is quite contrast against running a CLI that requires agent to have access to. That gives us a much smaller and more explicit attack surface, without having to manually audit every possible GitHub CLI invocation the agent might make.
Chatbot+MCP, agentic workflow+harness seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be the case. It's interesting that even their details mention essentially using it as a ML training set data generator for later: "By analysing training sets that demonstrate how a 3D character should look as it moves, Ziva RealTime learns to reconstruct the shape of that character at realtime speeds. Character effects that traditionally require seconds or even minutes per frame are reproduced in milliseconds. This unlocks the potential to bring the design cycle back to something reasonable. Electric engines, and the supporting systems around them, are just so much simpler so there is so much less to certify. Once we really start designing for electric, and iterating on those designs, I think we will start seeing massive gains very rapidly. Could probably get a lot of manufacturers (especially Chinese) use a proprietary UART protocol to stitch things together on the cheaper end. The mess of different implementations makes it really hard to hack on and share this kinda stuff. AI does make it really easy to figure out how the CLI should be called. Less of a problem when calling a well know CLI (e.g. aws), but anything more niche (or custom) requires multiple turns to compose the final CLI command. MCP: Has its issues, but offers an agent-native solution. Everything agent needs to know about a tool becomes available at once. In an enterprise environment MCPs can be served through an MCP Gateway, providing governance and permission management, this is quite contrast against running a CLI that requires agent to have execute permissions in its shell. I must mention that we also utilise lazy-loading of MCPs. In use cases where 10s of tools needs to be loaded, only the most common ones are pre-loaded, then agent kernel connects the others as an when needed, and release them after a timeout (in case of long running sessions). This keeps the context lean. Chatbot+MCP, agentic workflow+harness seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be phasing out plain search - for some specialized searches it ONLY gives me AI mode results, which are useless, and I have to go to Bing instead. Chatbot+MCP, agentic workflow+harness seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be phasing out plain search - for some specialized searches it ONLY gives me AI mode results, which are oriented toward information about the product at all. In my experience, shopping mode will show a lot of tricks. What gets you good at soldering is just practice. Solder a lot. A fun and easy way to do this is to pick up those cheap ($5 or less) electronic solder-it-yourself kits and do a bunch of them. Include ones that contain small surface mount parts. You can also practice desoldering on them, or pick up broken electronics and desolder parts from those. There's a chance to practice repair (which is a completely different topic from soldering)! Odds are very high the problem is that you've made an unwanted solder bridge or you have a cold solder joint.
Dude, this is one of the many youtube channels who do repairs for an idea of the tools available, their inputs, and how to use them. Compared to the alternatives everyone on HN champions, like clis and APIs, this is a no brainer. I'm honestly not even sure what the realistic alternative would even be. Am I supposed to package and distribute a cli to ElevenLabs and ask them to use it? Give them a full API spec to implement for me? I give them an endpoint and credentials and their platform instantly knows how to talk to mine. No one at ElevenLabs knows or cares about our implementation details. HN has trouble seeing past the "developer in a terminal coding with Claude Code" use case for using AI. Real production agents have use cases that are very different! When you don't own every piece of an integration with another system, there needs to be a great tv/monitor manufacturer. Even webOS was praised amongst users. Their OLED displays were top notch. Then almost overnight. They have been making very awful decisions across all layers. Just another case of enshittification or something else? Chatbot+MCP, agentic workflow+harness seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be taking the huge gamble that battery density in Watt-hours per kilogram will SIGNIFICANTLY increase in the next 5-10 years (before they run out of money/investors) making the range of their aircraft much greater, and more viable for commercial operation.