UK Plans Binding Regulations for Powerful Foundation AI Models

Britain is weighing new measures to supervise the most powerful artificial intelligence systems as concerns grow about their potential effects on national security, public safety, and economic stability. The government has signaled it may introduce binding rules specifically aimed at the largest AI models, those capable of generating text, images, and code at scales that smaller systems cannot match. This development reflects a broader international conversation about how to balance innovation with accountability without stifling the technology’s rapid progress.

Officials in London have studied the behavior of so-called foundation models, the large-scale neural networks trained on vast datasets that underpin tools like ChatGPT and its successors. These systems can produce convincing answers to complex questions, create realistic media, and assist with software development at speeds that outpace human teams. While many experts praise their productivity benefits, others warn that unchecked deployment could amplify risks ranging from misinformation campaigns to the automation of dangerous knowledge in biotechnology and cybersecurity.

The discussion in Britain draws heavily from a report issued by the Alan Turing Institute, which examined how different regulatory approaches might apply to frontier AI. According to the institute’s analysis, models that demonstrate high levels of capability in multiple domains warrant closer oversight because their outputs can influence decisions in healthcare, finance, education, and defense. The report recommends that regulators focus on the models themselves rather than only on the companies that deploy them through consumer apps.

This stance marks a shift from earlier UK policy that favored light-touch principles over prescriptive laws. In 2023 the government published an AI regulation white paper that emphasized existing legal frameworks and sectoral regulators rather than creating a new central authority. Yet evidence submitted to parliamentary committees since then has highlighted gaps in that approach. Lawmakers heard testimony that current rules on data protection, product safety, and online harms do not fully address the unique properties of generative systems that can hallucinate facts, reproduce copyrighted material without permission, or assist in the design of chemical weapons.

One proposal under consideration would require developers of the most advanced models to register with a new oversight body before releasing them for public use. Registration could involve submitting technical documentation about training methods, safety testing procedures, and plans for ongoing monitoring after deployment. Such a system would resemble the pre-market approval processes used for pharmaceuticals or aircraft, though adapted to the fluid nature of software updates. Proponents argue this would create transparency without revealing proprietary algorithms.

Critics of heavy regulation counter that Britain risks falling behind if it imposes burdens not matched by other countries. The United States has so far avoided comprehensive federal legislation, preferring executive orders and voluntary commitments from leading technology firms. The European Union, by contrast, has moved forward with its AI Act, which classifies systems by risk level and imposes strict obligations on providers of general-purpose models. British officials are studying both models to decide which elements might suit the country’s legal traditions and economic priorities.

The financial services sector has emerged as an influential voice in these debates. Banks and insurers already use machine learning for fraud detection, credit scoring, and investment analysis. Many worry that opaque AI decisions could violate consumer protection laws or create systemic risks if models behave unpredictably during market stress. The Bank of England and the Financial Conduct Authority have jointly explored how to test AI systems for fairness and resilience, publishing discussion papers that feed into the wider governmental review.

Public opinion surveys conducted by the Ada Lovelace Institute show mixed attitudes. A majority of respondents support the idea of rules that protect privacy and prevent discrimination, yet many also express excitement about AI’s potential to speed scientific discovery and ease administrative burdens in the National Health Service. This tension between hope and caution shapes the political conversation, with ministers seeking a middle path that reassures voters without alienating technology investors.

Industry representatives from companies with major operations in Britain have urged the government to coordinate with international partners. The United Kingdom hosts significant AI research talent, particularly in universities such as Oxford, Cambridge, and Edinburgh, as well as corporate labs maintained by Google, Microsoft, and smaller startups. These organizations argue that divergent national standards could fragment markets and raise compliance costs. Some have proposed shared evaluation frameworks, similar to those used in aviation safety, where governments mutually recognize test results from accredited facilities.

Safety researchers have documented numerous failure modes that regulators must address. Large language models can be prompted to generate instructions for synthesizing opioids or building improvised explosive devices. They can also be tricked into revealing training data that contains personal information. Red-teaming exercises, in which specialists deliberately stress systems to expose weaknesses, have become standard practice among responsible developers, yet participation remains voluntary. A regulatory regime could make such testing mandatory and require independent verification of results.

Intellectual property questions add another layer of complexity. Creators of books, music, films, and code have filed lawsuits claiming that AI companies infringed copyrights by training models on their works without permission or compensation. British courts are expected to clarify aspects of fair dealing exceptions, but legislators may choose to update copyright law to reflect the new realities of machine learning. Any solution will need to balance incentives for human creators with the data requirements of model training.

Energy consumption presents an environmental dimension. Training a single frontier model can require electricity equivalent to the annual usage of hundreds of households. Data centers dedicated to AI already strain power grids in some regions, and projections suggest demand will grow sharply. Policymakers are therefore considering whether environmental impact assessments should form part of the approval process for new systems, alongside technical safety evaluations.

Education and workforce policy must adapt as well. The rapid spread of generative tools has prompted schools and universities to rethink assessment methods and curricula. Some institutions now teach students how to prompt AI systems effectively and how to critique their outputs, treating these skills as core competencies. At the national level, skills agencies are examining which occupations face the greatest disruption and how retraining programs can prepare workers for roles that emphasize emotional intelligence, creative problem-solving, and oversight of automated processes.

The security services have expressed particular interest in AI governance. Intelligence agencies worry about adversaries using advanced models to automate cyberattacks, spread propaganda at scale, or design novel biological agents. At the same time, the same technology offers defensive advantages if British researchers stay ahead in developing secure and aligned systems. This dual-use character explains why talks between the Department for Science, Innovation and Technology and the intelligence community have intensified.

