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 | MK Stalin responds to Yogi Adityanath over Hindi row, calls remarks “political black comedy” | Get Latest International News & Updates. Your Source for World Events and Updates - NRI Page
Edit

MK Stalin responds to Yogi Adityanath over Hindi row, calls remarks “political black comedy”

MK Stalin responds to Yogi Adityanath over Hindi row, calls remarks “political black comedy”

In a fiery exchange over the long-standing language debate and the contentious three-language policy under the Centre’s National Education Policy (NEP), Tamil Nadu Chief Minister MK Stalin has launched a scathing counterattack on Uttar Pradesh Chief Minister Yogi Adityanath. Responding to Adityanath’s accusation that the DMK is fostering regional and linguistic division for vote-bank politics, Stalin described the remarks as not ironic but “political black comedy at its darkest.” The controversy erupted following Yogi Adityanath’s interview with ANI where he took aim at the Dravida Munnetra Kazhagam (DMK) and its leadership, accusing them of politicising the language issue and dividing the nation along regional lines. According to Adityanath, the DMK’s consistent opposition to Hindi was not based on policy concerns but was a tactic to protect its electoral base. He emphasized that every Indian should learn and respect all Indian languages, including Hindi and Tamil, which he called “one of the oldest and most revered languages in the country.”
 

However, Stalin’s rebuttal was swift and sharp. In a post on X (formerly Twitter), the Tamil Nadu Chief Minister stated that the state’s position on the two-language formula and its opposition to the upcoming delimitation exercise is not rooted in hatred but in the protection of federal values and social justice. “We don’t oppose any language; we oppose imposition and chauvinism. This isn’t riot-for-votes politics. This is a battle for dignity and justice,” Stalin posted. He further criticized Yogi Adityanath’s attempt to lecture Tamil Nadu on hate, noting that Tamil Nadu’s stance is not only constitutionally valid but also resonating nationwide. “And now Hon’ble Yogi Adityanath wants to lecture us on hate? Spare us,” he added, underlining the cultural and democratic uniqueness of the state.
 

Language Politics and Delimitation: A Larger Federal Debate

Tamil Nadu has been at the forefront of the opposition to the Centre’s push for a three-language formula, which includes the compulsory learning of Hindi in non-Hindi speaking states. The state has long adhered to a two-language policy—Tamil and English—rejecting Hindi imposition as a form of cultural dominance. The issue has gained renewed attention as the NEP implementation progresses and Hindi becomes more prominent in central examinations, education, and administrative communication. The DMK sees this as an infringement on regional identity and linguistic freedom. Another major flashpoint is the proposed delimitation exercise scheduled after 2026, which will redraw parliamentary constituencies based on updated population data. Stalin has voiced strong opposition to this process, warning that it will reduce the representation of southern states like Tamil Nadu in Parliament. These states, he argues, have successfully implemented population control measures and would be unfairly penalized for their developmental achievements.
 

“The delimitation exercise threatens to dilute the voice of progressive states which have contributed more to the national GDP while maintaining population discipline,” Stalin has repeatedly said. His concerns reflect the broader apprehension among southern states that delimitation based solely on population figures will shift political power disproportionately to the Hindi-speaking north, undermining federal balance. Yogi Adityanath, on the other hand, framed the DMK's resistance as narrow-minded and divisive. “When these people feel their vote bank is at risk, they try to create divisions based on region and language,” he said. “The people of this country should always be alert to such divisive politics and stand firm for the unity of the country.”
 

He also cited the Kashi-Tamil Sangamam, a cultural exchange event promoted by the Central Government, as a symbol of unity between regions. “We are grateful to Prime Minister Modi ji for organising the third generation of the Kashi-Tamil Sangamam in Varanasi,” Adityanath stated, adding that Tamil and Sanskrit both form the core of India’s ancient heritage. Despite this olive branch, tensions continue to rise as both leaders stand firm on their narratives. For the DMK and Stalin, the issue extends beyond language to a larger assertion of Tamil identity, federal autonomy, and resistance against central overreach. For the BJP and Yogi Adityanath, the emphasis remains on promoting national unity and integrating regional identities into a broader Indian cultural framework. As the debate intensifies in the lead-up to general elections and major policy rollouts like delimitation, language and regional identity are once again at the heart of India’s political discourse. Whether this fuels division or sparks a deeper conversation about India's pluralism and federalism remains to be seen.

What is your response?

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