I was reading GitLab's recent statements around agentic software engineering, and one quote really stood out: "Git itself is being reengineered for machine scale." ( Business Insider ) According to GitLab, future software development will involve AI agents that: plan, code, review, deploy, and repair software, with humans providing oversight and architectural judgment. ( Business Insider ) That got me thinking. There has been projects for some time arguing that AI agents shouldn't simply be treated as better autocomplete systems . Instead, they argued that agents should become first-class participants in software development : with their own identities, their own branches, their own merge requests, their own audit trails, and infrastructure designed for machine-rate collaboration. One example is GitLawb , which has described itself as a kind of "Git for agents." At the time, a lot of people dismissed these ideas as unnecessary or overly ambitious. But now GitLab—a multi-billion-dollar DevSecOps company—is talking about: agent-specific APIs, machine-scale Git infrastructure, orchestration layers coordinating agents, and agents acting as first-class users of development platforms. ( Business Insider ) It does raise an interesting question: Was the underlying thesis correct all along? We've seen similar patterns before: Containers existed before Kubernetes became the standard. Electric vehicle startups pushed ideas that incumbents later adopted. Cloud-native companies advocated architectures that the rest of the industry eventually embraced. The original innovators don't always dominate the market. But when major incumbents begin rebuilding around similar assumptions, it often suggests that the problem itself is real . So I'm curious what this community thinks: Do AI agents require an entirely new layer of collaboration infrastructure? Or will existing platforms simply evolve enough to absorb these workflows? Because if GitLab is right, software development may be tran

Fusion power startup Avalanche Energy said its reactor prototype heated a plasma to over 10 million degrees C.

What device do we use almost all the time? Our mobile phone, almost certainly. If we wanted to...

This is today’s edition of The Download, our weekday newsletter that provides a daily dose of what’s going on in the world of technology. The “steroid olympics” were a circus—and a window into our culture —Amit Katwala A couple of weeks ago, at a $50 million arena built in a casino parking lot in Las…

submitted by /u/Sumsub_Insights [link] [留言]

Adi Polak discusses the architecture required to transition from stateless prompts to state-aware, context-rich AI agents. Drawing on 15 years in distributed systems, she shares how engineering leaders can leverage Apache Kafka and Flink for real-time stream processing, dynamic memory tiering, and tool orchestration via MCP to solve token limits, cost spikes, and latency bottlenecks. By Adi Polak

A new report from OpenAI details PRC-linked influence operations using AI to target U.S. tech debates, data center narratives, tariffs, and false claims about ChatGPT.

I have been an audio reviewer for 20 years. My time as a freelance headphones panelist at Wirecutter, and the multitude of reviews I’ve written for sites like Reviewed, Digital Trends, IGN, and now The Verge, have given me the chance to listen to hundreds of earbuds. Some were truly excellent, and some were pretty […]

Ambrosia Energy wants to build power plants in less than 12 months while undercutting natural gas. It hopes to build gigawatts worth by 2030.

Meta has to open up WhatsApp to third-party AI chatbots again, the European Commission says.

Turn Claude into a recruiter that thinks like you Discussion | Link

So if you missed it, 32 npm packages under u/redhat-cloud-services got compromised last week. about 117,000 weekly downloads. i know, another supply chain attack, we're all tired. but this one is different from the usual "remove the package and move on" cleanup, which is why i'm posting. The malware doesn't stay in the package. during install it copies itself into your editor config. it adds a startup hook to ~/.claude/settings.json (runs every time you open Claude Code) and a task to .vscode/tasks.json (runs every time you open that project in VS Code). so you can delete the package, nuke node_modules, reinstall everything clean, and the attacker's code still runs every time you open your editor. uninstalling removes nothing. While it runs, it grabs every credential on your machine. AWS keys, Google Cloud, Azure, Kubernetes secrets, SSH keys, GitHub tokens, npm tokens. it checks whether you're running CrowdStrike or SentinelOne first, so it can stay quiet on monitored machines. It installs a small watchdog that pings GitHub with the stolen token every minute or so. if you revoke that token before removing the malware, the watchdog notices and wipes your entire home directory. overwrites the files so they can't be recovered. The advice, "rotate everything immediately" is exactly what triggers it. the attacker built it that way so you hesitate before kicking them out. cleanup steps in the right order are at the bottom. Three days later a second wave hit 57 more packages, around 647,000 monthly downloads. this one moved the malicious code into binding.gyp, a build config file that node-gyp executes during install. that means no preinstall or postinstall script at all, --ignore-scripts does not help you, and the scanners that caught the first wave missed this one. some malicious versions are still live on npm right now. and the worm spreads itself: it uses stolen npm tokens to publish poisoned versions of whatever packages that maintainer owns. Here's how the whole thi

Hi, How many rows have you ever tried to render on html via <table> ? I need maybe north of 300k rows on one page and want to know if the browser will die ? submitted by /u/Yha_Boiii [link] [留言]

Kit out your Apple tablet with our favorite stands, cases, keyboards, and styli.

Doctor Who's previously-announced Christmas special is no more as the BBC severs ties with Russell T. Davies and Bad Wolf.

Im investigating an idea i had about JSX for webcomponents after some experience with Lit. I am sharing this here because it might be interesting/educational for someone, if it isnt, let me know and i'll remove the post. Lit is a nice lightweight UI framework, but i didnt like that it was using class-based components. Vue has a nice approach but i prefer working with the syntax that React uses. I find it more intuitive for debugging and deterministic rendering. I wondered if with webcomponents, i could create a UI framework that didnt need to be transpiled. Read the docs Checkout the code Storybook demo (My intentions with this framework is to get to a reasonable level of stability, to then replace React on some of my existing projects.) IMPORTANT: Im not trying to promote "yet another ui framework", this is an investigation to see what is possible. You should not use this framework in your own code. It is not production-ready. It is not on NPM. Im not looking for another framework to replace React (im trying to create it). This framework is intended for myself on my own projects. This project is far from finished. Feel free to reach out for clarity if you have any questions. submitted by /u/Accurate-Screen8774 [link] [留言]