Soma.js and Angular Kendo UI

[Oscar Lito M Pablo]

Hi Romuald,

Thanks for the fantastic article you wrote at FlippinAwesome.org (http://flippinawesome.org/2013/07/15/soma-js-your-way-out-of-chaotic-javascript/)! Soma.js looks like the JS framework I’ve been looking for, and your article introduces us exceedingly well to it.

If it’s okay, would you mind spending a few minutes on the items below? (I’d like to consider using Soma.js for a consulting project in its early stages, and info on these key issues will help me decide if Soma.js is a viable option):

My questions:

1. Is there a good, solid use case for Soma.js and Angular.js to coexist and be used in the same application targeted for smartphone, tablet and desktop distribution?

If so, how do you think this use case should be handled? (I’m actually going to use Angular Kendo UI (http://kendo-labs.github.io/angular-kendo/#/) for the tablet and desktop versions of the application.)

2. Is Soma.js production-ready?

Thanks again Romuald – much appreciated.

Oscar

[Romuald Quantin]

It is production ready?

Yes it is, it has been used on real-world project. Also on some very cutting-edge mobile projects.

And unit tested on all browsers until IE7.

About Angular Kendo UI, I've got some question.

It is probably possible to mix everything up, but I'm wondering why you would go that way.

Why using "angular kendo UI" and not "Kendo UI" if you want to use soma.js?

What is it that your are missing with angular.js that you need to look at something else like soma.js?

Angular is such a big machine.

I'd say, if you are looking for a framework where everything is baked in, go for angular.

If you are looking for performance, and more or less start from scratch, adding on the way the strict minimum you need to maintain performance (and not just test when it is too late) as close as possible to raw javascript, go for soma.js. This is especially true for mobile or applications with high data refresh rate (loops).

soma.js is doing less for you, so you will have either write things, or get external micro libraries if you don't want to. You could need one for ajax for example, this is not built it. You can easily use a stripped version of jquery or others:

http://microjs.com/

If you know already angular, that's good. If you don't but you are quite good with vanilla javascript, you will not have much to learn with soma.js.

The message is: soma.js will give you control, there's no magic, no data-binding, no auto-refresh / auto-render that you don't control yourself. But it is stil very powerful with the DI and tools it provides.

You will need to write things on your own, it doesn't mean it will take longer and you orchestrate yourself the structure of your application. This is needed IMO if you require high performance (mobile for example).

Does that help?

Romu

[Oscar Lito M Pablo]

Hi Romu,

Thanks for your objective explanation on how to approach the use of Soma.js vis-a-vis AngularJS and KendoUI. It's really very helpful. I'll take a closer look at Soma.js to see if the need for "lean-ness" edges out the power of AngularJS+KendoUI for my project.

Much appreciated,
Oscar