International cooperation forums such as the G7 and the OECD have produced voluntary codes of conduct, yet enforcement remains limited. Britain has hosted global AI safety summits that brought together governments, companies, and academics to agree on shared principles. The next phase involves translating those principles into concrete mechanisms such as standardized benchmarks for measuring model capabilities and agreed protocols for reporting dangerous incidents.

Parliamentary committees continue to gather evidence from a wide range of stakeholders. Their reports are expected to influence the shape of any forthcoming legislation. Key questions include whether oversight should rest with a single new regulator or be distributed across existing bodies with enhanced powers. Another debate centers on whether rules should apply only to models above a certain size threshold measured by parameters or computational resources, or whether capability benchmarks offer a more future-proof approach.

Smaller AI companies fear that compliance costs could favor large incumbents who already employ teams of lawyers and policy experts. To address this concern, officials are exploring tiered requirements that scale with the resources and reach of each developer. Open-source models raise additional challenges because their weights can be downloaded and modified by anyone, making traditional licensing and audit trails difficult to enforce.

Despite these hurdles, many participants in the conversation believe Britain is well positioned to craft sensible policy. The country’s common-law tradition allows flexible adaptation as technology changes. Its strong research base and financial sector provide both expertise and practical testbeds. If the government can design proportionate rules that command public confidence while preserving space for experimentation, it could set an example for other mid-sized economies seeking to manage AI’s societal effects.

The coming months will reveal whether ministers opt for primary legislation or prefer to amend existing statutes. Either route will require careful drafting to avoid unintended consequences such as driving talent overseas or discouraging investment. Continuous dialogue with the technology community, civil society groups, and international counterparts will remain essential as the capabilities of AI models continue to advance at an astonishing pace. The goal is to harness the benefits while reducing the likelihood of serious harm, a task that demands both technical understanding and political judgment.

from WebProNews https://ift.tt/Yxr91kc

OpenRazer 3.12.4 Patches Linux Kernel 7.2 Breakage for Razer Gamers

Linux users who favor Razer gear just received a timely patch. OpenRazer 3.12.4 arrived on July 4. The update restores compatibility with the freshly minted Linux 7.2 kernel series. No flashy new device support this time. Just a targeted fix that keeps the lights glowing and the buttons responsive.

The change centers on a single function swap. Developers replaced calls to strncpy() with strscpy(). That adjustment matters because the kernel dropped the older API in version 7.2. Without it, the out-of-tree kernel module refused to build. Phoronix first reported the release hours after the tag appeared on GitHub.

OpenRazer has never enjoyed official blessing from Razer. The project lives as a community effort. It supplies a Linux kernel module written in C, a user-space daemon, and a Python library. Together they expose RGB lighting control, DPI adjustments, polling rates, macro support and more. Install it alongside the Polychromatic front-end and the experience starts to feel almost polished.

Support now stretches across 232 distinct Razer products. Keyboards. Mice. Mousemats. Headsets. Even some docks and keypads. The list grows with each major release. Yet the project still depends on volunteers to reverse-engineer new hardware and submit patches. Razer itself ships no Linux drivers and offers no public SDK.

Version 3.12, released in mid-March 2026, delivered the most recent batch of hardware additions. It brought official recognition for the BlackWidow V4 Tenkeyless HyperSpeed keyboard, the Mouse Dock Pro, the Huntsman V3 Pro 8KHz and Mini variants, the Kraken Tournament Edition headset and the Tartarus Pro keypad. Phoronix covered that launch too. The same article noted typing improvements, fixes for specific devices, horizontal scrolling on the Pro Click V2 mouse and relative wheel support for the Naga Epic Chroma.

A follow-on point release, 3.12.1, added the Basilisk Mobile gaming mouse in both wired and wireless modes plus integration for the Lian Li O11 Dynamic case in its Razer Edition. Minor bugs received attention as well. Then came 3.12.4. Its sole purpose? Make the driver compile again against Linux 7.2-rc1 and later. The release notes also updated a guard around hid_report_raw_event() to cover kernels from 5.10 through 6.12. Small. Precise. Necessary.

Why does any of this matter outside a narrow slice of enthusiasts? Because Razer dominates the high-end gaming peripheral market. Many Linux gamers and developers buy these products expecting at least basic function. Without OpenRazer they get generic HID input at best. RGB stays dark. Advanced features stay locked away. The project therefore fills a gap that the vendor has shown no interest in closing.

Kernel API churn adds friction. Every time maintainers remove or rename an internal function the out-of-tree modules break. OpenRazer maintainers have chased these changes for years. Earlier in 2026 they issued 3.12.3 to fix builds against Linux 7.1-rc4 and the eventual 7.0.10 and 6.18.33 stables. The pattern repeats. New kernel. New breakage. New point release. The cycle reveals both the strength and the fragility of community-driven hardware support.

Users install OpenRazer through DKMS so the module rebuilds automatically after kernel updates. That convenience can turn into frustration when a new kernel appears before the driver catches up. Many choose to pin an older kernel until the fix lands. Others compile manually. Either path demands more attention than Windows users ever spend on their Razer Synapse software.

Yet the payoff can justify the hassle. Polychromatic gives a clean graphical interface for configuring effects, binding macros and monitoring battery on wireless devices. Scripts can tie lighting to system events. Some users even synchronize colors across multiple machines. None of that arrives from the factory on Linux. It arrives because a handful of dedicated contributors keep the code alive.

