Axiom

Architecting systems. Automating workflows. Exploring AI.
Azure • Agents • Cloud
Code. Build. Repeat.

[Axiom @KernelGhosty]

@anoopkumar_ch @Starlink Brown sepoy 🤣

[Axiom @KernelGhosty]

@VedVery5 @Pankajpadekar @elonmusk Clearly you don't understand Starlink's architecture. It completely bypasses local land infrastructure, making it a unique national security challenge. Since you're in tech, do some basic research on LEO satellites and the history of non-compliant networks first. LMAO

[Axiom @KernelGhosty]

@VedVery5 @Pankajpadekar @elonmusk Chup chutiya you can't jamm it ... Us company anyways non compliant

[Axiom @KernelGhosty]

@NotSoStud @VedVery5 @xarvindk @elonmusk Chutiya ka dimag ghutno me hai.. nahi samjhega

[Axiom @KernelGhosty]

@VedVery5 @xarvindk @elonmusk No doubt you are whatapp university designer 😭😭😭😭

[Axiom @KernelGhosty]

@FighterPiloting @_yf23_ @KaliputraX The reality is stark: India’s aviation relies on an unstable foundation. The Tejas Mk2 and AMCA are too interdependent. Combined with a shaky US engine relationship, both platforms face an existential crisis. I hope I'm wrong, but they won't survive.
https://t.co/81sgzi66j7

[Axiom @KernelGhosty]

@FighterPiloting @_yf23_ @KaliputraX Let's be straight: the Tejas Mk2 and AMCA are tied at the hip. The current programmatic deadlock puts both at risk of replicating the premature end of the HAL Marut. Bottom line: neither fighter program has a viable future without the other or a sovereign engine ecosystem.

[Axiom @KernelGhosty]

@FighterPiloting @_yf23_ @KaliputraX You are confusing external network links with internal avionics architecture. We aren't arguing about the tactical value of AWACS or MUM-T. We are discussing the internal hardware bottleneck of the Mk1A.

[Axiom @KernelGhosty]

@FighterPiloting @_yf23_ @KaliputraX Having a fast Ethernet radio means nothing if the internal avionics bus bottlenecks that data at 1 Mbps before it can be fused and shown to the pilot. Mk1A has a modern "mouth" (the radio) but legacy "veins" (the bus). Mk2 gives it a full digital backbone.

[Axiom @KernelGhosty]

@FighterPiloting @_yf23_ @KaliputraX Check details https://t.co/aLpPTK5PBb

[Axiom @KernelGhosty]

@FighterPiloting @_yf23_ @KaliputraX Wrong, The Tejas Mk1A uses an older military databus (MIL-STD-1553B) that transfers data at just 1 Megabit per second, which is far too slow for heavy sensor fusion.Tejas Mk2 , It shifts to a high-speed fiber-optic netwok

[Axiom @KernelGhosty]

@FighterPiloting @GVC_16 The transition from Tejas Mk1A to Mk2 evolves the aircraft into a larger, more powerful medium-weight fighter, while the shift from Mk2 to AMCA steps up to a twin-engine, fifth-generation stealth design that intentionally shares the same core engine and avionics.

[Axiom @KernelGhosty]

@PulseDopplerRF @ThatArticleGuy He is dumb like our ndtv reporter...

[Axiom @KernelGhosty]

@ThatArticleGuy @NoEasyWayOut6 Such a dumb take.... Without mk2 there will be no AMCA..

[Axiom @KernelGhosty]

@sybauchamar Lmao, those bilateral records only exist because of match-fixing and underworld ties 🤣 That's precisely why the stats look so embarrassing when it comes to actual ICC games.

[Axiom @KernelGhosty]

@RajeshwariRW My estimate it required max 30 days to replace these.. All backend infra already exists just need to create the wrappers.

[Axiom @KernelGhosty]

@RajeshwariRW It’s a hypothetical scenario, and if it happens, we have the manpower to handle it, Only thing we are lagging is in AI but you can opt for open-source. We’re not in the Stone Age these services are quite basic today, and most of the required backend infrastructure already exists.

[Axiom @KernelGhosty]

@AmeyKulkarni_21 It’s a hypothetical scenario, and if it happens, we have the manpower to handle it, so his point is valid. We’re not in the Stone Age these services are quite basic today, and most of the required backend infrastructure already exists. Only thing people don't know. 🙂

[Axiom @KernelGhosty]

@Libertariazne4 🤣🤣🤣

[Axiom @KernelGhosty]

@Happydays99X 🤡🤡🤡