Looking for KnockoutJS developer.

[Jevgenij Dmitrijev]

Hello,

this is the job description:
https://www.linkedin.com/jobs/view/2280174843/

Preferable location: Lithuania. 

You would help us to maintain our old code, while we move to ReactJS and eventually drag you to become ReactJS developer.

Please apply via link, or contact me.

Thank you!

[Julio Di Egidio]

Drag me??  For your info, MCV with Knockout or similar is the right architecture and light years better than any upside-down React-like aberration, aka the layering fuckup.

Which is a piece of free consulting advice.  Another one is for your managers: look up Dunning-Kruger...

Julio

[Julio Di Egidio]

> ... For your info, MCV with Knockout or similar is ...

MVC...

Julio

[Gunnar Liljas]

Knockout is usually MVVM, though. Not MVC.

/G

--
You received this message because you are subscribed to the Google Groups "KnockoutJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to knockoutjs+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/knockoutjs/6c64b4cd-c811-4e81-b3a5-14d07dd97d19n%40googlegroups.com.

[Julio Di Egidio]

You can do whatever you like with KO, including just using the observables, and not even necessarily in the UI: that's not the point, the point was about design/architectural patterns.

Moreover, the fact that in the docs they say KO=MVVM is a *mistake* and, partly, a marketing stunt, since MVVM was the hit parade of cool few years ago, thanks to the big vendors.  But, as far as patterns go, it is *MVC* that is the most general and most fundamental pattern (for "interactivity"), encompassing MVVM, MVP, and all the others, which are rather simplifications/specializations of MVC...

Julio