This talk was quite confusing, it was hard to understand what was cool new ES6 stuff and what was other tools and libraries. Needed to explain one topic in depth instead of trying to show many things with one code snippet each.
Love your passion. But, if one wasn't already near the bleeding edge this talk was very difficult to follow and understand. At times hard to tell when you were referring to ES6 vs an included library or something you wrote.
I enjoy Nate's talks, but I have to admit this talk was a little meandering and could have been better served by a little more focus.
I would have prefered seeing something more functional, instead of showing a work in progress. Perhaps a little less complex code base may have served as better examples to begin with, and then perhaps end with "look at this cool thing I made" it's HUGE and AWESOME!
Still, I love JavaScript and learning about the new ES6, and thus still enjoyed this talk.
I think this talk was interesting from a kind of mad scientist perspective. It probably has more potential at Javascript conferences but needs some work. Overwhelming, at the current time, most PHP devs probably know very little about the basics of ES6 except that it is the next rev of Javascript. If the talk was reorganized and the concepts were more flushed out then it would probably help. I think it would be beneficial to discuss, at the beginning of the talk, what you're trying to teach or discuss with the audience. I'd leave the demo for the end.
FWIW, I've worked with Angular 2 a bit and am familiar with ES6 concepts but still had trouble finding what the talk was attempting to teach the audience. I think the app looks really cool and am excited to see the ObjectRegistry open sourced.
My expectations for this talk were that I would learn what was new is ES6. The main things I got from this talk were that you could do OO and functional programming in ES6, but that functional programming was superior.
Early on in the talk the speaker asked the audience if anybody was using dependency injection or if they were using global variables. He then commented that the second group that raised their hands, and anybody who didn't, "was doing it wrong." That might be technically correct, but it didn't feel like a very good way to raise people up so they feel like they are leaving the talk having learned more when the talk started.
Felt like the speaker assumed that the audience knew as much as he did about the subject, in which case, why would we need to attend the talk? The example shown was also very complicated, and it was unclear which elements of the example had anything to do with ES6.
Maybe this is on me, but I felt pretty low after listening to this talk, and I skipped the Saturday social hour because this talk left such a bad taste in my mouth. Really disappointed and mildly traumatized by the experience.
This talk included some content that was very challenging and interesting for me. I like to see a couple talks at any given conference that stretch my awareness of concepts and techniques. This was one of them. Very cool app he showed off and examples of JS doing sophisticated things.
It's true that the talk could be better organized and presented. I feel like we saw the finished product a lot, but not the building blocks that led up to it. Needs more of a narrative, like "this was my problem, here's how I would have done it the old way, here are the steps I took to do the new way, now look at this cool result." Reorganization might mean presenting a little less material overall, but it's probably a good tradeoff.
I feel that there was a disconnect between the content presented during this talk and what it promised to deliver in its description. Like several others have already mentioned, I thought the shift to discussing functional programming concepts when I was expecting more of an overview of what can be achieved with ES6 was difficult to adapt to. That said, Nate is very clearly adept at working with this language, though this presentation could benefit from being split up into several different talks (maybe one on new features, one on tools and libraries, and one on functional programming) that each provide a specific focus.
Nate's workflow application is beautiful and impressive, and the pseudo-in-memory-database project will see a lot of use when it's been open-sourced. That said, the presentation itself didn't clearly distinguish the nifty libraries from the nifty paradigms from the transpiled pseudo-languages from ES6. It was more "Look how I built this sophisticated application" and less "Look at this new stuff in ES6".
Based on the topic, I was expecting to hear more about ES6 features than I did. There was too much interjection of other libraries and language features to make that clear. I don't want to rate this poorly as a "JS talk at a PHP conf" because to be clear I'm infatuated with JS. But a poor presentation reflects negatively on the subject and reinforces the meme.
It was clear that Nate is very knowledgeable and I'm sure would have made a great presentation if there had been more structure and clarity.
The demo application was awesome, but I feel this talk suffered from trying to stuff 6 talks worth of information into a 45 minute session. Nate tried to cover TypeScript, React, ES6, Functional Programming, JavaScript architecture and a very cool in-memory object registry and ended up with a talk that left me asking a ton of questions with no time left for any answers.
I feel like this would have been a highly challenging talk to keep up with even at a JS conference where you could reasonably expect most attendees to be at least passingly familiar with most of the tools used.
Not the best talk. I would have liked a little more background and context before just diving in. I really just came to this hoping to get some info on what was new and what might be a killer feature I couldn't live without.
I got lost a few times but that's probably because I'm new to some of the concepts. However I can't help but wonder if the code examples wouldn't have benefited from comparing old style JS with code examples that use the new features.
Overall though, I think this was a tricky (and very important) subject and the speaker took a decent crack at trying to explain it.
Comments
Comments are closed.
This talk was quite confusing, it was hard to understand what was cool new ES6 stuff and what was other tools and libraries. Needed to explain one topic in depth instead of trying to show many things with one code snippet each.
Love your passion. But, if one wasn't already near the bleeding edge this talk was very difficult to follow and understand. At times hard to tell when you were referring to ES6 vs an included library or something you wrote.
I enjoy Nate's talks, but I have to admit this talk was a little meandering and could have been better served by a little more focus.
I would have prefered seeing something more functional, instead of showing a work in progress. Perhaps a little less complex code base may have served as better examples to begin with, and then perhaps end with "look at this cool thing I made" it's HUGE and AWESOME!
Still, I love JavaScript and learning about the new ES6, and thus still enjoyed this talk.
Thanks for the talk Nate!
This talk got a little deep a little fast for me - some less complex examples would have helped get my head around the concepts.
I think this talk was interesting from a kind of mad scientist perspective. It probably has more potential at Javascript conferences but needs some work. Overwhelming, at the current time, most PHP devs probably know very little about the basics of ES6 except that it is the next rev of Javascript. If the talk was reorganized and the concepts were more flushed out then it would probably help. I think it would be beneficial to discuss, at the beginning of the talk, what you're trying to teach or discuss with the audience. I'd leave the demo for the end.
FWIW, I've worked with Angular 2 a bit and am familiar with ES6 concepts but still had trouble finding what the talk was attempting to teach the audience. I think the app looks really cool and am excited to see the ObjectRegistry open sourced.
My expectations for this talk were that I would learn what was new is ES6. The main things I got from this talk were that you could do OO and functional programming in ES6, but that functional programming was superior.
Early on in the talk the speaker asked the audience if anybody was using dependency injection or if they were using global variables. He then commented that the second group that raised their hands, and anybody who didn't, "was doing it wrong." That might be technically correct, but it didn't feel like a very good way to raise people up so they feel like they are leaving the talk having learned more when the talk started.
Felt like the speaker assumed that the audience knew as much as he did about the subject, in which case, why would we need to attend the talk? The example shown was also very complicated, and it was unclear which elements of the example had anything to do with ES6.
Maybe this is on me, but I felt pretty low after listening to this talk, and I skipped the Saturday social hour because this talk left such a bad taste in my mouth. Really disappointed and mildly traumatized by the experience.
This talk included some content that was very challenging and interesting for me. I like to see a couple talks at any given conference that stretch my awareness of concepts and techniques. This was one of them. Very cool app he showed off and examples of JS doing sophisticated things.
It's true that the talk could be better organized and presented. I feel like we saw the finished product a lot, but not the building blocks that led up to it. Needs more of a narrative, like "this was my problem, here's how I would have done it the old way, here are the steps I took to do the new way, now look at this cool result." Reorganization might mean presenting a little less material overall, but it's probably a good tradeoff.
I feel that there was a disconnect between the content presented during this talk and what it promised to deliver in its description. Like several others have already mentioned, I thought the shift to discussing functional programming concepts when I was expecting more of an overview of what can be achieved with ES6 was difficult to adapt to. That said, Nate is very clearly adept at working with this language, though this presentation could benefit from being split up into several different talks (maybe one on new features, one on tools and libraries, and one on functional programming) that each provide a specific focus.
Nate's workflow application is beautiful and impressive, and the pseudo-in-memory-database project will see a lot of use when it's been open-sourced. That said, the presentation itself didn't clearly distinguish the nifty libraries from the nifty paradigms from the transpiled pseudo-languages from ES6. It was more "Look how I built this sophisticated application" and less "Look at this new stuff in ES6".
Based on the topic, I was expecting to hear more about ES6 features than I did. There was too much interjection of other libraries and language features to make that clear. I don't want to rate this poorly as a "JS talk at a PHP conf" because to be clear I'm infatuated with JS. But a poor presentation reflects negatively on the subject and reinforces the meme.
It was clear that Nate is very knowledgeable and I'm sure would have made a great presentation if there had been more structure and clarity.
The demo application was awesome, but I feel this talk suffered from trying to stuff 6 talks worth of information into a 45 minute session. Nate tried to cover TypeScript, React, ES6, Functional Programming, JavaScript architecture and a very cool in-memory object registry and ended up with a talk that left me asking a ton of questions with no time left for any answers.
I feel like this would have been a highly challenging talk to keep up with even at a JS conference where you could reasonably expect most attendees to be at least passingly familiar with most of the tools used.
Not the best talk. I would have liked a little more background and context before just diving in. I really just came to this hoping to get some info on what was new and what might be a killer feature I couldn't live without.
I got lost a few times but that's probably because I'm new to some of the concepts. However I can't help but wonder if the code examples wouldn't have benefited from comparing old style JS with code examples that use the new features.
Overall though, I think this was a tricky (and very important) subject and the speaker took a decent crack at trying to explain it.