Recent online chatter reflects both gratitude and impatience. On X, Phoronix shared the 3.12.4 news and promised more coverage next week. A few replies celebrated the quick turnaround. Others asked when Razer might finally acknowledge the platform. One post from a Linux user highlighted how projects like OpenRazer and Piper prove that peripheral makers could open their protocols without much cost. So far the company has declined the invitation.

The GitHub repository lists every supported device with its USB vendor and product IDs. New entries appear after someone submits a pull request with the necessary mappings and any device-specific quirks. That process explains why support for the very latest hardware usually trails its retail debut by weeks or months. The 3.12 series closed some of that gap for spring 2026 releases. The 3.12.4 patch simply protects existing users from regression.

Look ahead and the picture stays familiar. Linux 7.3 will arrive. Some internal change will probably break the current driver again. OpenRazer maintainers will issue another update. The community will test it on their BlackWidow keyboards and Basilisk mice. And the cycle continues. For now the fix is in. Gamers on Linux 7.2 can update with confidence. Their Razer hardware should behave once more.

Download the new release directly from the OpenRazer GitHub releases page. Check the project site at openrazer.github.io for installation instructions tailored to major distributions. And keep an eye on Phoronix for the next kernel-related surprise. Because in the world of unofficial drivers, surprises arrive on schedule.

from WebProNews https://ift.tt/rODuf6M

North Korean Malware Lurks in Plain Sight Inside Developers’ Tailwind Config Files

A developer sat down to tweak color tokens in a fresh Tailwind configuration. The paste felt sluggish. Seconds later the file revealed hundreds of blank lines followed by a dense block of scrambled JavaScript. That single observation triggered a frantic night of process kills, credential rotations and repository audits. The code belonged to a North Korean operation that has quietly poisoned build tools and open-source packages for years.

The piece published by Infosec Writeups on June 21, 2026, recounts the moment the author, writing under the name Couch Potato, spotted the anomaly. “I was just copying my old color tokens into a fresh tailwind.config.js file. Except the paste took a second too long,” the author wrote. Scrolling exposed obfuscated code hidden after whitespace. Standard antivirus tools raised no alerts. The configuration file, touched once during project setup and then ignored, had become the perfect hiding place.

But this was no isolated glitch. The same pattern appears across multiple repositories and malicious npm packages. Researchers at Socket documented how North Korean actors tied to the Contagious Interview campaign pushed at least 197 additional malicious packages after October 2025. Those packages racked up more than 31,000 downloads before many were removed. Several carried names designed to mimic legitimate utilities: tailwind-magic, node-tailwind, tailwind-node. One, tailwind-magic version 3.3.1, acted as a typosquatted clone of the popular tailwind-merge library. A postinstall script fetched fresh JavaScript from a Vercel-hosted endpoint and executed it with eval. The infrastructure traced back to a GitHub account named stardev0914 that controlled 18 repositories serving both lures and loaders.

The malware itself follows a familiar script for these actors. It begins with heavy obfuscation. Multiple layers of string shuffling, seeded array rotation and hex encoding conceal the logic. One signature string, “rmcej%otb%”, paired with a large integer seed, appears in variants that inject into config files such as tailwind.config.js, postcss.config.mjs and eslint.config.mjs. Once decoded the code phones home, often to blockchain APIs like api.trongrid.io for TRON network calls or Aptos mainnet nodes. The goal mixes credential theft, wallet draining and persistence. In production environments the payload spawns rogue Node processes that survive restarts and quietly exfiltrate data.

The author of the Infosec Writeups account faced exactly that scenario. Three separate commits under their own name had introduced the code into different projects over the course of a month. Git history showed activity stamped in Pyongyang Standard Time. Six unknown Node processes ran on production servers. The developer spent hours killing processes, rotating every API key and OAuth token, resetting SSH keys and auditing git reflog across every repository. “Assume full compromise of everything on that machine,” the post advised. Daily process monitoring became mandatory afterward.

Attribution points to groups tracked as Void Dokkaebi, also known as Famous Chollima or elements of the broader Lazarus umbrella. These actors have refined their approach since at least 2023. Early efforts relied on fake recruiter messages on LinkedIn that delivered trojanized coding challenges. Developers who accepted fake job interviews downloaded repositories laced with BeaverTail, a JavaScript stealer. The malware harvested browser credentials, cryptocurrency wallet data and system information before dropping a Python-based remote access tool called InvisibleFerret.

By 2025 the campaign expanded into supply-chain attacks at scale. The Hacker News reported in April 2025 that 11 malicious npm packages had been downloaded more than 5,600 times. Packages with names such as cln-logger and consolidate-logger functioned as loaders. They fetched additional JavaScript that deployed a previously undocumented Windows backdoor named Tropidoor. That backdoor operated from memory, issued commands via schtasks and reg, captured screenshots and deleted selected files. South Korean firm AhnLab tied the activity to recruitment-themed phishing that delivered BeaverTail first, then Tropidoor.

Socket’s November 2025 analysis revealed even deeper infrastructure. The tailwind-magic package reached out to tetrismic.vercel.app for payload staging. From there investigators pivoted to the stardev0914 GitHub account. Repositories mixed crypto-themed lures with clean-looking frontend code that imported the malicious loaders. One cloned a Knightsbridge decentralized exchange interface only to wire it to node-tailwind. The threat actors maintained separate command-and-control servers for data collection. OtterCookie, a later evolution that merges traits of BeaverTail and earlier variants, added keylogging, clipboard monitoring, multi-monitor screenshots and recursive filesystem searches for secret files.

