A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Duke vs North Carolina in NCAA Women’s Sweet 16: Rivalry Hits Historic March Madness Stage | Get Business News. Grow and Thrive in the Modern Market around the world - NRI Page
Edit

Duke vs North Carolina in NCAA Women’s Sweet 16: Rivalry Hits Historic March Madness Stage

Duke vs North Carolina in NCAA Women’s Sweet 16: Rivalry Hits Historic March Madness Stage

BIRMINGHAM, Ala. — One of college sports’ most iconic rivalries is set to write a new chapter on an even grander stage. On Friday, in the NCAA Women’s Basketball Tournament Sweet 16, Duke and North Carolina will face off for the very first time in tournament history. The game, which tips off at 2:30 p.m. ET on ESPN as part of the Birmingham Regional 2 semifinals, will be the third meeting between the two programs this season — but the first ever in March Madness. For a rivalry that stretches back nearly 50 years, it’s hard to believe this will be the first NCAA tournament clash between the Blue Devils and the Tar Heels. They’ve played 110 times since their first meeting in the 1975-76 season, with North Carolina holding a narrow 56-54 advantage in the series. But never before have the stakes been this high.
 

Both teams split their regular-season matchups this year. North Carolina emerged victorious in a 53-46 overtime battle on January 9 in Chapel Hill, while Duke responded with a dominant 68-53 win on February 27 in Durham. Friday’s game will be the tiebreaker — with a spot in the Elite Eight on the line. Courtney Banghart, head coach of the Tar Heels, recognizes the historical significance of this moment, not just for the programs but for women’s basketball overall. “I celebrate along with all the sports fans that have been watching so many Duke-Carolina battles throughout the years,” Banghart said. “We did it. We got you guys an NCAA tournament game between Carolina-Duke. If that doesn’t get your blood going, you should check it.”
 

On the other side, Duke head coach Kara Lawson is keeping the focus squarely on performance, not the narrative. Known for her no-nonsense approach since taking over in 2020, Lawson admitted she wasn’t even aware that this was the rivalry’s first tournament meeting. “We’re fighting for a spot in the Elite Eight, and so whoever the opponent is, is the opponent,” she said. “It’s not something we’ve really talked about or worried about.”
 

Tactical Chess Match Awaits Between Familiar Foes

While fans are buzzing over the historic backdrop, the on-court matchup promises to be a gritty, defensive contest. The numbers tell the story: Duke averages 73.8 points per game while holding opponents to just 57.1, whereas North Carolina scores 70.5 per game and allows only 57.6. These are two teams that pride themselves on their ability to lock down opponents, and familiarity from two previous meetings will only tighten the margins. Adding another layer of complexity is the return of key players for both teams. Tar Heels standouts Alyssa Ustby and Reniya Kelly, who missed the second game against Duke due to injuries, are both back in the lineup. On Duke’s side, freshman phenom and leading scorer Toby Fournier, who was out sick during their second-round victory over Oregon, is also returning to action.
 

Ustby, a fifth-year senior who knows the intensity of this rivalry all too well, believes experience will be critical. “The basketball you're going to see will be very gritty, maybe a little bit sloppy,” she said. “It’s hard to predict games like that. The teams know each other way too well. But we remind each other on court not to worry about those little feisty interactions and stuff. We know they're going to happen, especially at this stage with an Elite Eight on the line. That's much bigger stakes than a regular-season game.” Lawson, who took over during the uncertainty of the COVID-19 pandemic and saw her first season cut short after just four games, has gradually built Duke into a tournament regular. The Blue Devils missed the 2022 tournament but have now made three consecutive appearances and are in their second straight regional semifinal. Historically, Duke has reached the women’s Final Four four times — all under former coach Gail Goestenkors — with the most recent in 2006.
 

North Carolina, meanwhile, boasts a proud tradition with a national title in 1994 and Final Four appearances in 2006 and 2007. Under longtime coach Sylvia Hatchell, the program enjoyed sustained success until Banghart took over in 2019. The Tar Heels have now made the tournament five straight years and reached the Sweet 16 in 2022. Perhaps most striking about this year’s tournament is that it marks the first time both Duke and UNC ended up in the same regional bracket. It’s a coincidence that has produced a matchup decades in the making and one that could become a defining moment in both programs’ history. As Banghart pointed out, the Triangle region is enjoying a golden age in women’s basketball. In addition to Duke and UNC’s presence in the Sweet 16, NC State is also alive in the Spokane Regional, where they’ll face powerhouse LSU. It’s a time of unprecedented strength and visibility for the ACC and North Carolina basketball as a whole. Regardless of who wins Friday, the outcome will resonate far beyond the court. This game is about more than advancing to the Elite Eight. It’s about a rivalry finally getting its moment on the biggest stage, bringing generations of fans — and players — along for the ride.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD