Recommended Posts

First nuclear reactors since 1970s approved in US

The US Nuclear Regulatory Commission has approved the first nuclear reactors to be built in the country since 1978.

The commission voted 4-1 in favour of Southern Co building two nuclear reactors at an existing Georgia plant.

But Chairman Gregory Jaczko voted against, expressing concern that the licence was being approved "as if Fukushima never happened".

The reactors are expected to cost $14bn (?8.8bn) and could begin operating as early as 2016 or 2017.

No reactors have been approved for construction since a year before the accident at Three Mile Island, a nuclear power plant in Pennsylvania, in 1979.

'Binding commitment'

Safety concerns around nuclear power have risen following a meltdown at Japan's Fukushima power plant in March 2011 after an earthquake and tsunami damaged safety features.

In the wake of the Japanese disaster the commission launched a review into whether existing and new US reactors could withstand natural disasters like earthquakes and floods.

Mr Jaczko said he believes approving the reactors "requires some type of binding commitment" that safety enhancements planned from the review would be in place before the reactors opened.

Southern's project is considered a test of whether the industry can avoid costly delays that plagued previous reactors.

The Obama administration has offered Southern and its partners $8.3bn in federal loan guarantees, helping lowering financing costs.

The reactor design, approved separately in December, will also be used by utility companies in Florida and South Carolina currently in the approval process.

Source: BBC News

"as if Fukushima never happened"

Saying this is as dumb as saying that it's a shame that airplanes are still being produced after 9/11

I wouldn't call coal safe, those plants can put out a fair bit of radioactive material.

On top of the massive amount of any other kind of pollution that's guaranteed with burning fossil fuels. Nuclear only poses a safety risk in the case of a leak or other disaster which is actually pretty rare, just big news when it does happen. Fossil fuels on the other hand pollute and cause air quality issues all day every day.

At least someone in the US has some sense.

Meanwhile in the EU, "Green people" are more and more successful at shutting down existing nuclear power plants. In a few years time we will probably be burning wood again to heat ourselves and use candles for lighting.

At least someone in the US has some sense.

Meanwhile in the EU, "Green people" are more and more successful at shutting down existing nuclear power plants. In a few years time we will probably be burning wood again to heat ourselves and use candles for lighting.

More likely in a few years we'll be buying energy from countries that produce it with nuclear plants.

This is already happening in Italy where nuclear energy has been banned in the 80's after chernobyl disaster. Nowadays we buy energy from France. Energy produced in nuclear plants located near italian borders. :rolleyes:

If a Coal plant explodes, then the surround area is usable again within a relatively short time compared to using Nuclear.

I'm not against Nuclear, but i'm just point that fact out. Modern nuclear designs are far safer than they used to be. (Y)

Most modern reactor designs are not capable of doing a Cherynobl or Fukushima - they passively safe themselves.

Then there is my favorite: liquid salt thoroum reactors; the fuel is molten naturally, so there is no structure to damage. This plus the benefits of the thorium fuel cycle.

Then there is my favorite: liquid salt thoroum reactors; the fuel is molten naturally, so there is no structure to damage. This plus the benefits of the thorium fuel cycle.

I watched a TED video about this. It sounds highly promising.

For those interested - http://www.ted.com/talks/lang/en/kirk_sorensen_thorium_an_alternative_nuclear_fuel.html

Most modern reactor designs are not capable of doing a Cherynobl or Fukushima - they passively safe themselves.

Then there is my favorite: liquid salt thoroum reactors; the fuel is molten naturally, so there is no structure to damage. This plus the benefits of the thorium fuel cycle.

If that's the design I'm thinking of, then it's naturally self moderating. As it heats up the fuel expands, extending outside the main reactor core, slowing down the reaction and letting it cool down and contract again.

Awesome design, but at the same time it increases the risk of processing accidents while decreasing the risk of operating accidents (Since the fuel is liquid, it's easy to spill, vs. a solid rod or such)

Edit: The CANDU design is similar in how it handles that situation, the fuel rods are mounted horizontally so if they start overheating and melting, they bend out of shape and slow down the reaction (And the CANDU design can run on just about anything, natural uranium, spent fuel from other reactors, dismantled nuclear warheads, thorium, etc.)

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      592
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!