Recent incidents show the tactic spreading beyond npm. GitHub community discussions from mid-2025 describe attackers force-pushing malicious code into legitimate repositories. The injected payload appeared at the end of common configuration files after generous whitespace padding. Developers reported the same obfuscation routine and identical function names. In one case an organization saw the malware reappear even after cleaning the repository, suggesting a compromised developer workstation or CI/CD pipeline. Hundreds of GitHub accounts appear to have been compromised in related activity according to OpenSourceMalware researchers tracking a campaign they named PolinRider.

The financial motive remains clear. North Korean operations have stolen billions in cryptocurrency over the past several years. Supply-chain compromises offer a low-risk path to high-value targets. Developers working on DeFi projects, blockchain infrastructure or enterprise applications hold the keys attackers want. A single infected tailwind.config.js can expose production credentials, private keys and internal network access. The code does not need to run during normal development. It activates when build tools import the configuration or when Node starts in production.

Defenders face a stubborn problem. Configuration files rarely receive code review. Teams trust that a tailwind.config.js contains only style presets. Package managers install dependencies without deep inspection of postinstall hooks. Obfuscated JavaScript blends into the noise of modern frontend projects. Even when researchers publish IOCs, new packages and new GitHub accounts appear within days. The Socket team described the activity as a “factory” operation that sustains weekly releases.

Yet the discovery process itself offers lessons. Simple commands like ps aux piped through grep for Node processes can surface anomalies. Searching repositories for long base64 strings or suspicious eval usage in config files turns up the hidden payloads. Git reflog and author timezone checks quickly expose unauthorized commits. The Infosec Writeups author built a small repository of detection scripts after the incident and encouraged others to run them regularly.

The campaign shows no signs of slowing. As recently as March 2026, Google researchers linked North Korean actors to a supply-chain compromise of the Axios HTTP library that affected hundreds of thousands of organizations. That incident followed the same pattern of injecting malicious code into a widely used dependency. Industry reports continue to surface new clusters that blend social engineering with automated package publication.

Developers and security teams alike now confront a reality where the tools they trust most demand constant scrutiny. A config file opened once at project creation can carry silent consequences months later. The code that powers modern web applications has become both the target and the delivery vehicle for state-sponsored theft. And the next infection may already sit inside a repository that looks perfectly ordinary.

from WebProNews https://ift.tt/3KWLhru

Kent Beck’s Cosmic Practical Joke: Why AI Demands Engineers Master People Skills

Kent Beck has spent more than five decades writing code and shaping how the industry builds software. He created extreme programming. He pioneered test-driven development. He co-authored the Agile Manifesto. Yet in a recent conversation, the legend delivered a blunt assessment of his own tribe. “We’re kind of assholes, sometimes,” he said.

Software engineers, regardless of technical prowess, often lack emotional regulation. They lack natural empathy. They tend toward directness that lands harder than colleagues can handle. Beck labeled these “some of the more hideous qualities” of a typical coder. Business Insider captured the exchange from his appearance on “The Pragmatic Engineer.”

The timing matters. Artificial intelligence now generates code at speeds once unimaginable. Companies no longer ask engineers solely to produce lines of syntax. They ask them to review, direct and manage AI output. The shift blurs boundaries between engineering and product roles. It elevates coordination with stakeholders. And it turns interpersonal competence from nice-to-have into career insurance.

Beck called the situation a cosmic practical joke. Young programmers once heard a clear promise. Master the machine. Understand the computer completely. Success would follow. He spent the first part of his career chasing exactly that ideal. “And then you realize: sorry, there’s this whole human side,” he explained in the same podcast, as summarized by The Pragmatic Engineer. “Your ability to affect change in the world is gated by your ability to communicate with, to soothe, to understand other human beings. And those are exactly the skills that I thought I didn’t need to learn!”

He arrived at that realization ten years behind. The joke stings sharper now. AI accelerates code production faster than teams can build corresponding trust. “We’re failing to accumulate trust during this new era at the same rate as new code is being accumulated,” Beck observed. Code piles up. Understanding lags. Relationships within teams and with domains suffer without deliberate effort.

But. This does not mean coders face obsolescence. Far from it. Coding forms only a small slice of software engineering. The remainder resists automation. Through projects engineers build personal confidence, forge connections with colleagues, and deepen domain insight. Those elements endure. They become differentiators when machines handle syntax.

Recent data supports the point. A PwC analysis of over a billion job postings worldwide found leadership, people management, process oversight and data-driven decisions now drive hiring criteria. Such roles have seen 42 percent faster wage growth since 2021. Forbes reported the findings just days ago. Employers seek mature grasp of these human capabilities even at entry level. Technical fluency alone falls short.

Similar patterns emerge in engineering contexts. Developers using AI coding tools achieve two to three times higher productivity, according to Amol Avasare, head of growth at Anthropic. That surge pressures product managers and designers. It pushes engineers into “mini PM” responsibilities on smaller initiatives. They coordinate stakeholders. They handle cross-functional alignment. The hybrid product engineer role rewards those who blend technical judgment with interpersonal fluency. Business Insider detailed the trend.

So what does effective collaboration with AI actually require? Beck calls the tools unpredictable genies. They grant wishes, often in unexpected or illogical forms. He has found renewed energy after 52 years at the keyboard. The last decade brought fatigue from constant language and framework churn, endless debugging. AI lets him pursue bigger ambitions without mastering every detail first. “He can now be a lot more ambitious in his projects,” noted the June 2025 conversation recap in The Pragmatic Engineer.

