>It's a stack of 3 complementary and orthogonal technologies that don't overlap.
Irrelevant. I need one language to describe the data, a completely different language to specify how to lay it out and a third completely different language to do any dynamic work (which is a lot these days). In e.g. iOS I can do all this with Objective-C.
>For me it all comes down to developer happiness, that is, achieve maximum effect in less time.
Agreed.
>That's why i m a webdev diehard and will never endeavor on proprietary closed frameworks.
That's why I'm not and hopefully will never have to be.
We are obviously in different camps. Yet, regarding the first point, it's not irrelevant. Can you layout apps in ios or android without learning about layout files, property files or what else?
Actually yes. I can't speak to Android but on iOS you can just drag the controls where you want them to be. Or you could just do it all in code. You don't have to learn anything but the language and the APIs if you don't want to.
Irrelevant. I need one language to describe the data, a completely different language to specify how to lay it out and a third completely different language to do any dynamic work (which is a lot these days). In e.g. iOS I can do all this with Objective-C.
>For me it all comes down to developer happiness, that is, achieve maximum effect in less time.
Agreed.
>That's why i m a webdev diehard and will never endeavor on proprietary closed frameworks.
That's why I'm not and hopefully will never have to be.