Neuromorphic Processors Lag Behind GPUs for Large AI Models Despite Energy Advantages
Neuromorphic processors can perform an impressive trick: while nothing significant is happening around them, large portions of the circuit stay almost silent. When a signal arrives, the relevant artificial neurons activate, a brief stream of spikes passes through, and the computation ends. Compared with today’s AI accelerators that continuously crunch enormous arrays of numbers, the approach appears almost suspiciously efficient.
This efficiency raises an obvious question. If neuromorphic chips can save power, keep state next to the compute units, and even rewire connections during operation, why are data centers still filled with GPUs? Why can’t a large language model simply be moved to a brain-like processor and slash electricity bills?
The answer is straightforward. Neuromorphic architecture excels at a specific class of problems, but today’s generative AI has grown around an entirely different kind of mathematics. Large models favor dense matrix operations, enormous memory capacity, high numerical precision, and mature development tools. Neuromorphic systems must either alter their own architecture or fundamentally change the model itself. Researchers are currently pursuing both routes.
Why neuromorphic chips have not yet gone mainstream
The bottleneck is no longer the lack of working silicon. Intel has produced two generations of Loihi and the large-scale Hala Point system. BrainChip ships the Akida family. SynSense sells specialized processors for vision and temporal signals. SpiNNaker2 enables large event-driven systems. Yet a compelling advantage for mass-market workloads that would justify switching to an entirely new computing model is still missing.
GPUs have accumulated a vast software ecosystem over the past decade. A developer can take a ready model, library, driver, and profiler and run familiar code. For a neuromorphic processor, engineers often must select a different network architecture, convert the model, account for spike timing, and re-validate accuracy.
On-chip learning and synaptic plasticity
Neuromorphic processors can support local weight changes. The device receives new events and gradually adapts part of the network without shipping all data back to a central facility. Intel Loihi 2 was designed in part to study programmable on-chip learning. In 2025 researchers demonstrated contextual learning of a transformer on Loihi 2 using local plasticity for attention-like operations.
One well-known local rule is STDP (Spike-Timing-Dependent Plasticity). If one neuron fires just before another, the connection between them can strengthen; the reverse timing weakens it. This rule lets each synapse adapt using only nearby activity and precise timing, without waiting for a global gradient computation. However, simple local rules still fall short of the global optimization that gives today’s deep networks their accuracy.
Running large language models on neuromorphic hardware
At the 2025 ICML conference, researchers presented Sorbet, a spiking language model based on the transformer architecture. They replaced operations poorly suited to neuromorphic hardware, such as standard normalization and Softmax. Another 2025 effort converted a 1.5-billion-parameter model into spiking form, used sparse linear attention, and reported 161.8 tokens per second on an FPGA with markedly better energy efficiency than an A800 GPU. Direct comparison with production LLM stacks remains premature.
Future computing landscape
Complete replacement of GPUs by neuromorphic processors is considered unlikely because the two architectures optimize different properties. GPUs thrive on sustained high utilization of thousands of arithmetic units; neuromorphic systems gain advantage from sparsity. The most probable outcome is a heterogeneous platform in which neuromorphic blocks monitor rare events, matrix accelerators handle heavy generative workloads, in-memory and analog units reduce data movement, and photonic elements manage extreme parallelism. The CPU would continue to orchestrate tasks that do not benefit from specialized hardware.
Related articles
Wireshark Wi-Fi Traffic Analysis: Diagnosing Connectivity Failures in 802.11 Networks
Wireshark captures help distinguish between radio-layer issues, DHCP failures, and application-layer problems when a device connects to Wi-Fi but cannot load pages. The guide explains how to select the right capture point—client, monitor-mode adapter, or wired side of the access point—and why ordinary Ethernet headers often hide critical 802.11 management and control frames. Detailed sections cover CSMA/CA contention, frame types (Management, Control, Data), EAPOL-Key exchanges for WPA2-Personal, and the limitations of retry flags as loss indicators. Practical Linux commands using iw, dumpcap, and NetworkManager demonstrate how to enable monitor mode on channel 6 HT20 and record a two-minute trace. Filters for wlan.addr, eapol, and wlan.fc.retry allow analysts to isolate association failures, key-handshake problems, or DHCP delays. The article also addresses decryption of WPA2 traffic with a known passphrase and warns that Wireshark cannot replace a spectrum analyzer for detecting non-Wi-Fi interference.
15-Year-Old Developer Restores Social Network After Beget VPS Data Wipe in Cyber Attack
A 15-year-old Russian developer recovered his social network Agora within three hours after hosting provider Beget confirmed that a cyber attack had wiped his VPS, including binary backups. The recovery relied on offsite encrypted PostgreSQL dumps created just one day earlier using pg_dump and GPG, an escrow key for end-to-end encrypted messages, and pre-written migration scripts stored in a repository. The master encryption key stored only in the server environment was lost, rendering old private keys unusable and forcing a full re-encryption of 1218 messages via the escrow mechanism. Additional issues included broken authentication in existing Android builds, dead push notification subscriptions, and a failed monitoring runner hosted on the destroyed server. The incident highlighted the risks of single-provider architecture and insufficient offline key storage while demonstrating effective disaster recovery practices for a self-hosted Supabase stack.
Developer Creates Personal Task Manager Allowing Claude Code and OpenCode Agents to Autonomously Execute Marked Tasks
A developer has built a personal task management system at shar8.app that integrates directly with AI coding agents including Claude Code, Codex CLI, and OpenCode through the Model Context Protocol. Tasks marked with an 'Agent' flag are automatically picked up by scheduled agent runs, executed locally on the user's machine, and results are written back into the task notes for human review. The system supports both browser-based OAuth authentication and persistent bearer tokens for headless cron or CLI usage, with strict separation between human-initiated and agent-initiated actions. Security measures include treating task text as untrusted data rather than instructions, disabling all tools by default, and requiring explicit allow-lists for any external actions such as web search. The implementation uses a custom MCP server exposing fifteen specific tools for listing, creating, editing, and delegating tasks, while a companion plugin for Claude Code handles scheduled execution via native system schedulers like launchd and systemd timers. The author emphasizes that agents never assign work to themselves and that final task closure always remains with the human user.
T-Bank Warns Customers of Payment and Transfer Outages
On November 3, T-Bank notified users that payments and transfers may fail due to ongoing technical issues. The bank placed an in-app message stating that the problems are being fixed. Clients confirmed the disruption through reports to Interfax, noting that the online banking interface displays the warning upon login. The outage affects only payments and transfers, while other banking services remain available. No details were provided regarding the root cause, the number of impacted users, or an estimated time for full recovery. Monitoring service DETECTOR404 also recorded the incident, aligning with user complaints and the bank's official notice.