Good presentation Colin. I'm just getting started with Radium this week. Speaker tip: Always repeat the audience questions. This helps for at least three reasons: 1. So those viewing the video later (or those in the live audience who couldn't hear the question asker) know what question you're answering. 2. Repeating the question, even paraphrased, helps ensure you are answering the question that the asker asked (he/she will correct you if you paraphrased incorrectly). 3. It gives you a moment or two to contemplate the answer. Cheers!
nice! but i think we still need to be very careful and clear demarcation between dynamic styles required and static one. I think to have static selectors in a separate style sheet from performance perspective.
Doesn't sound too far off from PHP WordPress themes to me. I'll be interested to see an example where the gains are obvious and larger scale sites with many included 'widgets.' *Could* be exciting. Something like twitter, that seems to have very little UI modules or small react apps make sense now, but more examples would help get a real picture beyond the excitement. How can this use the cascade? I'm sure the holy grail is a combination and it's a bigger picture of building DOM based on need instead of if else templates.
if there was one piece of advice i'd give Colin, seeing a few of his presentations. try slowing down your speaking pace. in the mean time i'm going to try to watch it at .5x so that i myself don't feel anxious. :-P
Jon Madison as for me, I usually watch at 1.5x, so I saw your comment and decided to watch at normal speed. Halfway through I completely forgot this wasn’t 1.5x!
Inline styles, especially with React, are so much smoother and convenient to work with. It's very easy to manipulate it as well and have each style specific to each individual component.
It really depends on the kind of things you work on. I can imagine all this inline react stuff is best for large, complex applications with multiple state changes. Also, who hasn't learned Sass yet?
Good presentation Colin. I'm just getting started with Radium this week.
Speaker tip: Always repeat the audience questions. This helps for at least three reasons:
1. So those viewing the video later (or those in the live audience who couldn't hear the question asker) know what question you're answering.
2. Repeating the question, even paraphrased, helps ensure you are answering the question that the asker asked (he/she will correct you if you paraphrased incorrectly).
3. It gives you a moment or two to contemplate the answer.
Cheers!
Please make the animated GIFs stop.
nice! but i think we still need to be very careful and clear demarcation between dynamic styles required and static one. I think to have static selectors in a separate style sheet from performance perspective.
Css doesn't cause problems at all if you know how to use it properly
absolutely.. CSS isn't issue, lack of CSS knowledge is.
Doesn't sound too far off from PHP WordPress themes to me. I'll be interested to see an example where the gains are obvious and larger scale sites with many included 'widgets.' *Could* be exciting. Something like twitter, that seems to have very little UI modules or small react apps make sense now, but more examples would help get a real picture beyond the excitement. How can this use the cascade? I'm sure the holy grail is a combination and it's a bigger picture of building DOM based on need instead of if else templates.
if there was one piece of advice i'd give Colin, seeing a few of his presentations. try slowing down your speaking pace. in the mean time i'm going to try to watch it at .5x so that i myself don't feel anxious. :-P
Jon Madison as for me, I usually watch at 1.5x, so I saw your comment and decided to watch at normal speed. Halfway through I completely forgot this wasn’t 1.5x!
i hate CSS &'ve wanted to see it die 4 yrs (but myOpinionsAside, this is an excellent talk)
hot damn, Colin. hot damn XD
Inline styles, especially with React, are so much smoother and convenient to work with. It's very easy to manipulate it as well and have each style specific to each individual component.
So what you're saying Colin, is that if I haven't learned SASS by now, don't bother and just learn React.js?
It really depends on the kind of things you work on. I can imagine all this inline react stuff is best for large, complex applications with multiple state changes. Also, who hasn't learned Sass yet?
Awesome presentation! Learned a lot! :)
Daaaaaaaaang, that's awesome
Declarative is the best. You make the CSS gods mad