Novice, Intermediate, Expert ...

[Alexander Praetorius]

I really enjoy the drips of javascript i receive and sometimes they teach me something.
Other times, i think, they are important to be known, but i find myself knowing them already.
If the drips would become more challenging and advanced, maybe that would be bad for people who are new to javascript.
But i would like to join an "intermediate drips" mailinglist and eventually raise to "expert drips list" when i figure that intermediate also becomes simple enough for me.

[Joshua Clanton]

Hey Alexander,

I think that's a great idea. Unfortunately, it's also hard to consistently estimate what is beginner vs intermediate with the wide range of backgrounds people have. And as of right now I don't have the bandwidth to build up the necessary backlog for something like that.

However, if you have specific intermediate/expert topics to suggest, I'd love to hear them!

Thanks,

Josh Calnton

[Phillip Senn]

Maybe you could crowd source it.

At the end of the email ask two questions:

1. Do you like this tip?

2. What level is this tip (1=Beginner, 2=Intermediate, 3=Advanced)

[tomByrer]

Kinda hard to peg levels sometimes.
Some are obvious to level; like callbacks are at least intermediate.
You'd think that minifing files would be something that beginners would grasp, but I've seen many 'experts' shun minifing..

[Phillip Senn]

Each person would define their own interpretation as to whether a feature is a beginner feature or not.

I think it would work.

Take wikipedia as an example: on the surface, it's not possible for Wikipedia to work.  Too many people would vandalize it.

And yet it does work.  Inexplicably.

I think crowd sourcing amongst thoughtful people could work.

If you're a novice, then you are trying to gauge where to start.

Looking a table that says that x people think it's beginner level assures you that it's worth learning.

[Matt Mischewski]

What about functional vs object oriented approach related to creating rich models / data interface?

As reference there is this approach, in coffeescript but you'll get the idea

https://github.com/ProLoser/AngularJS-ORM

And on the same subject the comments at the bottom of this article are particularly interesting, but lack a rival implementation to fully appreciate the strengths and weaknesses

http://blog.shinetech.com/2014/02/28/rich-object-models-and-angular-identity-maps/

The question I have is related whether or not using bacon.JS like this fits? What I understand of functional programming (which is not enough) is that data should populate POJO's and the functions would massage the data to desired outputs.

Following on from that or perhaps a pre-cursor it would be great to understand more about how bacon.js is put together and effective implementation strategies for streaming events / creating bacon.bus and how  browserification of node.js stream would provide an alternative to bacon.js?

https://github.com/dominictarr/event-stream

Then perhaps this could lead to an explanation of outpace sees clojuescript as advantageous to solving complex problems?

http://www.outpace.com/career/

Hope that makes sense, as obviously doesn't fully make sense to me.

Cheers

Matt

[Matt Mischewski]

Add highland into the mix

http://highlandjs.org/