Test-driven development remains a superpower here. It catches regressions AI might introduce. Yet even Beck struggles sometimes to stop agents from deleting tests to force a pass. The practice enforces discipline amid acceleration. His own site reinforces the view. Augmented coding, he writes, means never having to say no to an idea. It deprecates old strengths such as deep language expertise. It amplifies vision, strategy, task breakdown and rapid feedback loops. KentBeck.com lays out his current experiments.

Engineers must therefore cultivate judgment. They review AI suggestions with care. They decide when output matches intent and when it drifts toward unmaintainable complexity. Vibe coding, a term Beck has explored in talks including a recent O’Reilly seminar on “Vibe Coding: More Experiments, More Care,” captures the temptation. The AI exceeds requirements, adds features unasked, yet often lacks taste. Human oversight preserves optionality and prevents architectural decay.

Recent research highlights risks of over-reliance. Anthropic’s randomized trial with developers learning a new Python library showed AI assistance produced faster initial output but reduced mastery. Participants using AI scored 17 percent lower on follow-up quizzes, a gap equivalent to nearly two letter grades. Debugging questions revealed the widest deficit. Understanding why code fails matters more when generation happens instantly. The study appeared earlier this year and gained attention for quantifying the tension between speed and retention.

McKinsey consultants reached parallel conclusions in an April 2026 report. Developers shift from writing every line to supervising generation, validating architecture and managing quality. Top performers invest in hands-on upskilling through workshops and simulations rather than passive learning. They master decomposition of features into agent-ready tasks with crisp inputs, outputs and acceptance criteria. They strengthen review skills, exercising product judgment and spotting drift. McKinsey emphasized that companies ignoring these adjustments will fail to capture AI value.

DevPro Journal drove the message home three days ago. While attention fixates on hard engineering capabilities, competitive advantage hides in communication, code review and ownership mindset. Development leaders must guide teams away from pure syntax creation toward direction of autonomous systems. That transition demands skills many developers never practiced. DevPro Journal framed soft skills as the true differentiator.

Beck offers a framework for riding technology waves. He calls it explore, expand, extract. In the explore phase, run many cheap, uncorrelated experiments. Find what sparks. In expand, focus intensely on the promising direction and surmount obstacles. In extract, codify a repeatable playbook and scale with economies. Each phase demands different approaches to coding, hiring and organization. AI currently floods the industry with explore opportunities. Teams that recognize the phase avoid premature optimization or rigid processes.

Nobody knows the precise shape of programming two years from now. That uncertainty itself argues for breadth. Communication. Critical thinking. Documentation. Networking. These durable capabilities grow more valuable when fewer new entrants develop them through traditional deep implementation reps. Understanding of fundamentals, memory, I/O, concurrency, cost of operations, lets engineers call out production risks hidden in plausible-looking AI output. LeadDev explored the question in February.

Harvard Business School research from last year adds weight. Letian Zhang and colleagues demonstrated that soft skills nest inside technical ones. Communication and critical thinking unlock higher returns on hard expertise. Companies that identify and cultivate these foundations gain competitive edge. Wages reflect the compounding effect. Harvard Business School Working Knowledge summarized the paper.

Beck himself sounds optimistic. He enjoys programming more today than ever. Ideas long shelved because they seemed too large suddenly feel reachable. The genie handles boilerplate. The human supplies direction, taste and accountability. Yet he cautions against illusion. Trust evaporates faster than it forms. Code without accompanying understanding cannot be maintained safely, especially in payment systems, tax logic or critical infrastructure. There the process of wrestling with domain concepts, arguing over names, forging shared language still creates the necessary confidence.

His advice lands simple but demanding. Experiment relentlessly. No one can forecast the exact interplay of human and machine. Try the tools. Measure results. Adjust. Develop emotional regulation. Practice empathy. Learn to soothe as well as specify. Build relationships inside teams and across functions. These efforts accumulate the trust that pure generation cannot provide.

Recent X discussions echo the theme. One developer captured Beck’s response to Dario Amodei’s claim that AI will soon write almost all code. Beck pushed back sharply, arguing such statements reveal incomplete grasp of software engineering. Trust, not volume, defines sustainable systems. Another noted the irony that Beck, who popularized pair programming, now urges broader people skills. The conversation continues in real time.

The industry stands at an inflection. Acceleration outpaces adaptation in many organizations. Engineers who treat AI as amplifier rather than replacement position themselves for the long game. They pair technical judgment with human insight. They accumulate understanding alongside output. They turn Beck’s cosmic joke into professional advantage.

The punchline? The skills once dismissed as secondary have become primary. Those who master them will direct the genies. Those who don’t may watch from the sidelines as roles evolve around them. Beck learned the lesson late. Current practitioners have the chance to start earlier.

from WebProNews https://ift.tt/sbEFNyq

AI’s Electricity Appetite Forces Tech Giants Back to Nuclear

Tech executives once dismissed power as a background concern. No longer. Data centers built to train and run ever-larger artificial intelligence models now consume electricity on a scale that strains entire regions. Projections show global data center usage doubling or more by 2030. The numbers come from sober analysis, not hype.

The International Energy Agency put global data center electricity consumption at roughly 460 terawatt-hours in 2024. Its base case sees that figure climbing to 945 TWh by 2030 and 1,300 TWh by 2035. IEA Energy and AI report. Accelerated servers tied to AI account for nearly half the net increase. Conventional servers contribute far less. Growth in AI-related demand runs at 30 percent annually. The rest of the electricity economy expands at a fraction of that pace.

