52 min listen
JSJ 335: “CanJS 4.0” with Justin Meyer
ratings:
Length:
54 minutes
Released:
Oct 16, 2018
Format:
Podcast episode
Description
Panel:
Aimee Knight
Charles Max Wood (DevChat TV)
Christopher Ferdinandi (Boston)
Joe Eames
Special Guests: Justin Meyer
In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out!
Show Topics:
0:58 – We had you on Episode 202.
1:14 – Chuck: Can you tell everyone who you are?
1:20 – Justin tells us his background.
1:50 – Chuck.
1:58 – Justin.
2:06 – Chuck: Can you give us an introduction to what CanJS 4.0?
2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well.
2:44 – Panelist.
2:49 – Justin.
2:55 – Panelist: What is the current...
3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories.
Justin continues to talk about the differences/similarities between the different versions.
4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions.
1.) Where is the core strength of JS and its user base?
2.) What is like to be the CanJS when everyone is talking about the other programs?
5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it.
Justin answers the second question.
8:44 – Panelist: You mentioned two things.
9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network.
10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program.
10:26 – Now I am intrigued.
10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often.
10:54 – Aimee.
10:58 – Justin: Deep inheritance is definitely a problem and it can create...
11:13 – Aimee.
11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road.
13:00 – Aimee.
13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS.
13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)...
If you look at React’s statistics – more than 50% doesn’t use any state management.
16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...”
16:43 – Justin: The last coolest thing I’ve done is...
18:02 – Justin continues.
18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native...
18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without.
19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line?
21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the
Aimee Knight
Charles Max Wood (DevChat TV)
Christopher Ferdinandi (Boston)
Joe Eames
Special Guests: Justin Meyer
In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out!
Show Topics:
0:58 – We had you on Episode 202.
1:14 – Chuck: Can you tell everyone who you are?
1:20 – Justin tells us his background.
1:50 – Chuck.
1:58 – Justin.
2:06 – Chuck: Can you give us an introduction to what CanJS 4.0?
2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well.
2:44 – Panelist.
2:49 – Justin.
2:55 – Panelist: What is the current...
3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories.
Justin continues to talk about the differences/similarities between the different versions.
4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions.
1.) Where is the core strength of JS and its user base?
2.) What is like to be the CanJS when everyone is talking about the other programs?
5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it.
Justin answers the second question.
8:44 – Panelist: You mentioned two things.
9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network.
10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program.
10:26 – Now I am intrigued.
10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often.
10:54 – Aimee.
10:58 – Justin: Deep inheritance is definitely a problem and it can create...
11:13 – Aimee.
11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road.
13:00 – Aimee.
13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS.
13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)...
If you look at React’s statistics – more than 50% doesn’t use any state management.
16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...”
16:43 – Justin: The last coolest thing I’ve done is...
18:02 – Justin continues.
18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native...
18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without.
19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line?
21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the
Released:
Oct 16, 2018
Format:
Podcast episode
Titles in the series (100)
Episode 6: 006 JSJ Chrome Dev Tools with Paul Irish by JavaScript Jabber