@alpha_defense The more pain we endure, the stronger we become as a nation. Let them block technology and impose restrictions. Eventually, we’ll develop it ourselves. Bite the bullet now for a stronger, self-reliant future.
@DefenceMinIndia Sir ji apako sabse pahele screwdrivergiri 🪛 chahiye there will be no other nation on earth who will allow foreign OME to play at cost of indigenous system.
You are the most useless and incompetent on understanding defence. विश्वगुरु बाते करने से नहीं बनाते !!!
@ShiroBarks@strategicfront Tejas was never just about building a fighter jet. It was about rebuilding an entire aerospace ecosystem India had lost—flight controls, composites, radar, testing, weapons integration and design expertise. Delays were real, but so was the capability created. 🇮🇳✈️
@jeevish@ragebaitop Blaming HAL alone is convenient. If manpower, testing capacity and programme structure were known bottlenecks, then responsibility sits with the whole system — MoD, ADA, HAL, IAF and funding/staffing decisions. Who knew, who could fix it, and why didn’t they?
@braddy_Codie05 Delays are real. But Tejas wasn’t simply a HAL project—ADA led design, HAL production. IOC-I came in 2011, IOC-II in 2013. And no, a 2016 Tejas was not “1983 technology”; avionics, sensors, weapons and configuration evolved repeatedly.
@VishnuNDTV Interesting how every Tejas delay becomes an argument for another foreign ord. Mk2 hasn’t rolled out -we know. Now compare it honestly with Rafale: all aspects including delivery timeline. Otherwise just say it plainly: imports first, indigenous programme second. Import Bahadur.
@alpha_defense What a convenient little ecosystem: Tejas in the 2030s is “obsolete,” Rafale in the same decade is “urgent.” Criticise HAL by all means, but this selective hysteria looks less like analysis and more like narrative-setting for another import push.
@AdithyaKM_ The full answer matters. Kapoor didn’t “slam” Tejas Mk2—he explicitly said India still needs it, but much faster. The real issue is selective framing: if “4th gen in 2035” is the test, why wasn’t Rafale subjected to the same question?
@alpha_defense That’s the import-lobby logic: Tejas in the 2030s = obsolete, imported 4.5-gen jets in the same decade = acceptable. Same timeline, same generation, different standard.
@swasrao Calling a spade a spade cuts both ways. If Tejas has capability gaps, say so. But also ask why those gaps weren’t closed with sustained funding, orders and user feedback—and why 2030s timelines are unacceptable for indigenous jets but acceptable for imports.
@VishnuNDTV@ndtv This isn’t about defending HAL delays. It’s about consistency. If Tejas Mk2 arriving in the 2030s is “too late,” then apply the same scrutiny to imported fighters arriving in the same decade. Question indigenous failures—but question import dependence too.
@VishnuNDTV You called Tejas/Mk2 “too little, too late.” Then apply the same standard to Rafale: 114 jets aren’t even contracted yet and deliveries would stretch deep into the 2030s. Why is delay a strategic problem only when the platform is indigenous?
@rhinohistorian@sakthivel_cit93 So the choice should not be “Rafale or Atmanirbharta.” Buy enough Rafales for the genuine gap, but use the same 2030 timeline to massively scale Tejas Mk2, AMCA and an indigenous engine ecosystem.
@rhinohistorian@sakthivel_cit93 On engines, I would not claim Kaveri will definitely power fighters by 2030. But India can push a 90–110 kN indigenous engine program aggressively while using F414 for Mk2 in parallel.