Talk comments

Anonymous at 22:12 on 21 May 2014

Great info, but a longer session with more examples would have made it even better

October is still in beta (definitely not production ready), and is a very new product (has rough edges and odd concepts at times), so like any open source project, input from the community is much appreciated. At the beginning of the session, I mentioned both of those aspects and that this session would be largely looking at a different way to do content management but it's certainly not for everyone. I also talked about some alternative CMS projects with other approaches.

Sorry you felt bored, Katherine! For more information on the file-based approach (which has pros and cons for sure), see http://octobercms.com/blog/post/getting-back-to-basics and feel free to contribute your feedback and questions directly on their forum at http://octobercms.com/forum/chan/october-helpsupport

Bradley, thanks for your feedback! Check out http://octobercms.com/features for an overview that might clarify the odd approach they've taken. May or may not clear things up. Also, check out the forums.

Thanks all for attending! Enjoyed the conversations after about alternative CMS approaches.

Great talk guys! Any chance y'all can upload the slides with examples? I got the server installed and ready to go!

Great talk! Can you fix the link to the slides, its not correct.
Thanks

I enjoyed this introduction to PHPIDS, it's not something I'd really considered as part of my security stack.

Lots of great stuff in here. Fun and funny talk that gets the message across clearly.

Fantastic talk. Great speaker obviously both very knowledgeable and very passionate about the topic. Learned TONS.

Every so often, I have to remind myself how exactly JS does what it does. This talk was a refreshing way to do just that. Tough to cover the topics in just an hour; found that some of the initial examples were difficult to follow but soon made sense as they were built upon.

One thing to add (though, again, difficult in an hour time slot) would be a quick example of the module pattern. Was mentioned at least twice in the talk but not really explained how it fits into JS development or why.

Maybe it's just me, but "this" is far more confusing than the variable scope, so I would have allocated less time to discussing scope. Also, you rely on an understanding of objects in order to discuss "this", but don't officially explain them until later in the talk. You could order it as: (1) scope (but much shorter), (2) object literals (quick mention), (3) the concept of a function as something which can be assigned (another quick mention), (4) context, as you had it, and then (5) prototyping (slightly shorter than you had it due to reorganization). That might provide better scaffolding.

But given (1) that you deride prototyping and (2) the time it takes to explain it, perhaps find a way to quickly convey its very basic concept and complexity, dismiss it, and replace that content with a description of the module pattern which you laud.

Mind blown. Lots of interesting uses for this comingin the future. Great work guys!