A little off-topic, but, how are developers staying up to date in the JavaScript community?
I've been an observer of the JavaScript eco-system and it is changing so rapidly, particularly in the MVC space (i.e. SproutCore 1.xx, SproutCore 2.xx, BackBone.js, Spine.js, Knockout.js, etc etc).
It's so easy to get stuck in analysis paralysis. Is there a discussion list or a website that can help make some decisions for my next hack project?
I'm coming from a heavy backend background and I think the JavaScript MVC space warrants a hack-day project :)
Most don't. Just keeping up with new DOM additions is difficult enough. Instead you pick a project and follow it until you run into problem area it can't solve and then move on to another.
I'm not sure why you are getting downvoted. Although I don't feel you necessarily need to share it on HN, the best way is the build some simple apps and find out for yourself what the libraries are all about.
It's not downvoted right now, so I think most people get what I'm saying. I think it's important to get feedback from the community, but I agree you don't need to show everything to HN, as most random projects won't get a lot of attention here-- and I think you've picked out my real point that no blog is a substitute for getting your hands dirty.
I've been an observer of the JavaScript eco-system and it is changing so rapidly, particularly in the MVC space (i.e. SproutCore 1.xx, SproutCore 2.xx, BackBone.js, Spine.js, Knockout.js, etc etc).
It's so easy to get stuck in analysis paralysis. Is there a discussion list or a website that can help make some decisions for my next hack project?
I'm coming from a heavy backend background and I think the JavaScript MVC space warrants a hack-day project :)