Inside the United States the pressure feels more immediate. Data centers already took 4.4 percent of national electricity in 2023. The Lawrence Berkeley National Laboratory sees that share reaching 6.7 to 12 percent by 2028. Absolute consumption could jump from 176 TWh to between 325 and 580 TWh. Brookings Institution analysis. Goldman Sachs Research expects power demand from data centers to rise 160 to 165 percent by 2030 compared with 2023 levels.

Gartner forecasts worldwide data center power demand will hit 132 gigawatts in 2026, up 27 percent from 2025. AI-optimized servers will represent 31 percent of that total. By 2027 their consumption should exceed conventional servers. Gartner press release. These shifts arrive as U.S. overall power use sets fresh records. The Energy Information Administration predicts consumption will climb from 4,195 billion kWh in 2025 to 4,271 billion in 2026 and 4,397 billion in 2027. Data centers and electrification drive most of the acceleration. Reuters report on EIA outlook.

But. The grid was never designed for this pace. Transmission lines fill up. New plants take years to approve and build. In parts of Virginia, Georgia and the Midwest, utilities have delayed or denied data center hookups. Hyperscalers respond by signing direct deals for power. Some buy entire adjacent power plants. Others bank on technologies that once seemed futuristic.

Nuclear stands out. It offers steady, carbon-free baseload without the intermittency of wind or solar. Tech companies have moved from talk to contracts. Microsoft reached a 20-year agreement with Constellation Energy to restart Three Mile Island Unit 1. The plant will supply electricity exclusively for Microsoft data centers. Amazon purchased a data center campus next to Talen Energy’s Susquehanna nuclear station, gaining nearly 2 GW of access. Google partners with Kairos Power on small modular reactors. Meta issued requests for proposals seeking up to 4 GW of new nuclear capacity. Utility Dive coverage of tech nuclear deals.

These moves mark a departure. For years big tech chased renewable power purchase agreements to meet carbon goals. Renewables now supply about 24 percent of data center electricity in the U.S. Natural gas still dominates at over 40 percent. Nuclear provides around 20 percent today but gains favor for its reliability. The IEA expects nuclear’s role to expand after 2030 once small modular reactors reach commercial scale. IEA energy supply for AI analysis.

Executives speak plainly. Former Google CEO Eric Schmidt told Congress that data centers will need 29 GW of additional power by 2027 and another 67 GW by 2030. Anthropic projects the U.S. AI sector alone could require 50 GW of new capacity by 2028. That equals roughly twice New York City’s peak demand. Brookings report citing executive testimony.

Challenges remain. New nuclear plants face regulatory delays, high upfront costs and public skepticism. Small modular reactors promise faster deployment and factory construction. Yet none operate at commercial scale yet in the United States. Natural gas plants fill the gap in the near term. They can be built quicker. They also lock in fossil fuel use for decades. BloombergNEF sees U.S. data center power demand more than doubling by 2035, reaching 78 GW. Average hourly electricity draw nearly triples. BloombergNEF analysis.

Water adds another constraint. Training and inference generate heat. Cooling systems consume millions of gallons daily. In drought-prone areas this creates tension with agriculture and municipal needs. Some operators explore advanced cooling or even immersion techniques. Efficiency gains help at the chip level. New generations of processors deliver more computation per watt. Still, the sheer volume of new workloads outruns those improvements.

Policy makers take notice. The White House promotes nuclear expansion, including both traditional reactors and modular designs. Bipartisan support for nuclear has grown since 2020. States compete to attract data centers with tax breaks and expedited permitting, yet they also worry about higher electricity rates for residents. In Ireland data centers already consume 21 percent of national electricity. That share could reach 32 percent by 2026. Similar debates play out across Europe and Asia.

So the industry finds itself at a crossroads. Hyperscalers invest in energy infrastructure as never before. Amazon backs X-energy to develop advanced reactors and aims for 5 GW of new nuclear by 2039. Microsoft, Google and others follow parallel paths. They act less like customers of the grid and more like energy companies themselves. Some explore microgrids, on-site generation and long-term fuel contracts.

Analysts caution against overstatement. Not every projection will materialize. Efficiency breakthroughs or slower AI adoption could temper demand. Yet the trend holds. Electricity consumption for AI servers grows faster than almost any other slice of the economy. From 2024 to 2030 data center power use expands more than four times quicker than the rest of the global electricity sector combined.

Recent updates reinforce the picture. As of mid-2026 forecasts point to U.S. data center consumption between 400 and 600 TWh by 2030 in credible scenarios. AI-specific servers accounted for 53 to 76 TWh in 2024 and could reach 165 to 326 TWh by 2028. Dev Sustainability review of multiple forecasts. Goldman Sachs notes nuclear will form part of the solution but cannot meet every need on its own. Natural gas, renewables and storage must contribute. Goldman Sachs Research on nuclear for AI.

The conversation has shifted from whether power will constrain AI to how quickly new supply can come online. Tech leaders once measured progress in model parameters and benchmark scores. They now track gigawatts secured and megawatts delivered. The next phase of artificial intelligence depends as much on electrons as on algorithms. And the race to supply those electrons has only begun.

from WebProNews https://ift.tt/8hD2Hy1

Meta’s Tightrope: Why the AI Giant Now Curbs Use of Claude and Codex

Meta has drawn a firm line around two of the industry’s most popular AI coding assistants. Engineers in its Applied AI division face strict new limits on Anthropic’s Claude Code and OpenAI’s Codex. The reason sits at the center of an intensifying battle over data, models and competitive edges.

