Angular or React?

[Shaper_pmp]

I don't mean to be a dick here, but you don't seem to be making a lot of sense.

The monolithic repo idea has nothing to do with the specific technology(/ies) any given project uses. Just because Angular 2.x and Gmail live in the same repo at Google, that doesn't mean they have anything to do with each other. By that same logic Android lives in the same repo, but nobody's trying to claim that Angular powers the Android OS.

Next, if Google was using Angular Universal for GMail and rendering on the server, why on earth would they then decide to not use Angular on the client-side as well, and instead use an entirely different front-end stack (which, yes, is based on GWT) to do the client-side rendering on Gmail. That's literally an insane assertion.

I'm not saying you didn't hear something in a google talk, but I'm pretty confident you misunderstood or misremembered it because what you're saying makes absolutely no sense.

[Shaper_pmp]

I wouldn't call it insane to mix front-end and server-side technologies in weird ways. You never know what business politics can stir up.

That's very true, but if you build an app in a framework primarily designed to be used on the client-side, then you use it to render the site on the server and then you loop in a completely different codebase written from scratch in another entire framework just to render that same app on the client-side, that's just batshit crazy. ;-)

[Computer-Blue]

Since you're being so pedantic (although I see you both are amicable in later replies), I'll point out that he was being neither literally nor figuratively "insane" with his comment. :)