Enfocus and Kioo

121 views
Skip to first unread message

Boris Kourtoukov

unread,
Feb 1, 2014, 4:01:44 AM2/1/14
to enf...@googlegroups.com
Hi Creighton,

As I am sure you have noticed over the past while I am still in the process of really getting efficient with Enfocus.
I chose it as my primary way of working with elements in the DOM for a few (albeit quite minor) projects and haven't had time to focus on any of the other options available. 

I am mostly interested in the core.async UI development that sprung up since last summer and have been using Enfocus to interweave my DOM work with that. Just wondering if a better path now would be to divert focus on OM(+async) and Kioo instead of Enfocus and just core.async if I want to seriously go further in this direction?

I have been following David Nolen's tutorial and posts on OM, but can't currently apply it to the aforementioned projects as the way everything is structured looks like it would demand a heavy rewrite.

I know this sounds like a 'tools first' approach to working but I am really trying to make sure I understand the tools before I end up trying to make a complete mess of bigger front-end applications.

Thanks.

Creighton Kirkendall

unread,
Feb 1, 2014, 7:59:28 AM2/1/14
to Enfocus
Boris,
Great question! In a world were even your language is considered bleeding edge and the ecosystem is evolving rapidly where do you concentrate your time.  At this point I see Enfocus as well tested software with proven design patterns.  Om and Kioo not so much.  I love the ideas of Om but I am not sure what patterns are needed for the model to scale to large applications.  Personally, I am playing around with Om and Reagent but if I had to do a project for a client it would be Enfocus.   Kioo is very new and the api structure is still evolving and may end up closer to enliven. Then we have enliven whose goals are large and if achieved make Om obsolete by building a pure clojure reactive core.   Enfocus is learning a bit from these projects and others and recently we got smart view bindings that borrowed some ideas from Om. Long term, as in a few years from now, I do see reactive programming style as dominant force but have no idea if Om, Kioo, or Enliven will be the technologies driving it.  Right now I certainly wouldn't rewrite apps in those technologies but i might start small ones to play around in them.  I hope that helped.

CK 


--
 
---
You received this message because you are subscribed to the Google Groups "Enfocus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enfocus+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

ckirkendall

unread,
Feb 1, 2014, 8:28:34 AM2/1/14
to enf...@googlegroups.com
Predictions from looking over the bleeding edge.  :)

Om - Will evolve into something close to a view layer + datomic interface to the app state in the browser.  It will be complex to use directly but will become the base that many will build easier to use frameworks on.
Kioo - Will continue to evolve to provide an enliven like interface on top of Om.
Enliven - Will eventually reach it goals but will never reach the market share of Om.  It will be awesome but very opinionated. I will be difficult for people understand its underpinnings and its pure view on development.
Enfocus - Will continue to improved and in both structure and performance.  Ideas will be poached from Kioo and others.
Core.asyc - Will underlie everything! People will figure out many ways to use it that we haven't thought of yet.  These ideas will most likely eclipse all projects above.  This is the game changer.  Learn it and love it!

CK

kinleyd

unread,
Feb 1, 2014, 1:33:43 PM2/1/14
to enf...@googlegroups.com
Thanks Creighton,

Like many others, I've felt the wave of excitement that core.async has brought and have wondered how the dust is going to settle given sufficient time. I'm particularly keen on its long term impact on rich client development which promises to include vastly improved performance and development approaches.

Like Boris, I've been trying to figure out which of the approaches currently available best embraces the potential that core.async has unleashed, and from what I understand you are saying, it looks like I'll have to take a good hard look at all of them. Sound's like fun. :)

Boris Kourtoukov

unread,
Feb 1, 2014, 3:38:53 PM2/1/14
to enf...@googlegroups.com
Thanks taking the time to put together this overview. Ill continue working in Enfocus and try my best to keep up with OM and Kioo as things move forward.

And I 100% that Core.Async is the game changer, it's what moved me out of my comfort zone and into ClojureScript in the first place last summer. :) Can't wait to have a better hang of it haha.

-Boris
Reply all
Reply to author
Forward
0 new messages