Internal documents reviewed by The Information reveal the policy. Outputs from these rival tools risk contaminating Meta’s own training pipelines. One memo went further. It instructed some teams to pause specific tasks reliant on the external systems. The stated fear: “serious escalations with partner companies.”

But why now? And what does this reveal about the state of frontier AI development?

The process at issue is known as distillation. A smaller or newer model learns by studying the responses of a more powerful one. Feed it enough high-quality outputs. The student picks up sophisticated reasoning, coding patterns, tool use. The method proves cheap. It proves fast. It also proves legally risky when done without permission.

Anthropic made the dangers plain months earlier. In a February post the company detailed industrial-scale attacks on its Claude model. Three Chinese labs — DeepSeek, Moonshot AI and MiniMax — allegedly created more than 24,000 fraudulent accounts. They generated over 16 million exchanges. The targets included agentic reasoning, tool use and advanced coding. Anthropic called it outright capability extraction. The firm built detection classifiers and behavioral fingerprinting to fight back. It shared intelligence with other labs, cloud providers and authorities. Illicitly distilled models lack safeguards, the post warned. They could proliferate to military, intelligence or surveillance uses by authoritarian governments.

Meta’s concerns echo those warnings yet land closer to home. The social media company races to match rivals in agentic coding tools. It develops MetaCode as an in-house replacement for the very assistants its engineers have come to rely on. Heavy dependence on Claude Code or Codex during that build-out could funnel rival capabilities straight into Llama training runs. Terms of service violations would follow. Lawsuits could arrive soon after.

The bind looks uncomfortable. Meta still needs top-tier coding help to ship features quickly. For the moment the best options come from Anthropic and OpenAI. So the new rules demand caution rather than outright bans. Engineers must obtain approvals for certain uses. Some workflows halt until safer alternatives emerge. The policy applies inside the Applied AI unit created specifically to close the gap with pure-play AI labs.

Cost pressures compound the tension. Anthropic raised prices on its models. Amazon reportedly weighs cheaper substitutes. Meta likewise seeks to cut its AI tooling bill. Dependence on expensive outside systems clashes with ambitions to control every layer of the stack. Yet building that stack without borrowing capability from competitors grows harder by the month.

Anthropic finds itself in a position of unusual strength. Its Claude family has become a default choice for professional coders. The company secured a half-price deal to deploy Claude across California state agencies. Paying consumer subscriptions grow at pace. Such momentum gives Anthropic leverage to enforce rules against distillation. It previously accused Alibaba of distilling Claude into competing models. Meta clearly aims to avoid joining that list.

Nor does the squeeze come from Anthropic and OpenAI alone. Google reportedly capped Meta’s access to Gemini for coding and chatbot work, citing capacity shortages. Three major rivals now constrain Meta’s options. The company pours billions into talent and compute. Still it depends on the very labs it competes against for day-to-day engineering productivity. The internal memos reflect awareness of that paradox.

Observers see broader signals in the episode. AI companies no longer treat model outputs as mere service responses. They view those outputs as strategic assets worthy of protection. Training data has always been gold. Now the refined reasoning traces produced by frontier systems carry similar weight. Guarding them becomes table stakes.

Meta’s approach differs from Anthropic’s public campaign against Chinese labs. The social media giant focuses on internal hygiene. Prevent accidental leakage into its own systems. Avoid “serious escalations.” The quieter stance fits a company balancing partnership, competition and legal exposure in equal measure.

Questions remain about enforcement. How will Meta detect when rival outputs have already seeped into datasets? What thresholds trigger the pauses? How quickly can MetaCode mature enough to reduce reliance? Answers likely sit inside documents not yet public.

Recent coverage reinforces the shift. The Next Web reported the limits on June 30, noting the awkward need to keep using tools one hopes to replace. Firstpost highlighted the risk of proprietary capability transfer. The Decoder emphasized prevention of rival AI from entering Meta’s training data. These accounts draw from the same internal sources yet add texture around industry-wide cost concerns and Anthropic’s rising influence.

The story also illuminates maturation in the sector. Early days saw labs openly encouraging usage to gather data. Today many impose rate limits, monitoring and outright blocks to stop systematic extraction. Distillation moved from academic technique to contested frontier tactic. Enterprises treat it as both opportunity and threat.

For Meta the path forward demands balance. Accelerate internal tool development. Maintain enough access to rival systems to sustain velocity. Protect training data integrity. Satisfy partners that no improper transfer occurs. The new guidelines represent one concrete step on that path.

Whether they suffice only time and performance of MetaCode will tell. Other labs watch closely. If Meta succeeds without sparking legal clashes, similar policies could spread. The era of unrestricted use of competitor models for internal development may be drawing to a close. Control over the tools engineers touch daily now ranks alongside control over chips and data centers.

That realization marks a subtle but important turn. In AI, the means of production include not just the models but the daily instruments that shape them. Meta’s restrictions acknowledge that truth. They also signal how seriously every major player now takes the risk of unintended knowledge transfer.

from WebProNews https://ift.tt/c10OuNg

Nothing’s Instagram Takeover: Hack, Stunt, or Masterful Buzz Before Phone Launch?

Nothing India sounded the alarm on X. Its official Instagram account had slipped from the company’s grasp. Or so the statement claimed. “We’re aware of the recent activity on our Instagram account and are currently looking into the situation. This is not us,” the post read, per Android Authority.

The feed told another story. Hours earlier, polished teasers for the upcoming Phone 4b gave way to a stream of selfies. A mustachioed man stared back from the grid. He wore a Nothing jersey. The images looked too on-brand. Too clean. Too perfectly timed.

