Using Kernel.js for bigger usecase

[Kailash Singh]

Hi, I went though the architecture which Nicholas proposes and finds it exciting. We are thinking of proposing this architecture across our organization but before that I need something up and running. So currently evaluating few JS libs that provides some kind of support for that structure. So now I am evaluating Kernel.js not actually written anything but just gone though the details available on its site.

I have few questions in mind like before I actually write code in that.

1. Will it be able to support modules those are not simple enough but contains MV* pattern within itself.

 for e.g. there are modules having its own view, viewmodel, model forming a widget

2. Since the architecture restricts the direct communication between different modules, will kernel be able to provide the navigation capabilities between view of different modules.

3. I see there is no separate entity for Base Library, does kernel knows directly which libraries are being used. Shouldn't it be abstracted. 

4. I think Base Library cannot include libraries like Knockout, Kendo these needs to be directly referred in modules and cannot be abstracted in Base Library.

Its lot to ask for now but I need these information to evaluate it and if it provides the capabilities we can use it for our projects.

Thanks,

Kailash Singh