Urgent.News

600+ sources. One page. See who else covered it.

Editions

Tech

The Real Reason Data Center Gas Power Plants Are So Dirty

A massive new gas plant in Texas will be built with much less efficient technology than regular gas plants. It’s far from the only data center power project to rely on dirty turbines.

The Real Reason Data Center Gas Power Plants Are So Dirty

An Amazon data center in Texas will be powered by a massive off-grid power plant, which could be considered one of the highest sources of greenhouse gas emissions in the US. However, the plant's environmental impact is not solely due to its size. The plant will utilize simple cycle gas turbines, which are less efficient than the combined cycle turbines typically used in regular power plants.

These simple cycle turbines release significant amounts of waste heat, contributing to higher emissions for the same amount of energy produced. According to the US Environmental Protection Agency, even if the Texas plant emits only half of its permitted emissions annually, it would still generate more greenhouse gas pollution than 78 average-sized natural gas plants.

The use of simple cycle turbines is becoming increasingly common among data center power developers seeking flexible, quickly installable power. Other tech giants, such as Meta, Microsoft, and Google, are also investing in similar projects. These plants are permitted to release millions of tons of greenhouse gases. While Amazon claims that the Texas plant will not raise electricity costs for Texas families and will eventually transition to grid-connected service, the rapid construction of new, inefficient power plants threatens to create a parallel fossil fuel grid generating substantial greenhouse gas emissions.

Written by urgent.news from Wired's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.

Also reported by 1 other outlet

Read the original at wired.com →

More in Tech

RAG vs. Direct Context: I Tested Both on Real Documents, Here's What Broke

A hands-on test of BGE-M3 + Qwen3 (RAG vs. direct-context answering) on a real research paper and a full-length book including a retrieval bug hiding in a footnote, and one surprisingly good model…

  • RAG and direct-context answering tested on real documents
  • RAG failed with full-length book, retrieved footnote as main contribution
  • RAG excelled with specific question about book, identified lack of relevant context

AWS WAF Challenge : bloquer les bots avant qu’ils n’atteignent l’application

Quand on m’a appelé, l’attaque durait depuis environ une semaine. Elle visait la page de connexion d’une application historique qui générait son HTML côté serveur.

  • Attack targeted legacy application's login page
  • Million queries from vast IP addresses, ineffective IP blocking
  • AWS WAF Challenge feature placed at infrastructure layer

Why RAG on legal text keeps hallucinating dates - and what actually fixed it

A couple of weeks ago I dropped the CRA text (the EU's cybersecurity regulation for IoT devices) into ChatGPT and asked when the main requirements actually kick in.

  • ChatGPT incorrectly stated CRA regulation entered force in 2024, 3 years off.
  • Dispersed dates in EU regulation PDF caused AI confusion.
  • Platanor rebuilt repository with proper file structure to fix RAG hallucinations.