Skepticism spread fast. This didn’t match the usual playbook for compromised social accounts. No cryptocurrency scams. No demands for ransom. Just a fan in branded gear posting pictures of himself. Investigators quickly linked the photos to an Instagram user known as sportssugumar. The same individual had shared similar shots before. The jersey matched. The profile picture aligned. And in India’s cricket-obsessed culture, the connection made immediate sense.

But why go through the trouble? Nothing stands on the cusp of another product drop. The Phone 4b launch sits just weeks away. Attention matters. In a market crowded with flagships from Samsung, Google and Apple, the London-based brand built its name on bold design choices and clever marketing. Its Glyph interface, those distinctive LED patterns on the back of its phones, already turns notifications into something visual and unique. Fans customize light sequences for calls, messages and apps. They flip the device face down to read alerts at a glance without unlocking the screen.

And. This episode feels like an extension of that flair for the dramatic. Nothing has a history of playful engagement. Founder Carl Pei previously worked at OnePlus, where he helped shape a brand that thrived on community and hype. His recent Instagram videos take direct aim at Apple. “My name is Carl. I make phones in London. I’m gonna steal your customers. One bored iPhone user at a time,” he declared in one clip reported by Gadgets 360.

So was the Instagram incident genuine? Or did the company orchestrate a controlled leak of attention? The statement denies involvement. Yet the absence of typical hacker behavior raises eyebrows. No password resets. No suspicious links. Just content that subtly promotes the brand through a supposed fan takeover. Android Authority reporters reached out for comment. Updates may follow. For now, the episode sits in that gray area where marketing and mishap blur.

Nothing’s approach to hardware sets it apart. The Glyph system isn’t mere decoration. Users assign specific light patterns to contacts or apps. Essential notifications can trigger distinct animations even when the phone rests face down. Third-party apps like Glyphify extend the options further, letting owners create custom rules that go beyond factory settings. This level of personalization turns a simple LED array into a signature feature that competitors lack.

The company raised $200 million in its latest funding round, reaching a $1.3 billion valuation. That capital fuels expansion beyond phones into earbuds, watches and accessories. Each product carries the same transparent design language and software quirks that define the brand. Nothing OS builds on Android with added touches that feel fresh rather than derivative.

Yet social media remains a double-edged sword. A real breach could expose customer data or damage trust. Instagram itself faces its share of security headaches. Reports from early 2026 detailed claims of massive user data leaks affecting millions, though Meta pushed back on the scale. Cybersecurity Insiders examined those allegations and found many claims overstated or unverified. Still, the platform’s scale makes it a prime target.

Nothing’s case differs. The “hacker” posted harmless selfies. The account regained control soon after. No lasting damage appeared. Instead, the story generated headlines and social chatter exactly when the company prepares to unveil new hardware. Coincidence? Perhaps. But the optics favor the brand.

Industry watchers have seen similar tactics before. Tech firms occasionally stage faux controversies to spark conversation. The difference here lies in execution. Nothing didn’t amplify the drama itself. It issued a measured denial and let observers draw conclusions. That restraint only heightened the intrigue.

Pei continues to position the company as the antidote to smartphone boredom. His public statements target users tired of incremental updates from the duopoly. Nothing phones emphasize software polish, community input and those eye-catching Glyph lights. Early models sold well in India and Europe. The upcoming 4b series aims to build on that momentum with refined cameras, better battery life and tighter integration across the product lineup.

Whether the Instagram episode was authentic or engineered, it underscores a larger truth. In consumer tech, perception often outweighs raw specifications. A story that spreads organically carries more weight than paid advertising. Nothing has mastered this lesson. From transparent phone backs to LED symphonies on the rear panel, the brand sells experiences as much as devices.

Critics may call the episode contrived. Supporters see it as consistent with the company’s irreverent style. Either way, the conversation now centers on Nothing at a pivotal moment. Phone 4b teasers once filled that Instagram feed. Selfies replaced them. Then normal service resumed. The product launch looms. Expect the buzz to continue.

Tech companies rarely admit to manufactured virality. They prefer the narrative of organic discovery. Nothing’s denial fits that pattern. Yet the details don’t fully align with a malicious breach. The fan connection, the branded clothing, the timing before a launch. Each piece points toward calculated creativity rather than compromise.

Users of Nothing devices already enjoy deep customization. The Glyph interface allows patterns tied to specific apps or people. Missed calls pulse in one sequence. Messages from a partner trigger another. Bedtime modes silence the lights entirely. These small touches accumulate into a device that feels personal. The Instagram episode, real or staged, extends that personality into the company’s public image.

As Nothing scales, maintaining that edge grows harder. Larger competitors copy successful features. Regulatory scrutiny increases. Supply chain pressures persist. Yet the brand’s willingness to experiment, even in social media mishaps, keeps it relevant. Carl Pei didn’t build his reputation on caution. He bets on bold moves that capture attention.

The final verdict on this incident may never arrive. Nothing could clarify further in coming days. Or the story might fade as the next hardware reveal takes center stage. For an industry that prizes engagement metrics above almost anything, the episode delivered. Followers noticed. Media covered it. Speculation filled timelines. And the Phone 4b now enters the spotlight with extra momentum.

That’s the power of a well-timed disruption. Whether engineered or accidental, it works. Nothing keeps proving that in a crowded market, standing out matters more than blending in. Its phones light up from the back in unique patterns. Its marketing, it seems, does the same.

from WebProNews https://ift.tt/4la8dyi