WEBVTT

1
00:00:01.080 --> 00:00:02.960
<v Speaker 1>How'd you like to listen to dot net rocks with

2
00:00:03.040 --> 00:00:07.839
<v Speaker 1>no ads? Easy? Become a patron for just five dollars

3
00:00:07.919 --> 00:00:10.800
<v Speaker 1>a month. You get access to a private RSS feed

4
00:00:10.800 --> 00:00:14.240
<v Speaker 1>where all the shows have no ads. Twenty dollars a month,

5
00:00:14.279 --> 00:00:16.879
<v Speaker 1>we'll get you that and a special dot net Rocks

6
00:00:16.960 --> 00:00:20.960
<v Speaker 1>patron mug. Sign up now at Patreon dot dot NetRocks

7
00:00:21.120 --> 00:00:34.200
<v Speaker 1>dot com.

8
00:00:34.359 --> 00:00:37.840
<v Speaker 2>Hey, and welcome back to dot net Rocks. I'm Carl Franklin.

9
00:00:37.479 --> 00:00:39.439
<v Speaker 3>And I'm Richard Campbell, episode two.

10
00:00:39.240 --> 00:00:41.399
<v Speaker 2>Thousand and one. It's going to be good if I

11
00:00:41.439 --> 00:00:43.399
<v Speaker 2>can live through it. As you can tell.

12
00:00:43.759 --> 00:00:46.439
<v Speaker 3>Yeah, you're still battling that cold, and of course a

13
00:00:46.479 --> 00:00:48.320
<v Speaker 3>bit of time shifting. So the cold you may have

14
00:00:48.399 --> 00:00:52.399
<v Speaker 3>heard a few weeks ago is the same cold. Yeah,

15
00:00:52.439 --> 00:00:55.679
<v Speaker 3>in between, you know, there's been other shows. It's crazy.

16
00:00:56.039 --> 00:00:58.840
<v Speaker 2>Uh, And I picked us up while I was in Seattle, right,

17
00:00:58.880 --> 00:01:01.679
<v Speaker 2>So I'm not really sure you know how long it's

18
00:01:01.679 --> 00:01:03.600
<v Speaker 2>going to take. But I know it's not the flu,

19
00:01:04.120 --> 00:01:05.680
<v Speaker 2>and I know it's not COVID, So.

20
00:01:05.760 --> 00:01:07.879
<v Speaker 3>There you go. Yeah, that's important. It's just a cold.

21
00:01:08.040 --> 00:01:09.280
<v Speaker 3>It's just a springtime cold.

22
00:01:09.319 --> 00:01:11.319
<v Speaker 2>It's a cold. It's gonna last for a while, and

23
00:01:11.359 --> 00:01:13.079
<v Speaker 2>I hope I make it to the next gig.

24
00:01:13.640 --> 00:01:15.799
<v Speaker 3>I hope so too. All right, we got more shows

25
00:01:15.799 --> 00:01:16.439
<v Speaker 3>to record.

26
00:01:16.359 --> 00:01:22.079
<v Speaker 2>Yeah, this being episode two thousand and one a Space Odyssey.

27
00:01:22.200 --> 00:01:26.280
<v Speaker 2>Oh boy, let's talk about what happened in two thousand

28
00:01:26.319 --> 00:01:29.359
<v Speaker 2>and one. The big one, Yeah, of course is September

29
00:01:29.400 --> 00:01:32.079
<v Speaker 2>eleventh attacks. Yeah, not much we can say about that

30
00:01:32.079 --> 00:01:33.439
<v Speaker 2>that hasn't already been said.

31
00:01:33.640 --> 00:01:36.280
<v Speaker 3>No, I think it's it's all been said, but it

32
00:01:36.319 --> 00:01:39.079
<v Speaker 3>overwhelms a whole lot of other news that went on there.

33
00:01:39.239 --> 00:01:42.400
<v Speaker 3>That was also the year the Enron collapse. Mm hmm,

34
00:01:43.000 --> 00:01:47.200
<v Speaker 3>you know that sort of accounting scandal and you know,

35
00:01:47.519 --> 00:01:49.760
<v Speaker 3>company worth billions at the beginning of the year, by

36
00:01:49.799 --> 00:01:51.959
<v Speaker 3>the end of the week year is bankrupting, gone and

37
00:01:52.799 --> 00:01:55.680
<v Speaker 3>actually destroyed Arthur Anderson, like one of the largest accounting

38
00:01:55.680 --> 00:01:57.560
<v Speaker 3>firms in the world, who was supposed to be the

39
00:01:57.560 --> 00:01:59.719
<v Speaker 3>odded body that made sure that what they were saying

40
00:01:59.760 --> 00:02:02.079
<v Speaker 3>was true and what they were saying was not true

41
00:02:02.120 --> 00:02:04.159
<v Speaker 3>and so yeah, they literally were dismantled for it.

42
00:02:04.879 --> 00:02:09.479
<v Speaker 2>And the war in Afghanistans started shortly thereafter nine to eleven.

43
00:02:09.599 --> 00:02:12.000
<v Speaker 3>Yeah, and Bush had just gotten into office, like it's yeah,

44
00:02:12.039 --> 00:02:14.199
<v Speaker 3>remember when it started out like there was seemed to

45
00:02:14.240 --> 00:02:16.360
<v Speaker 3>be like a conflict with China. There was the incident

46
00:02:16.879 --> 00:02:19.879
<v Speaker 3>with the with the US aircraft and a fighter jet.

47
00:02:20.319 --> 00:02:22.319
<v Speaker 3>It's like this, this is what's going on. And then

48
00:02:22.360 --> 00:02:25.039
<v Speaker 3>of course in September hits and everything changes.

49
00:02:25.280 --> 00:02:29.879
<v Speaker 2>Yeah, nasty. There's a lot of other international conflicts. I

50
00:02:29.879 --> 00:02:33.199
<v Speaker 2>want to just mention the standoffs between Indian and Pakistan,

51
00:02:34.719 --> 00:02:38.080
<v Speaker 2>continued violence in the Second Intifada, in the start of

52
00:02:38.319 --> 00:02:43.599
<v Speaker 2>conflicts in Macedonia. Just I don't know, maybe this was

53
00:02:43.639 --> 00:02:49.439
<v Speaker 2>a millennial angst kind of you know, come to fruition.

54
00:02:49.680 --> 00:02:50.039
<v Speaker 2>I don't know.

55
00:02:50.120 --> 00:02:52.039
<v Speaker 3>This is all the fallout of the collapse of the

56
00:02:52.479 --> 00:02:53.919
<v Speaker 3>of the Eastern Bloc, right.

57
00:02:53.919 --> 00:02:57.319
<v Speaker 2>Yeah, much, Yeah, go ahead. Let's talk about space and

58
00:02:57.360 --> 00:02:58.759
<v Speaker 2>technology first.

59
00:02:58.800 --> 00:03:02.639
<v Speaker 3>Javentin space. I think of importance in February when the

60
00:03:02.879 --> 00:03:06.400
<v Speaker 3>near Shoemaker spacecraft, which has been orbiting around four thirty

61
00:03:06.400 --> 00:03:10.199
<v Speaker 3>three arrows an asteroid, actually lands on the asteroid. No,

62
00:03:10.319 --> 00:03:13.400
<v Speaker 3>it did not have landing gear, but gravity was so

63
00:03:13.639 --> 00:03:16.400
<v Speaker 3>very low that it was able to maneuver precisely into

64
00:03:16.439 --> 00:03:20.680
<v Speaker 3>this little saddle region and actually touch the asteroid successfully.

65
00:03:22.599 --> 00:03:27.639
<v Speaker 3>That same month, the Atlantis Space Shuttle carries the Destinary

66
00:03:27.680 --> 00:03:30.319
<v Speaker 3>Laboratory module to the International Space station, so this is

67
00:03:30.319 --> 00:03:34.199
<v Speaker 3>the big one, the large module. The most interesting thing

68
00:03:34.240 --> 00:03:37.159
<v Speaker 3>in that event is during this space walks to hook

69
00:03:37.240 --> 00:03:39.280
<v Speaker 3>that module up, so they actually have to get it,

70
00:03:39.680 --> 00:03:41.840
<v Speaker 3>go into their space suits, and go outside to hook

71
00:03:41.919 --> 00:03:45.800
<v Speaker 3>up lines. On the outside, there's an ammonia leak and

72
00:03:46.800 --> 00:03:50.479
<v Speaker 3>astronaut Robert Kirbeam ends up being covered in an inch

73
00:03:50.680 --> 00:03:56.560
<v Speaker 3>of frozen ammonia, so he's outside the spaceship. He said, yeah,

74
00:03:56.639 --> 00:04:00.439
<v Speaker 3>this is not good, and ammonia is quite toxic. They

75
00:04:00.479 --> 00:04:03.360
<v Speaker 3>can't carry it into the space station now, so he's

76
00:04:03.400 --> 00:04:06.319
<v Speaker 3>basically stuck out there for nineteen minutes for a full

77
00:04:06.479 --> 00:04:09.520
<v Speaker 3>orbit until they get around into the Sun's side again,

78
00:04:09.800 --> 00:04:12.639
<v Speaker 3>where the sun will evaporate all of the ammonia off

79
00:04:12.680 --> 00:04:15.879
<v Speaker 3>of him, so he can't see things we take for granted,

80
00:04:16.000 --> 00:04:20.560
<v Speaker 3>yes the sun. Now he's not stuck, he's not paralyzed

81
00:04:20.560 --> 00:04:23.680
<v Speaker 3>in his suit or anything. It's just crystals covering him.

82
00:04:23.759 --> 00:04:27.000
<v Speaker 3>So then they get him too the airlock and it's

83
00:04:27.040 --> 00:04:29.079
<v Speaker 3>the old airlock because they haven't flown the new one

84
00:04:29.160 --> 00:04:31.040
<v Speaker 3>yet so it's not very big and put him in

85
00:04:31.040 --> 00:04:34.040
<v Speaker 3>the airlock pressurized it depressurized a couple times to try

86
00:04:34.079 --> 00:04:36.639
<v Speaker 3>and blow all the ammonia that's left on him out

87
00:04:36.879 --> 00:04:38.639
<v Speaker 3>before they actually get inside, and it turns out to

88
00:04:38.680 --> 00:04:41.040
<v Speaker 3>be a non event. But for a moment there, the

89
00:04:41.160 --> 00:04:44.839
<v Speaker 3>things were really serious. Yeah, following month, in March, the

90
00:04:44.920 --> 00:04:47.480
<v Speaker 3>Mere space station is deorbited. This has been decided the

91
00:04:47.519 --> 00:04:52.480
<v Speaker 3>following the previous year in November, the Russian Federation just

92
00:04:52.519 --> 00:04:54.759
<v Speaker 3>did not have the money to operate both mir and

93
00:04:54.839 --> 00:04:58.439
<v Speaker 3>the International Space Station requirements they had, plus, Mirror was

94
00:04:58.759 --> 00:05:01.079
<v Speaker 3>very old at that point was a ten year space

95
00:05:01.120 --> 00:05:04.199
<v Speaker 3>station that was now fifteen years old. In fact, the

96
00:05:04.319 --> 00:05:08.040
<v Speaker 3>deorbit was delayed because of gyro failures on the mirrorment

97
00:05:08.120 --> 00:05:10.759
<v Speaker 3>that they couldn't dock the progress booster to it to

98
00:05:11.199 --> 00:05:14.560
<v Speaker 3>deorbit it, and they didn't want they It was already

99
00:05:14.600 --> 00:05:17.360
<v Speaker 3>low enough that if they didn't boost it immediately it

100
00:05:17.399 --> 00:05:18.879
<v Speaker 3>was going to deorbit by the end of March on

101
00:05:18.920 --> 00:05:21.759
<v Speaker 3>its own, out of control a la sky Lab, and

102
00:05:21.800 --> 00:05:26.879
<v Speaker 3>nobody wanted that. So instead they brought a progress booster

103
00:05:27.040 --> 00:05:28.959
<v Speaker 3>up to it, and then in March deliberately drever it

104
00:05:29.000 --> 00:05:31.839
<v Speaker 3>so that it came down near Fiji into the South

105
00:05:31.879 --> 00:05:36.399
<v Speaker 3>Atlantic I mean sad, but also it was time, you know,

106
00:05:36.480 --> 00:05:39.319
<v Speaker 3>these space stations don't last forever. They met the materials

107
00:05:39.360 --> 00:05:41.920
<v Speaker 3>wear out, the equipment wear is out, and the design

108
00:05:42.040 --> 00:05:45.040
<v Speaker 3>of those stations, the Russian design, a lot of those

109
00:05:45.040 --> 00:05:47.600
<v Speaker 3>parts weren't replaceable. You just had to replace the whole module.

110
00:05:47.639 --> 00:05:51.240
<v Speaker 3>So it just wasn't worthwhile. Plenty of Space Shuttle missions

111
00:05:51.240 --> 00:05:54.240
<v Speaker 3>to the ISS to do resupply and so forth, including

112
00:05:54.480 --> 00:05:57.759
<v Speaker 3>Chris Hadfield, the Canadian very famous now Fairies Game is

113
00:05:57.839 --> 00:06:01.560
<v Speaker 3>Canadian astronaut. At the time, it was his first trip

114
00:06:01.600 --> 00:06:03.959
<v Speaker 3>to the International Space Station and he would be the

115
00:06:04.000 --> 00:06:06.759
<v Speaker 3>first Canadian spacewalker ever. He would later go on to

116
00:06:06.800 --> 00:06:07.759
<v Speaker 3>command the space station.

117
00:06:08.319 --> 00:06:10.720
<v Speaker 2>In the first person spaced David Bowie sung in space.

118
00:06:10.800 --> 00:06:14.959
<v Speaker 3>Yeah, that's right. Also, the Mars Odyssey mission was launched

119
00:06:14.959 --> 00:06:16.879
<v Speaker 3>in April. This we'll get and we'll get to Mars

120
00:06:16.879 --> 00:06:20.639
<v Speaker 3>in October, and it's one of the telemetry satellites and

121
00:06:20.879 --> 00:06:26.360
<v Speaker 3>image surface map aerial mappers orbiters. The big airlock for

122
00:06:26.360 --> 00:06:30.120
<v Speaker 3>the National Space Station arrives in July, the question joined

123
00:06:30.199 --> 00:06:34.120
<v Speaker 3>airlock which is a lot more capacity. And also Dennis Tito,

124
00:06:34.199 --> 00:06:38.160
<v Speaker 3>you remember Dennis Tito, now the first space tourist in

125
00:06:38.199 --> 00:06:40.879
<v Speaker 3>April gets to the International Space Station when it's still

126
00:06:40.920 --> 00:06:43.480
<v Speaker 3>pretty small, right on TM thirty two and he gets

127
00:06:43.519 --> 00:06:46.240
<v Speaker 3>to spend eight days on the International Space Station. Very

128
00:06:46.240 --> 00:06:46.879
<v Speaker 3>first space.

129
00:06:46.839 --> 00:06:48.800
<v Speaker 2>I remember that, but I just didn't remember his name.

130
00:06:48.839 --> 00:06:53.959
<v Speaker 3>His name is Tito. And yeah, more supply missions. Final

131
00:06:54.000 --> 00:06:56.839
<v Speaker 3>thing I'll mention on space is that. And this year,

132
00:06:57.120 --> 00:07:03.759
<v Speaker 3>a not particularly well known tech entrepreneur named Elon Musk

133
00:07:04.480 --> 00:07:07.600
<v Speaker 3>donates one hundred thousand dollars to the Mars Society and

134
00:07:07.680 --> 00:07:11.560
<v Speaker 3>joins the board, and during one of their meetings, announces

135
00:07:11.680 --> 00:07:15.279
<v Speaker 3>a project he calls Mars Oasis, the idea of landing

136
00:07:15.360 --> 00:07:20.279
<v Speaker 3>a greenhouse on Mars. At the time, he's in negotiation

137
00:07:20.600 --> 00:07:24.519
<v Speaker 3>with ross Cosmos with the Russian Federation to acquire a

138
00:07:24.639 --> 00:07:28.800
<v Speaker 3>neeper launch vehicle to be able to fly a mission

139
00:07:28.839 --> 00:07:32.319
<v Speaker 3>to Mars. The Russians think he's a joke, and it

140
00:07:32.399 --> 00:07:34.839
<v Speaker 3>makes him angry, and he starts looking at how what

141
00:07:34.879 --> 00:07:36.519
<v Speaker 3>it would take to build his own rocket.

142
00:07:37.879 --> 00:07:39.839
<v Speaker 2>I never went anywhere, did it all?

143
00:07:39.959 --> 00:07:45.199
<v Speaker 3>Right Over to computing, I'd call it foreshadowing except its history.

144
00:07:47.120 --> 00:07:49.560
<v Speaker 3>It's two thousand and one, the dot com crash is

145
00:07:49.639 --> 00:07:52.800
<v Speaker 3>well underway. Tech companies have lost a lot of value already.

146
00:07:52.800 --> 00:07:55.600
<v Speaker 3>It's not over yet. Bottom up in two thousand and two,

147
00:07:56.279 --> 00:08:02.040
<v Speaker 3>so that's exciting. And Apple has an amazing year in

148
00:08:02.079 --> 00:08:05.040
<v Speaker 3>two thousand and one. In January, they released iTunes. It

149
00:08:05.079 --> 00:08:07.279
<v Speaker 3>was originally a product called Soundjawn that they acquired in

150
00:08:07.399 --> 00:08:10.519
<v Speaker 3>ninety nine. It was created in ninety nine they acquired

151
00:08:10.560 --> 00:08:13.160
<v Speaker 3>in two thousand and they're heading down their music path

152
00:08:13.199 --> 00:08:16.879
<v Speaker 3>because in October they'll release the iPod. They also opened

153
00:08:16.920 --> 00:08:20.319
<v Speaker 3>the first Apple stores in Glendale, California and in Tysons,

154
00:08:20.600 --> 00:08:23.879
<v Speaker 3>Virginia and mac OSX is released, So I mean Apple

155
00:08:24.000 --> 00:08:26.079
<v Speaker 3>was firing on all cylinders there. It was amazing.

156
00:08:26.279 --> 00:08:28.600
<v Speaker 2>Microsoft also released the Xbox that year.

157
00:08:28.639 --> 00:08:31.240
<v Speaker 3>Matt Microsoft releases the Xbox that year. They also released

158
00:08:31.399 --> 00:08:35.080
<v Speaker 3>XP that year, including the sixty four bit Itanium version.

159
00:08:36.120 --> 00:08:39.159
<v Speaker 3>The Xbox release includes is also the same time they

160
00:08:39.200 --> 00:08:42.559
<v Speaker 3>released Halo, the most popular game for the Xbox, and

161
00:08:42.600 --> 00:08:46.320
<v Speaker 3>it's also too. In June, the US versus Microsoft decision

162
00:08:46.360 --> 00:08:48.720
<v Speaker 3>where Microsoft is ordered to break up into two companies

163
00:08:49.200 --> 00:08:51.240
<v Speaker 3>that didn't have they will sub subsequently by the end

164
00:08:51.240 --> 00:08:53.559
<v Speaker 3>of the year negotiate a consent to cree that won't have.

165
00:08:53.720 --> 00:09:00.759
<v Speaker 3>That actually happen. Also July, Napster is shut down. This

166
00:09:00.960 --> 00:09:04.480
<v Speaker 3>was the music and media piracy site. Yeah there was,

167
00:09:05.000 --> 00:09:07.440
<v Speaker 3>you know, but it's solid. That same month, a guy

168
00:09:07.519 --> 00:09:12.200
<v Speaker 3>named Bram Cohen announces a open source library he calls BitTorrent.

169
00:09:12.639 --> 00:09:17.039
<v Speaker 2>Yeah, BitTorrent. We we got sucked into the BitTorrent thing

170
00:09:17.080 --> 00:09:19.200
<v Speaker 2>because bandwidth was expensive back then.

171
00:09:19.360 --> 00:09:23.080
<v Speaker 3>Yeah, and we were trying to save bandwidth. So well,

172
00:09:23.159 --> 00:09:25.200
<v Speaker 3>we had started the show yet, you hadn't started the

173
00:09:25.200 --> 00:09:26.840
<v Speaker 3>show yet. Remember I'm the new guy. I'll show up

174
00:09:26.840 --> 00:09:27.600
<v Speaker 3>a couple of years later.

175
00:09:27.639 --> 00:09:28.320
<v Speaker 2>But yeah, that's right.

176
00:09:28.360 --> 00:09:30.840
<v Speaker 3>Yeah, BitTorrent's already invented, and we'll you'll need to use

177
00:09:30.879 --> 00:09:33.080
<v Speaker 3>it to try and save me what cause? So yeah,

178
00:09:33.120 --> 00:09:37.279
<v Speaker 3>for on the Microsoft side, we we've got the case,

179
00:09:37.679 --> 00:09:42.200
<v Speaker 3>We've got XP We've got I E six, very popular browser,

180
00:09:42.879 --> 00:09:45.039
<v Speaker 3>and the Xbox with Hailo. That's all I got.

181
00:09:45.320 --> 00:09:48.200
<v Speaker 2>There's something else that I forgot to say, and maybe

182
00:09:48.600 --> 00:09:50.440
<v Speaker 2>you want to talk about it, But the first draft

183
00:09:50.440 --> 00:09:53.720
<v Speaker 2>of the Complete Human Genome was published in Nature in

184
00:09:53.799 --> 00:09:54.639
<v Speaker 2>two thousand and one.

185
00:09:54.720 --> 00:09:58.240
<v Speaker 3>Yeah, we talked about the preliminaries of that previously, but yeah,

186
00:09:58.279 --> 00:10:00.720
<v Speaker 3>the the Human Genome project had been going on for

187
00:10:00.759 --> 00:10:04.279
<v Speaker 3>some time. And yeah, the complete draft is almost a misnomer.

188
00:10:04.279 --> 00:10:06.840
<v Speaker 3>There'll be subsequent additions to it after that, but yeah,

189
00:10:06.879 --> 00:10:09.759
<v Speaker 3>it's a multi billion dollar multi year project that now

190
00:10:10.320 --> 00:10:12.159
<v Speaker 3>has paved the way to a whole lot of science.

191
00:10:12.159 --> 00:10:16.840
<v Speaker 2>Also, before we go on all, musician George Harrison died.

192
00:10:17.200 --> 00:10:18.559
<v Speaker 2>You may have heard of him. He was in that

193
00:10:18.639 --> 00:10:24.080
<v Speaker 2>little band called the Beatles. November twenty ninth. And yeah,

194
00:10:24.120 --> 00:10:27.679
<v Speaker 2>that was bad. Some anthrax attacks happened, some natural disasters

195
00:10:27.720 --> 00:10:30.399
<v Speaker 2>and other things. But I want to talk about the

196
00:10:30.399 --> 00:10:34.240
<v Speaker 2>top ten movies of two thousand and one. Hannibal number ten,

197
00:10:34.799 --> 00:10:39.399
<v Speaker 2>Planet of the Apes, number nine, Jurassic Park three, number eight.

198
00:10:39.639 --> 00:10:42.120
<v Speaker 2>Did you even see two or three? I only saw

199
00:10:42.159 --> 00:10:42.679
<v Speaker 2>the first one.

200
00:10:42.919 --> 00:10:43.919
<v Speaker 3>You alys saw the first one?

201
00:10:44.000 --> 00:10:50.480
<v Speaker 2>Yeah, The Mummy returns, Pearl Harbor, Ocean's eleven, Shrek also

202
00:10:50.519 --> 00:10:52.960
<v Speaker 2>great now. Number three is Monsters Inc.

203
00:10:53.240 --> 00:10:54.080
<v Speaker 3>Great great movie.

204
00:10:54.159 --> 00:10:59.080
<v Speaker 2>Number two, oh yeah, number two, Philly Crystal is just

205
00:10:59.120 --> 00:11:01.919
<v Speaker 2>so great that it's so great. Number two is Lord

206
00:11:01.960 --> 00:11:05.519
<v Speaker 2>of the Rings, the Fellowship of the Ring. And okay,

207
00:11:05.720 --> 00:11:09.039
<v Speaker 2>number one Harry Potter and the Sorcerer's Stone.

208
00:11:09.320 --> 00:11:12.919
<v Speaker 3>Yeah yeah, what a series? What a series?

209
00:11:13.519 --> 00:11:15.440
<v Speaker 2>All right? So that's about all we can say about

210
00:11:15.480 --> 00:11:16.919
<v Speaker 2>two thousand and one. I'm sure we left a lot

211
00:11:16.960 --> 00:11:18.639
<v Speaker 2>of stuff out, but hey, it's only an hour show,

212
00:11:20.320 --> 00:11:21.639
<v Speaker 2>so let's get on with better.

213
00:11:21.679 --> 00:11:21.720
<v Speaker 4>No.

214
00:11:21.799 --> 00:11:22.240
<v Speaker 2>Framework.

215
00:11:22.320 --> 00:11:22.679
<v Speaker 3>Awesome.

216
00:11:30.200 --> 00:11:33.799
<v Speaker 2>All right, all right, so I went, you know, as

217
00:11:33.840 --> 00:11:37.039
<v Speaker 2>I always do, I go looking for trending repos. This

218
00:11:37.080 --> 00:11:40.399
<v Speaker 2>one was beating all of the other trending repos by

219
00:11:40.519 --> 00:11:43.919
<v Speaker 2>a long shot, just like in one day, something like

220
00:11:43.960 --> 00:11:50.120
<v Speaker 2>six hundred thousand downloads or something. It's a it's basically

221
00:11:50.200 --> 00:11:55.399
<v Speaker 2>a video maker bot where you take a Reddit conversation

222
00:11:56.159 --> 00:12:00.480
<v Speaker 2>and you have a dialogue box that shows a question, right,

223
00:12:00.879 --> 00:12:03.919
<v Speaker 2>and then another dialogue after that posted over it that

224
00:12:04.000 --> 00:12:07.519
<v Speaker 2>has the answer, and it's usually hilarious, right, And so

225
00:12:07.600 --> 00:12:12.320
<v Speaker 2>people are making videos of these with a with a

226
00:12:12.399 --> 00:12:16.639
<v Speaker 2>background and posting them on TikTok and YouTube and Instagram

227
00:12:16.679 --> 00:12:20.320
<v Speaker 2>and everywhere, and they're going viral. This is just like

228
00:12:20.399 --> 00:12:23.480
<v Speaker 2>a thing that you're you know, you're just memish that

229
00:12:23.519 --> 00:12:27.080
<v Speaker 2>you're making fun of people on Reddit or or you know.

230
00:12:27.360 --> 00:12:29.799
<v Speaker 3>Reddit is where people make fun of people all the time.

231
00:12:29.919 --> 00:12:33.840
<v Speaker 3>So this is now a visualization because comments are historically

232
00:12:33.960 --> 00:12:34.960
<v Speaker 3>phenomenally funny.

233
00:12:35.039 --> 00:12:38.720
<v Speaker 2>The chickens are coming home to roost, I guess. So basically,

234
00:12:38.759 --> 00:12:43.039
<v Speaker 2>this guy put together a bot that makes a video

235
00:12:44.159 --> 00:12:49.360
<v Speaker 2>just with you know, pure programming basically, and he takes it.

236
00:12:49.639 --> 00:12:54.279
<v Speaker 2>He use his Python uses playwright, and he autumn. You

237
00:12:54.399 --> 00:12:56.840
<v Speaker 2>just give it the Reddit topic that you want and

238
00:12:57.000 --> 00:12:59.279
<v Speaker 2>bing bang boom makes an MP.

239
00:12:59.279 --> 00:13:04.519
<v Speaker 3>Three playwrights doing the scraping role to pull the data needed. Yeah,

240
00:13:04.879 --> 00:13:05.440
<v Speaker 3>I get it.

241
00:13:05.639 --> 00:13:07.759
<v Speaker 2>Yeah, and so yeah, this is the thing. If you

242
00:13:07.840 --> 00:13:10.440
<v Speaker 2>know it, you know, But if you don't, you don't care. Sorry,

243
00:13:10.759 --> 00:13:11.879
<v Speaker 2>I just wasted your time.

244
00:13:12.200 --> 00:13:13.440
<v Speaker 3>Hilarious.

245
00:13:14.000 --> 00:13:15.879
<v Speaker 2>So that's what I got. Who's talking to today?

246
00:13:16.440 --> 00:13:18.799
<v Speaker 3>You know, we're talking about nano framework today, And I've

247
00:13:18.840 --> 00:13:20.879
<v Speaker 3>been a while since we've done any shows around the

248
00:13:20.919 --> 00:13:23.279
<v Speaker 3>micro framework and you know, the precursor to it. But

249
00:13:23.320 --> 00:13:26.879
<v Speaker 3>I went into the wayback machine there and found our

250
00:13:27.159 --> 00:13:30.919
<v Speaker 3>IoT on Windows Talk conversation with Dan Rosenstein. This is

251
00:13:30.919 --> 00:13:35.320
<v Speaker 3>from twenty fourteen. It's episode ten nineteen, and this was

252
00:13:36.039 --> 00:13:39.120
<v Speaker 3>part of the Windows Developer program being trying to make

253
00:13:39.200 --> 00:13:42.360
<v Speaker 3>IoT easier in that space, and it focused on Intel's

254
00:13:42.399 --> 00:13:46.279
<v Speaker 3>Galileo device which works with our duino but also you know,

255
00:13:46.440 --> 00:13:51.000
<v Speaker 3>it works with x eighty six, and they at that

256
00:13:51.279 --> 00:13:55.679
<v Speaker 3>moment they hadn't released an implementation of the micro framework

257
00:13:55.679 --> 00:13:57.799
<v Speaker 3>for it, but subsequently they did. And in fact I

258
00:13:57.840 --> 00:14:00.720
<v Speaker 3>grabbed our friend Pete Brown's calm atop of the show

259
00:14:00.759 --> 00:14:03.919
<v Speaker 3>where he said, and immediately it's eleven years ago. You

260
00:14:03.960 --> 00:14:07.159
<v Speaker 3>can get the Intel Galileo for fifty nine dollars from

261
00:14:07.200 --> 00:14:11.360
<v Speaker 3>Amazon net. Duenogo runs the dot net micro framework, which

262
00:14:11.399 --> 00:14:13.919
<v Speaker 3>itself is an operating system for the device. Although OS

263
00:14:14.080 --> 00:14:16.200
<v Speaker 3>is a strong term for what is really a hardware

264
00:14:16.240 --> 00:14:20.519
<v Speaker 3>distraction layer and API set with an interpreter yeah operating system,

265
00:14:21.919 --> 00:14:23.960
<v Speaker 3>there is no additional OS required at this point. The

266
00:14:23.960 --> 00:14:27.679
<v Speaker 3>GO protocol in bus is conceptually similar to USB versus Gadgeteer,

267
00:14:27.679 --> 00:14:30.200
<v Speaker 3>which is more Arduino like in that it exposes native

268
00:14:30.240 --> 00:14:33.600
<v Speaker 3>pins and interfaces to the microcontroller. Our duino is more

269
00:14:33.639 --> 00:14:36.799
<v Speaker 3>of an API layer over ABR and not really any

270
00:14:36.799 --> 00:14:39.720
<v Speaker 3>sort of operating system in general. It uses shields, which

271
00:14:39.759 --> 00:14:42.080
<v Speaker 3>is this pin based way of adding additional hardware to

272
00:14:42.080 --> 00:14:45.200
<v Speaker 3>our duenos. But they're increasingly a number of smaller form

273
00:14:45.200 --> 00:14:50.240
<v Speaker 3>factors and breadboard family implementations. And admittedly this is a

274
00:14:50.279 --> 00:14:52.960
<v Speaker 3>ten year old post. Things have changed a fair bit here,

275
00:14:52.960 --> 00:14:55.039
<v Speaker 3>but he still goes on to say this is Pete.

276
00:14:55.320 --> 00:14:58.120
<v Speaker 3>Raspberry Pie runs Linux, as does boards like beagle Bone

277
00:14:58.159 --> 00:15:02.279
<v Speaker 3>and others. Dot A Gadgetar modules through the standard tenpin connectors,

278
00:15:02.480 --> 00:15:04.320
<v Speaker 3>but the pins are like our do we know form

279
00:15:04.360 --> 00:15:07.559
<v Speaker 3>factors dedicated specific uses. It makes it easier to prototype,

280
00:15:07.720 --> 00:15:09.799
<v Speaker 3>and when combined with a design service and class libraries

281
00:15:09.799 --> 00:15:13.360
<v Speaker 3>and visual studio, makes really good dev experience. And thanks

282
00:15:13.360 --> 00:15:16.559
<v Speaker 3>for the shartout. Thank you, Pete. We haven't met on

283
00:15:16.559 --> 00:15:19.080
<v Speaker 3>the show in forever. We should probably do something about that,

284
00:15:19.919 --> 00:15:22.480
<v Speaker 3>and I am really looking forward to our conversation to days,

285
00:15:22.559 --> 00:15:24.879
<v Speaker 3>just because there's so much that has changed in the

286
00:15:24.919 --> 00:15:27.240
<v Speaker 3>IoT space. There's so much better hardware out there and

287
00:15:27.399 --> 00:15:30.559
<v Speaker 3>obviously better tool it. So Pete, thank you so much

288
00:15:30.559 --> 00:15:32.120
<v Speaker 3>for your comment. And a copy of Music Coby is

289
00:15:32.159 --> 00:15:33.279
<v Speaker 3>on its way to you, And if you'd like a

290
00:15:33.279 --> 00:15:35.039
<v Speaker 3>copy of music co buy right a comment on the

291
00:15:35.039 --> 00:15:37.320
<v Speaker 3>website at dot net rocks dot com or on the facebooks.

292
00:15:37.320 --> 00:15:39.320
<v Speaker 3>We publish every show there and if you comment there

293
00:15:39.360 --> 00:15:40.799
<v Speaker 3>and reading on the show, we'll send you a copy

294
00:15:40.799 --> 00:15:42.399
<v Speaker 3>of Music go By and Music Coby.

295
00:15:42.480 --> 00:15:45.399
<v Speaker 2>You know, I still haven't finished the twenty third track.

296
00:15:45.559 --> 00:15:47.919
<v Speaker 2>I really got to do that, really in downtime. I

297
00:15:47.919 --> 00:15:51.519
<v Speaker 2>can't believe I didn't do that all right, twenty two tracks,

298
00:15:51.559 --> 00:15:54.360
<v Speaker 2>twenty five minutes each to help you get into a

299
00:15:54.399 --> 00:15:58.639
<v Speaker 2>state of flow while developing and stay there and still

300
00:15:58.679 --> 00:16:03.600
<v Speaker 2>going strong, also getting multiple multiple sales every week all right,

301
00:16:04.200 --> 00:16:08.200
<v Speaker 2>let's bring on our guest today, Jose Simolish. He is

302
00:16:08.279 --> 00:16:12.799
<v Speaker 2>the CEO of Eclose Solutions and founder and core team

303
00:16:12.879 --> 00:16:17.120
<v Speaker 2>lead of dot Net nano Framework. Based in Lyria, Portugal,

304
00:16:17.279 --> 00:16:20.519
<v Speaker 2>he was awarded Microsoft MVP five times for his work

305
00:16:20.519 --> 00:16:24.840
<v Speaker 2>on Internet of Things and developer technologies. His ship projects

306
00:16:24.879 --> 00:16:30.240
<v Speaker 2>across embedded firmware, hardware design, and cloud connected products, with

307
00:16:30.320 --> 00:16:34.519
<v Speaker 2>a toolbox that includes dot Net and Azure technologies alongside

308
00:16:34.600 --> 00:16:40.159
<v Speaker 2>c C plus plus microcontrollers and electronics. Passionate about building

309
00:16:40.159 --> 00:16:43.360
<v Speaker 2>open source communities and empowering developers in the various communities

310
00:16:43.399 --> 00:16:47.399
<v Speaker 2>he's actively engaged with. He's also a published author of

311
00:16:47.600 --> 00:16:51.879
<v Speaker 2>Embedded Systems with dot Net nanoframework from Apress. Welcome to

312
00:16:51.879 --> 00:16:52.879
<v Speaker 2>the show, Jose.

313
00:16:53.240 --> 00:16:57.120
<v Speaker 4>Well, thanks for having me. It's a real pleasure to

314
00:16:57.200 --> 00:16:58.080
<v Speaker 4>be here with you.

315
00:16:58.120 --> 00:16:58.399
<v Speaker 3>Guys.

316
00:16:59.159 --> 00:17:00.840
<v Speaker 2>I think it was you that reached out to us

317
00:17:00.879 --> 00:17:03.840
<v Speaker 2>about the nano framework, or somebody did recently, and that's

318
00:17:04.559 --> 00:17:05.680
<v Speaker 2>ended up being.

319
00:17:06.039 --> 00:17:09.160
<v Speaker 3>It was at episode two thousand, which you know we

320
00:17:09.279 --> 00:17:12.440
<v Speaker 3>published last week is all the time shifting thing, It

321
00:17:12.480 --> 00:17:15.440
<v Speaker 3>was actually a couple of weeks ago, Like time is weird,

322
00:17:16.039 --> 00:17:18.200
<v Speaker 3>but yeah, we had a chance to meet him and

323
00:17:18.279 --> 00:17:20.720
<v Speaker 3>like holy Man, we have never talked about nano framework.

324
00:17:20.720 --> 00:17:24.359
<v Speaker 3>We talked about micro framework years ago, right, not nano framework.

325
00:17:24.440 --> 00:17:26.240
<v Speaker 3>So we should fix that right away. It's been a

326
00:17:26.240 --> 00:17:28.000
<v Speaker 3>long time. I guess that's a good starting point. Like

327
00:17:28.039 --> 00:17:30.400
<v Speaker 3>what's the difference between micro framework and nano framework.

328
00:17:31.440 --> 00:17:35.279
<v Speaker 4>Well, interestingly, to the best of my knowledge, two thousand

329
00:17:35.359 --> 00:17:40.319
<v Speaker 4>and one was when the work started to on developing

330
00:17:40.960 --> 00:17:44.680
<v Speaker 4>micro framework, which was published in two thousand and two.

331
00:17:46.079 --> 00:17:48.000
<v Speaker 3>Right, so it came out at the same time as

332
00:17:48.000 --> 00:17:49.119
<v Speaker 3>the regular framework.

333
00:17:49.319 --> 00:17:51.759
<v Speaker 4>Yes, about the same time as far as I know. Yeah,

334
00:17:53.359 --> 00:18:02.799
<v Speaker 4>And what says about it's revised and augmented micro framework.

335
00:18:04.400 --> 00:18:11.240
<v Speaker 4>It's capable for running on small devices it had it

336
00:18:11.599 --> 00:18:16.359
<v Speaker 4>still uses a lot of the comproducts from the original

337
00:18:16.599 --> 00:18:22.319
<v Speaker 4>micro framework. We left the good parts in and we

338
00:18:22.480 --> 00:18:26.880
<v Speaker 4>revamped the basically the build system, which was quite outdated.

339
00:18:27.720 --> 00:18:33.599
<v Speaker 4>We focused on having it possible to run on multiple

340
00:18:33.839 --> 00:18:39.160
<v Speaker 4>and different hardware vendors and micro controllers, which is what

341
00:18:39.240 --> 00:18:43.000
<v Speaker 4>you can do now. Any Certitude its micro control can

342
00:18:43.440 --> 00:18:48.480
<v Speaker 4>run a nano framework. And we had a bunch of

343
00:18:48.559 --> 00:18:54.079
<v Speaker 4>stuff with everything that it's new on the embedded systems world,

344
00:18:55.720 --> 00:19:01.000
<v Speaker 4>like io T, the network connections, various protocols of course,

345
00:19:01.039 --> 00:19:05.200
<v Speaker 4>all the usual stuff that you would expect on a

346
00:19:05.279 --> 00:19:10.240
<v Speaker 4>micro control is there, spi as Czer reports, all that put.

347
00:19:10.000 --> 00:19:12.920
<v Speaker 2>By the Nano moniker that it's smaller than the micro

348
00:19:13.000 --> 00:19:14.720
<v Speaker 2>framework is that, yes.

349
00:19:15.359 --> 00:19:20.920
<v Speaker 4>Yeah, yeah, that's the naming is hard. And back then

350
00:19:20.960 --> 00:19:25.880
<v Speaker 4>when we spin off the project, we went a lot.

351
00:19:26.000 --> 00:19:28.839
<v Speaker 4>There was a lot of discussion on what we should

352
00:19:28.880 --> 00:19:34.319
<v Speaker 4>call it, and ended up being Nano with a small

353
00:19:35.039 --> 00:19:41.200
<v Speaker 4>caps N to stress that it's it's a nano version

354
00:19:41.519 --> 00:19:44.319
<v Speaker 4>of the full dot net.

355
00:19:43.759 --> 00:19:45.839
<v Speaker 3>And this is not a Microsoft in issues. This is

356
00:19:45.880 --> 00:19:46.839
<v Speaker 3>all community driven.

357
00:19:47.039 --> 00:19:54.079
<v Speaker 4>Yeah, yeah, that's something that sometimes people confuse. But despite

358
00:19:54.119 --> 00:19:59.440
<v Speaker 4>this sitting on the dot net ecosystem uses visual Studio

359
00:19:59.599 --> 00:20:03.559
<v Speaker 4>visuals to go the dot net new gats and all that.

360
00:20:04.839 --> 00:20:09.079
<v Speaker 4>It's not a Microsoft project and does not run on

361
00:20:09.400 --> 00:20:12.319
<v Speaker 4>Microsoft budget. It's community driven.

362
00:20:12.440 --> 00:20:17.359
<v Speaker 3>That's awesome. The big difference, you know, referencing the comment

363
00:20:17.359 --> 00:20:19.039
<v Speaker 3>I grabbed from ten years ago, the big difference ten

364
00:20:19.079 --> 00:20:22.680
<v Speaker 3>years from ago to now is the micro controllers are

365
00:20:22.799 --> 00:20:27.440
<v Speaker 3>wildly better. Esp. Thirty two and five, like, this is

366
00:20:27.480 --> 00:20:30.759
<v Speaker 3>such good gear out there. They're small, they're super cheap,

367
00:20:30.839 --> 00:20:32.599
<v Speaker 3>and they're really very powerful.

368
00:20:32.839 --> 00:20:38.359
<v Speaker 4>Yeah. Yeah, that's the thing when compared with micro framework. Memory,

369
00:20:38.720 --> 00:20:41.440
<v Speaker 4>despite being expensive, is much more cheap.

370
00:20:42.920 --> 00:20:46.599
<v Speaker 3>Computing me not today, but like six months ago.

371
00:20:47.400 --> 00:20:56.400
<v Speaker 5>Yeah exactly, but everything is cheaper than it was when

372
00:20:56.759 --> 00:20:57.880
<v Speaker 5>when all this started.

373
00:20:58.079 --> 00:21:02.400
<v Speaker 4>Yeah, and it makes it makes a ton of difference,

374
00:21:02.799 --> 00:21:05.799
<v Speaker 4>even with the CPU power that you see that you

375
00:21:05.880 --> 00:21:09.279
<v Speaker 4>have on the on the micro controller, and you can

376
00:21:09.599 --> 00:21:14.759
<v Speaker 4>have much smaller devices and all that has changed.

377
00:21:15.079 --> 00:21:18.480
<v Speaker 3>Yeah, just and I've been doing I haven't done much

378
00:21:18.519 --> 00:21:21.599
<v Speaker 3>with nano framework, not any with Nano framework. When I

379
00:21:21.720 --> 00:21:23.880
<v Speaker 3>use ESP thirty twos, and I'm a home assistant guy,

380
00:21:23.920 --> 00:21:25.599
<v Speaker 3>so I use the SP thirty twos all the time.

381
00:21:25.720 --> 00:21:30.480
<v Speaker 3>It's through ESP Home right where you almost barely touch

382
00:21:30.559 --> 00:21:33.400
<v Speaker 3>that hardware per se. You're just kind of giving instructions

383
00:21:33.400 --> 00:21:35.400
<v Speaker 3>for what you wanted to do, and it generates into

384
00:21:35.440 --> 00:21:37.960
<v Speaker 3>the device because it just has so much cloud exactly.

385
00:21:39.119 --> 00:21:43.440
<v Speaker 4>That's kind of I would say, similar to to the

386
00:21:43.519 --> 00:21:49.839
<v Speaker 4>to the Nano framework promise our value propositions that nano

387
00:21:49.920 --> 00:21:56.279
<v Speaker 4>frameworker abstracts all the complication from imbedded systems development and

388
00:21:56.440 --> 00:22:01.680
<v Speaker 4>the hardware. The hard part like booting my controller, configuring

389
00:22:01.759 --> 00:22:06.880
<v Speaker 4>all those registers to have the clock properly set, the

390
00:22:06.960 --> 00:22:11.359
<v Speaker 4>memory maps, the linker files. All that is hard and

391
00:22:11.480 --> 00:22:19.000
<v Speaker 4>it's abstracted. As you use Nano framework, you have framewares

392
00:22:19.039 --> 00:22:23.000
<v Speaker 4>for a bunch of different micro controllers and you can

393
00:22:23.079 --> 00:22:28.079
<v Speaker 4>basically cause ones and deploy on the different platforms that

394
00:22:28.200 --> 00:22:29.039
<v Speaker 4>you are working with.

395
00:22:29.400 --> 00:22:30.319
<v Speaker 2>Yeah, that's a nice.

396
00:22:30.119 --> 00:22:32.680
<v Speaker 3>Feature, you seem to imply. Then there is a kind

397
00:22:32.720 --> 00:22:35.640
<v Speaker 3>of a CLR here that's abstracting the hardware for us.

398
00:22:35.839 --> 00:22:39.200
<v Speaker 4>Yeah, that's there is the CLR and also how and

399
00:22:39.279 --> 00:22:44.480
<v Speaker 4>the power layer, because abstruct the hardware and you abstract

400
00:22:44.720 --> 00:22:48.799
<v Speaker 4>the platform. Despite those being micro controllers. With the thirty

401
00:22:48.839 --> 00:22:54.160
<v Speaker 4>two pits, there are cordex ones. They are the extensor

402
00:22:54.240 --> 00:23:01.359
<v Speaker 4>from Expressive, the original ones. All those are different different hardwarees,

403
00:23:01.440 --> 00:23:05.960
<v Speaker 4>different vendors. Each one has his own SDK, which makes

404
00:23:05.960 --> 00:23:12.079
<v Speaker 4>even more complicated. Also, the real time operating system, the

405
00:23:12.200 --> 00:23:17.720
<v Speaker 4>r TOSS, it's something that we added in nano framework

406
00:23:17.839 --> 00:23:21.200
<v Speaker 4>which wasn't there on the micro framework. Basically we have

407
00:23:21.240 --> 00:23:25.000
<v Speaker 4>an abstraction layer that makes it possible to use any

408
00:23:25.160 --> 00:23:29.279
<v Speaker 4>r TOS that you find out there. Given the platform

409
00:23:29.440 --> 00:23:34.920
<v Speaker 4>abstraction layer, it's there, which makes it even more powerful

410
00:23:35.200 --> 00:23:38.759
<v Speaker 4>and suitable for use on different projects.

411
00:23:38.880 --> 00:23:41.640
<v Speaker 3>I'm presuming you're not just in time compiling here. That

412
00:23:41.680 --> 00:23:44.359
<v Speaker 3>you actually compile to a given stack when you're going

413
00:23:44.440 --> 00:23:45.279
<v Speaker 3>to deploy it.

414
00:23:46.240 --> 00:23:51.839
<v Speaker 4>Actually, now this you have your c sharp publication with

415
00:23:51.960 --> 00:23:56.720
<v Speaker 4>visual Studio. When you hit F five, Rosslyn does it

416
00:23:56.880 --> 00:24:01.279
<v Speaker 4>sing with building, the upp cation, compiling and all that.

417
00:24:02.000 --> 00:24:07.200
<v Speaker 4>And then there is an extra step which runs down

418
00:24:08.039 --> 00:24:13.039
<v Speaker 4>the IL instructions and the metadata through what we call

419
00:24:13.119 --> 00:24:18.440
<v Speaker 4>the metadata processor. What it does it strips down everything

420
00:24:18.559 --> 00:24:24.440
<v Speaker 4>that it's not absolutely needed to run sharkcote. It also

421
00:24:24.640 --> 00:24:28.519
<v Speaker 4>changes the addresses because it doesn't use sixty four it

422
00:24:28.680 --> 00:24:37.200
<v Speaker 4>uses certitude bytes. And also it's yes, it's shrinking it

423
00:24:37.240 --> 00:24:40.599
<v Speaker 4>and also some changes with the resources and the enoms.

424
00:24:40.640 --> 00:24:45.759
<v Speaker 4>And that's that's basically on a very simplistic overview on

425
00:24:46.000 --> 00:24:49.559
<v Speaker 4>what's going on. And then you have the execution engine,

426
00:24:49.880 --> 00:24:52.400
<v Speaker 4>just like you have on the full dot net, which

427
00:24:52.480 --> 00:24:55.680
<v Speaker 4>is interpreting the ALE instructions one after the app.

428
00:24:55.839 --> 00:24:59.640
<v Speaker 2>Can you optionally do ahead of time compiling? No? And

429
00:24:59.759 --> 00:25:02.119
<v Speaker 2>if you could, would it help? I mean, would it

430
00:25:02.200 --> 00:25:02.880
<v Speaker 2>make it faster?

431
00:25:04.119 --> 00:25:08.799
<v Speaker 4>There is not enough room on these small mark controls too.

432
00:25:08.960 --> 00:25:12.480
<v Speaker 4>I see, so we are not doing any AOT here.

433
00:25:12.720 --> 00:25:16.400
<v Speaker 2>Right, Okay, yeah, I got some questions here. Maybe we

434
00:25:16.440 --> 00:25:18.160
<v Speaker 2>should wait till after the break though, should we do

435
00:25:18.200 --> 00:25:20.400
<v Speaker 2>it early break? Yeah, all right, we'll be right back

436
00:25:20.440 --> 00:25:28.200
<v Speaker 2>after these very important messages, and we're back. I'm Carl Franklin,

437
00:25:28.279 --> 00:25:33.000
<v Speaker 2>that's Richard Campbell. We're talking to Jose Simoish about nano framework.

438
00:25:33.680 --> 00:25:38.799
<v Speaker 2>And my big question was, obviously this has been in

439
00:25:38.799 --> 00:25:43.480
<v Speaker 2>production for a long time and devices have you know,

440
00:25:44.480 --> 00:25:48.000
<v Speaker 2>you know, have have gotten more powerful and smaller and

441
00:25:48.160 --> 00:25:51.240
<v Speaker 2>faster and all of that stuff. Can you tell me

442
00:25:51.319 --> 00:25:55.319
<v Speaker 2>what your what project you've seen out in the wild

443
00:25:55.400 --> 00:25:58.960
<v Speaker 2>or maybe you did it yourself. IoT project has been

444
00:25:59.279 --> 00:26:00.519
<v Speaker 2>the most amazing to.

445
00:26:00.519 --> 00:26:05.319
<v Speaker 4>You, the most amazing I deal with with serve products

446
00:26:05.359 --> 00:26:13.880
<v Speaker 4>from from different customers. One that it's not an.

447
00:26:12.799 --> 00:26:13.720
<v Speaker 2>I T per se.

448
00:26:14.559 --> 00:26:20.440
<v Speaker 4>One of the most interesting uses because of the all

449
00:26:20.519 --> 00:26:27.000
<v Speaker 4>the contexts it has. It's from Skyworks, a company that produces,

450
00:26:27.960 --> 00:26:35.680
<v Speaker 4>along with other compoundents, timing timing chips and they their

451
00:26:35.720 --> 00:26:39.960
<v Speaker 4>development team is a dot net shop and they use

452
00:26:40.160 --> 00:26:44.720
<v Speaker 4>dot net a long time to use their the applicate

453
00:26:44.759 --> 00:26:48.920
<v Speaker 4>the desktop applications for the the engineers network with those chips,

454
00:26:50.319 --> 00:26:54.480
<v Speaker 4>and they decided to use nano frameworks so they could

455
00:26:54.559 --> 00:26:57.839
<v Speaker 4>go all the way and so the area is in

456
00:26:57.960 --> 00:27:02.799
<v Speaker 4>NNAL framework to run the framework on the devaluation boards there,

457
00:27:03.680 --> 00:27:09.079
<v Speaker 4>and so they can benefit from all the couture used

458
00:27:09.079 --> 00:27:12.000
<v Speaker 4>that you can do on dot net, so use the

459
00:27:12.000 --> 00:27:12.640
<v Speaker 4>same quaesses.

460
00:27:12.799 --> 00:27:16.640
<v Speaker 2>So they wrote firmware with nano framework that's pretty exactly.

461
00:27:16.839 --> 00:27:20.799
<v Speaker 4>Yeah, and they use it on devaluation boards, on test benches,

462
00:27:21.400 --> 00:27:26.000
<v Speaker 4>on the test chambers and all that is using dot

463
00:27:26.119 --> 00:27:32.519
<v Speaker 4>Net from top to bottom, using classes, unit tests, all that.

464
00:27:32.720 --> 00:27:33.759
<v Speaker 4>So it's pretty amazing.

465
00:27:33.880 --> 00:27:37.079
<v Speaker 3>I really appreciate that you're not talking about a hobby project,

466
00:27:37.160 --> 00:27:40.200
<v Speaker 3>Like a lot of these things are hobbyist things. And

467
00:27:40.200 --> 00:27:44.559
<v Speaker 3>then it's like, no, this is production gear for big

468
00:27:44.640 --> 00:27:47.160
<v Speaker 3>factories that need timing equipment. And I was just looking

469
00:27:47.200 --> 00:27:49.599
<v Speaker 3>at Skyworks that they do anti jitter stuff and like

470
00:27:49.640 --> 00:27:52.039
<v Speaker 3>that's complicated machine management stuff.

471
00:27:52.119 --> 00:27:52.319
<v Speaker 2>Yeah.

472
00:27:52.680 --> 00:27:54.519
<v Speaker 3>Absolutely, but nano framework is part of that.

473
00:27:54.680 --> 00:27:58.920
<v Speaker 4>Yeah, yeah absolutely. I mean as first class you can

474
00:27:59.000 --> 00:28:02.559
<v Speaker 4>see oh right, running sea shop on a micro control.

475
00:28:02.680 --> 00:28:06.720
<v Speaker 4>That's neat. Yeah it is. And you can you can

476
00:28:06.799 --> 00:28:12.279
<v Speaker 4>do your garage opener, your sprinkling system, home automation with that,

477
00:28:12.440 --> 00:28:17.759
<v Speaker 4>and that's fine. You can also use it on universities

478
00:28:17.799 --> 00:28:20.480
<v Speaker 4>and schools to learn how to code. Sea Sharp is

479
00:28:20.480 --> 00:28:24.400
<v Speaker 4>a great language to learn how to code, but for

480
00:28:24.519 --> 00:28:29.400
<v Speaker 4>commercial products. That's that's the real change here. You can

481
00:28:29.559 --> 00:28:33.519
<v Speaker 4>be very very productive coding without matter. With all the

482
00:28:33.680 --> 00:28:40.440
<v Speaker 4>powerful debugging experience that visual Studio gives you unit tests

483
00:28:41.039 --> 00:28:44.839
<v Speaker 4>F five, you can change variables. This is far from

484
00:28:44.920 --> 00:28:49.960
<v Speaker 4>the usual embedded systems debugging cycle that you find with

485
00:28:50.079 --> 00:28:51.480
<v Speaker 4>the C and C plus plus.

486
00:28:51.559 --> 00:28:54.839
<v Speaker 2>Do you have customers using it to do real time

487
00:28:54.920 --> 00:28:59.319
<v Speaker 2>digital signal processing? I mean, I'm thinking in the audio world, right,

488
00:28:59.519 --> 00:29:02.720
<v Speaker 2>you have like Echo f X boxes and things like

489
00:29:02.759 --> 00:29:04.519
<v Speaker 2>that that you plug an input and you get an

490
00:29:04.519 --> 00:29:08.640
<v Speaker 2>output and in real time it kind of adjusts the signal.

491
00:29:09.039 --> 00:29:12.160
<v Speaker 2>But you know, DSP isn't just for audio. Of course.

492
00:29:14.440 --> 00:29:17.599
<v Speaker 4>I don't have any commercial project too that I know

493
00:29:17.680 --> 00:29:20.319
<v Speaker 4>of using it, but this is an open source project,

494
00:29:20.359 --> 00:29:23.240
<v Speaker 4>so anyone can use it. But there have been questions

495
00:29:23.279 --> 00:29:28.920
<v Speaker 4>on our discord surface about I square s, which relates

496
00:29:29.000 --> 00:29:32.759
<v Speaker 4>with sound, so I wouldn't be surprised if someone out

497
00:29:32.799 --> 00:29:34.200
<v Speaker 4>there would be using it for that.

498
00:29:34.680 --> 00:29:37.960
<v Speaker 2>Yeah, very cool. I wish I knew more about, you know,

499
00:29:38.039 --> 00:29:40.400
<v Speaker 2>that kind of low level programming to be able to

500
00:29:40.440 --> 00:29:43.839
<v Speaker 2>do that stuff. I'm really my spaces and at the

501
00:29:43.880 --> 00:29:45.559
<v Speaker 2>application layer and the back end.

502
00:29:45.880 --> 00:29:47.880
<v Speaker 4>Yeah, but you can do that with an our framework.

503
00:29:48.119 --> 00:29:50.160
<v Speaker 4>If you know how to kill the c sharp you

504
00:29:50.200 --> 00:29:50.720
<v Speaker 4>can do that.

505
00:29:51.559 --> 00:29:54.400
<v Speaker 3>Yeah, it guess always. The question here when I deal

506
00:29:54.440 --> 00:29:57.440
<v Speaker 3>with IoT projects in general, is it's the sensor set.

507
00:29:57.640 --> 00:30:01.319
<v Speaker 3>You know, the compute's fine, Now what are we trying

508
00:30:01.359 --> 00:30:04.279
<v Speaker 3>to do? Like I'm putting this small gizmo in an

509
00:30:04.359 --> 00:30:07.119
<v Speaker 3>unusual place and I want to measure things, right, light

510
00:30:07.200 --> 00:30:12.400
<v Speaker 3>levels or temperature, humidity rate of a motor spin, you

511
00:30:12.400 --> 00:30:15.160
<v Speaker 3>know that kind of thing. How do you connect sensors

512
00:30:15.160 --> 00:30:16.960
<v Speaker 3>to this is all hardware layer, and how does it

513
00:30:17.039 --> 00:30:18.599
<v Speaker 3>show up in nano framework.

514
00:30:19.359 --> 00:30:22.480
<v Speaker 4>It uses the buses on the on the macro controller,

515
00:30:23.319 --> 00:30:25.880
<v Speaker 4>the real port being the most basic one, and then

516
00:30:25.960 --> 00:30:30.880
<v Speaker 4>can have SPI R, s QC all this kind of

517
00:30:31.200 --> 00:30:34.799
<v Speaker 4>it interfaces allows you to interface with the with the

518
00:30:34.839 --> 00:30:38.680
<v Speaker 4>real world. Because I'm there are all sorts of usages

519
00:30:38.720 --> 00:30:43.279
<v Speaker 4>out there for IoT, and you can't have big machines

520
00:30:43.359 --> 00:30:47.119
<v Speaker 4>using it. But you also need the smallest one to work.

521
00:30:47.559 --> 00:30:50.599
<v Speaker 4>I mean, you don't need you don't need the device

522
00:30:50.680 --> 00:30:54.799
<v Speaker 4>with the eight cores and sixteen gigas off RAM to

523
00:30:54.839 --> 00:30:58.759
<v Speaker 4>send a hundred bytes back to the cloud. Macri Control

524
00:30:58.960 --> 00:31:01.680
<v Speaker 4>is more than capable of doing that, and you want

525
00:31:01.720 --> 00:31:07.119
<v Speaker 4>to do it with using the least possible amount of

526
00:31:07.279 --> 00:31:13.000
<v Speaker 4>energy if it's wireless device. And sometimes you can even

527
00:31:13.119 --> 00:31:17.480
<v Speaker 4>do processing on the edge with it. I mean you

528
00:31:17.519 --> 00:31:22.160
<v Speaker 4>can have it connected with in an electrical motor. You

529
00:31:22.200 --> 00:31:26.319
<v Speaker 4>can sense the vibration temperature on the shaft and you

530
00:31:26.319 --> 00:31:29.559
<v Speaker 4>can see that it's not doing what you supposed and

531
00:31:30.000 --> 00:31:35.119
<v Speaker 4>you can go into predative maintenance and give you ahead

532
00:31:35.119 --> 00:31:38.920
<v Speaker 4>of time information that something is not okay and you

533
00:31:38.920 --> 00:31:43.480
<v Speaker 4>should fix it before it burns. So there is use

534
00:31:43.519 --> 00:31:49.559
<v Speaker 4>case scenarios for all these different machines and micro controls

535
00:31:49.559 --> 00:31:50.759
<v Speaker 4>and dioite projects.

536
00:31:50.960 --> 00:31:52.880
<v Speaker 3>Yeah, I mean you mentioned a few times, but power

537
00:31:52.960 --> 00:31:54.839
<v Speaker 3>use and so forth. Is this all about being on

538
00:31:55.039 --> 00:31:57.240
<v Speaker 3>battery and trying to be efficient that way.

539
00:31:57.279 --> 00:32:00.359
<v Speaker 4>That's one of the use cases you can use it

540
00:32:00.440 --> 00:32:05.319
<v Speaker 4>with most of the time sleeping. There is a telemetry project.

541
00:32:05.359 --> 00:32:10.440
<v Speaker 4>For example, we have this deployed in solar farms and

542
00:32:10.480 --> 00:32:15.759
<v Speaker 4>the other customers using for a telemetry from oil tanks

543
00:32:16.079 --> 00:32:19.279
<v Speaker 4>out into the desert on which the device is sleeping

544
00:32:19.319 --> 00:32:22.839
<v Speaker 4>most of the time. It takes every other hour it

545
00:32:23.000 --> 00:32:26.440
<v Speaker 4>measures all the various senses that it's out there, composes

546
00:32:26.480 --> 00:32:32.000
<v Speaker 4>the package with a telemetry turns on a satellite radio

547
00:32:32.519 --> 00:32:35.200
<v Speaker 4>sends its thing to the id of and then go

548
00:32:35.279 --> 00:32:36.119
<v Speaker 4>back to sleep.

549
00:32:36.039 --> 00:32:40.039
<v Speaker 3>Back, sleep again. Yeah, that's cool and funny. Like the

550
00:32:40.119 --> 00:32:44.400
<v Speaker 3>compute consumes no energy at all, that's easy part transmitting data.

551
00:32:44.799 --> 00:32:47.720
<v Speaker 3>That's the power hog like only whan. Yeah, what a

552
00:32:47.759 --> 00:32:50.119
<v Speaker 3>difference that makes. Like you I learned pretty quickly playing

553
00:32:50.160 --> 00:32:52.480
<v Speaker 3>with ESP thirty two is like if you use that

554
00:32:52.559 --> 00:32:56.200
<v Speaker 3>Wi Fi antenna that eats your battery, you talk Bluetooth

555
00:32:56.279 --> 00:32:58.559
<v Speaker 3>bl E. You can do that all day long. It

556
00:32:58.640 --> 00:32:59.240
<v Speaker 3>means nothing.

557
00:33:00.880 --> 00:33:03.319
<v Speaker 4>Wi Fi is expensive energy wise.

558
00:33:03.680 --> 00:33:07.200
<v Speaker 3>Oh yeah, just not and and so much handshaking. It's not.

559
00:33:07.319 --> 00:33:11.279
<v Speaker 3>It just wasn't built for intermitting connectivity. It's just not

560
00:33:11.359 --> 00:33:13.480
<v Speaker 3>efficient for that sort of thing. I don't want to

561
00:33:13.519 --> 00:33:15.359
<v Speaker 3>let go the hardware piece of that, because I hope

562
00:33:15.359 --> 00:33:21.119
<v Speaker 3>you clarified that different hardware uses different buses, so you've

563
00:33:21.160 --> 00:33:22.680
<v Speaker 3>got to kind of map all that out to figure

564
00:33:22.720 --> 00:33:24.240
<v Speaker 3>out what you're going to get your connection to. But

565
00:33:24.279 --> 00:33:27.240
<v Speaker 3>the nano framework abstracts that enough you kind of don't care.

566
00:33:27.440 --> 00:33:28.880
<v Speaker 3>It's just the service at that point.

567
00:33:29.039 --> 00:33:33.400
<v Speaker 4>Yes, When, for example, if you've ever an SPI controller

568
00:33:34.039 --> 00:33:38.920
<v Speaker 4>to connect to an SPI sensor, let's say, let's say

569
00:33:39.079 --> 00:33:44.279
<v Speaker 4>a biometric sensor, you just when you're institiating the classes,

570
00:33:44.400 --> 00:33:48.519
<v Speaker 4>just say, hey, this is using spipins three, four, and sixteen,

571
00:33:49.119 --> 00:33:52.039
<v Speaker 4>and that's it. And then you can go and call

572
00:33:52.160 --> 00:33:55.839
<v Speaker 4>the right methods, the read methods with the buffers to

573
00:33:56.160 --> 00:33:58.119
<v Speaker 4>centerate or retate it from it.

574
00:33:58.279 --> 00:34:01.440
<v Speaker 3>Yeah. And then in your motor example, you'd be using

575
00:34:01.480 --> 00:34:03.880
<v Speaker 3>an SPI to do something like measure the vibration, so

576
00:34:04.000 --> 00:34:05.839
<v Speaker 3>some kind of accelerometer.

577
00:34:05.480 --> 00:34:07.400
<v Speaker 4>Yeah, exactly, Yeah, but you.

578
00:34:07.359 --> 00:34:10.000
<v Speaker 3>Still have to learn to parse that data to figure

579
00:34:10.000 --> 00:34:11.960
<v Speaker 3>out like what does this mean? What you know, what

580
00:34:11.960 --> 00:34:14.440
<v Speaker 3>are we actually measuring? Like, none of that's just that simple.

581
00:34:14.480 --> 00:34:16.679
<v Speaker 3>It takes a little time to go, Okay, we're now

582
00:34:16.719 --> 00:34:20.920
<v Speaker 3>getting g meeting readings or accelerometer readings. Now what do

583
00:34:21.000 --> 00:34:24.400
<v Speaker 3>they mean? What's good? What's bad? You know, what's the

584
00:34:24.519 --> 00:34:27.239
<v Speaker 3>rate of sample? I've played a lot of games with

585
00:34:27.400 --> 00:34:29.840
<v Speaker 3>It's one thing to check temperature every ten minutes, but

586
00:34:29.840 --> 00:34:33.039
<v Speaker 3>if you're trying to figure out if a bearing starting

587
00:34:33.039 --> 00:34:38.440
<v Speaker 3>to fail, those vibrations are in killer hurts, you need

588
00:34:38.480 --> 00:34:41.320
<v Speaker 3>to sample many times per second to really see the

589
00:34:41.400 --> 00:34:42.280
<v Speaker 3>acceleration going.

590
00:34:42.960 --> 00:34:47.360
<v Speaker 4>Yeah, you still need to despite this abstracting the complication

591
00:34:47.519 --> 00:34:52.440
<v Speaker 4>from you, you still need to understand what you are doing. Yeah,

592
00:34:52.480 --> 00:34:58.039
<v Speaker 4>so that's that's exactly. You need to understand what you

593
00:34:58.079 --> 00:35:01.000
<v Speaker 4>are doing and it makes you easy to connect to

594
00:35:01.079 --> 00:35:04.679
<v Speaker 4>that sensor. But you need to understand the data. If

595
00:35:04.719 --> 00:35:09.039
<v Speaker 4>you are a regular dot net developer, you know how

596
00:35:09.119 --> 00:35:12.440
<v Speaker 4>to instantiate an object is the classes and the methods

597
00:35:12.480 --> 00:35:16.320
<v Speaker 4>and all that, but very quickly and you don't have

598
00:35:16.400 --> 00:35:18.679
<v Speaker 4>to go through the through the sense of data ship.

599
00:35:19.360 --> 00:35:22.920
<v Speaker 4>You can understand easily understand the concept and all that

600
00:35:23.039 --> 00:35:26.880
<v Speaker 4>wires to your knowledge of the shop and how that works,

601
00:35:27.559 --> 00:35:33.000
<v Speaker 4>and you will be very productive and coding your application

602
00:35:33.239 --> 00:35:36.159
<v Speaker 4>and in a very short period of time.

603
00:35:36.719 --> 00:35:41.159
<v Speaker 2>Right, you mentioned that this is a great way for

604
00:35:41.320 --> 00:35:44.320
<v Speaker 2>people to learn how to write code, you know, especially kids,

605
00:35:44.559 --> 00:35:46.639
<v Speaker 2>you know, give them a device, give them something, right,

606
00:35:48.480 --> 00:35:54.199
<v Speaker 2>Are there any courses or trainings available that specifically use

607
00:35:54.320 --> 00:35:57.599
<v Speaker 2>the nano framework and maybe a particular device like a

608
00:35:57.679 --> 00:36:01.920
<v Speaker 2>kit that all goes together to teach programming, Not.

609
00:36:02.000 --> 00:36:05.920
<v Speaker 4>That I'm aware of, but that would be I would

610
00:36:05.960 --> 00:36:07.559
<v Speaker 4>say easy to come up with.

611
00:36:08.199 --> 00:36:13.400
<v Speaker 2>Sure, what's your favorite device for just mucking around?

612
00:36:13.559 --> 00:36:16.719
<v Speaker 4>Obvioists, how it would have to be an SP SAT two.

613
00:36:17.360 --> 00:36:19.440
<v Speaker 4>It's it's crazy cheap.

614
00:36:20.239 --> 00:36:23.840
<v Speaker 2>Yeah, And ESP thirty two said.

615
00:36:24.280 --> 00:36:27.519
<v Speaker 4>Yeah, ESP thirty two, and you can connect that you

616
00:36:28.159 --> 00:36:32.320
<v Speaker 4>to pretty much any censor up there, LEDs all the

617
00:36:32.519 --> 00:36:34.119
<v Speaker 4>all sorts of stuff.

618
00:36:33.840 --> 00:36:36.599
<v Speaker 3>And a room ESP thirty two. We can get them

619
00:36:36.599 --> 00:36:42.039
<v Speaker 3>off of Amazon, which I'll have on it, USB, Wi Fi, Bluetooth,

620
00:36:42.880 --> 00:36:46.000
<v Speaker 3>a couple of cores, ram so forth ten bucks.

621
00:36:46.400 --> 00:36:46.760
<v Speaker 2>Wow.

622
00:36:47.079 --> 00:36:51.880
<v Speaker 3>Yeah, wow. Yeah, it's like you're not really constrained. Like

623
00:36:51.920 --> 00:36:53.760
<v Speaker 3>there's a lot of compute in there, there's a lot

624
00:36:53.760 --> 00:36:56.000
<v Speaker 3>of power in there. You plug it the you plug

625
00:36:56.000 --> 00:36:58.599
<v Speaker 3>the USB port into your PC and you just start

626
00:36:58.639 --> 00:37:00.280
<v Speaker 3>talking to it. And there's a bunch of ways to

627
00:37:00.280 --> 00:37:02.320
<v Speaker 3>go about it. Nano frameworks an amazing one.

628
00:37:02.400 --> 00:37:02.599
<v Speaker 2>Yeah.

629
00:37:02.639 --> 00:37:05.679
<v Speaker 4>Yeah, it's the first time that the man went to

630
00:37:05.760 --> 00:37:07.920
<v Speaker 4>the moon. There was not such a.

631
00:37:07.920 --> 00:37:12.880
<v Speaker 3>Complete Yeah, we're recording this while Artemis is just passed

632
00:37:12.880 --> 00:37:14.519
<v Speaker 3>the moon and is on its way back, still a

633
00:37:14.519 --> 00:37:17.000
<v Speaker 3>few days away. And yeah, they got a whole bit

634
00:37:17.199 --> 00:37:19.639
<v Speaker 3>bit more computed power than say, Apollo eight had. But

635
00:37:19.800 --> 00:37:24.440
<v Speaker 3>these things the same thing, just hugely powerful. It's just

636
00:37:24.480 --> 00:37:27.000
<v Speaker 3>this interesting collision now where you've got the framework down

637
00:37:27.039 --> 00:37:30.039
<v Speaker 3>of this nice tidy size and the hardware has gotten

638
00:37:30.079 --> 00:37:33.480
<v Speaker 3>so powerful. It's just like you don't have to compromise, all.

639
00:37:33.480 --> 00:37:35.559
<v Speaker 2>Right, So now you got me looking on Amazon and

640
00:37:35.599 --> 00:37:42.679
<v Speaker 2>I found an ultimate starter kit with the ESP thirty two,

641
00:37:43.320 --> 00:37:46.360
<v Speaker 2>which has a display, it has a remote, it has

642
00:37:46.400 --> 00:37:50.679
<v Speaker 2>a camera. You know, it's got yeah, speakers, it's got

643
00:37:50.920 --> 00:37:51.679
<v Speaker 2>all the stuff.

644
00:37:52.119 --> 00:37:57.079
<v Speaker 4>Yeah, fun you can Yeah. How crazy is that?

645
00:37:58.280 --> 00:38:01.920
<v Speaker 3>Yeah, you're spending more on sense Yeah absolutely, Yeah, the

646
00:38:02.000 --> 00:38:04.599
<v Speaker 3>compute the comp pieces. Now you know that's a very

647
00:38:04.800 --> 00:38:06.159
<v Speaker 3>inexpensive smart rock.

648
00:38:06.840 --> 00:38:10.760
<v Speaker 2>And what is the process for getting the nano framework

649
00:38:10.880 --> 00:38:14.039
<v Speaker 2>on say one of these boards? Is it pretty easy?

650
00:38:14.320 --> 00:38:19.119
<v Speaker 4>You need a plant SIMPLYSB connector UH. And there there

651
00:38:19.199 --> 00:38:24.280
<v Speaker 4>is a a c l I too on which you

652
00:38:24.280 --> 00:38:30.280
<v Speaker 4>you you've typed the options kind of update massive raise

653
00:38:30.360 --> 00:38:33.320
<v Speaker 4>the target ESP S T two and it connects to

654
00:38:33.480 --> 00:38:37.719
<v Speaker 4>the can you say which which comport it is connected to? Uh?

655
00:38:37.760 --> 00:38:42.280
<v Speaker 4>And then it goes and talks with with the macro controller,

656
00:38:42.360 --> 00:38:48.320
<v Speaker 4>find out what's the model, goes and grabs the appropriate firmware,

657
00:38:48.800 --> 00:38:53.840
<v Speaker 4>flashes it, and less than one minute you have the

658
00:38:53.920 --> 00:38:57.719
<v Speaker 4>device popping on visual studio and you can start your

659
00:38:58.079 --> 00:38:59.159
<v Speaker 4>low world application.

660
00:38:59.360 --> 00:39:03.800
<v Speaker 2>So now this says it comes with Python, c Scratch

661
00:39:04.480 --> 00:39:10.679
<v Speaker 2>and video courses. But just because it comes with Python

662
00:39:10.760 --> 00:39:13.880
<v Speaker 2>doesn't mean you can't use c sharp, right, correct? You

663
00:39:13.920 --> 00:39:17.880
<v Speaker 2>just have to flash it with a nano firmwork framework.

664
00:39:18.280 --> 00:39:20.719
<v Speaker 2>It's great, fantastic, It's in my car.

665
00:39:20.880 --> 00:39:24.559
<v Speaker 3>So what's it when you're in the dead cycle here

666
00:39:24.599 --> 00:39:27.079
<v Speaker 3>are you testing as an emulator? Are you always pushing

667
00:39:27.119 --> 00:39:29.280
<v Speaker 3>to the ESP thirty two and actually running the code

668
00:39:29.320 --> 00:39:30.320
<v Speaker 3>on the SP thirty two.

669
00:39:31.079 --> 00:39:35.480
<v Speaker 4>Also a virtual device which is used to to run

670
00:39:36.679 --> 00:39:39.519
<v Speaker 4>unit tests when you don't have a real device, and

671
00:39:39.679 --> 00:39:42.960
<v Speaker 4>you can do a lot of stuff except when you

672
00:39:43.000 --> 00:39:46.599
<v Speaker 4>start touching the hardware because obviously you cannot connect there

673
00:39:47.559 --> 00:39:49.800
<v Speaker 4>being a virtual device, right.

674
00:39:49.920 --> 00:39:52.239
<v Speaker 3>Yeah, it only becomes complicated when now you want to

675
00:39:52.280 --> 00:39:54.159
<v Speaker 3>talk to the sensors and things and you kind of

676
00:39:54.199 --> 00:39:57.519
<v Speaker 3>need the hardware for that. But and my experience, just

677
00:39:57.519 --> 00:40:00.159
<v Speaker 3>take that load of to load long to loading P

678
00:40:00.280 --> 00:40:02.079
<v Speaker 3>thirty two in the first place. Like you can just

679
00:40:02.159 --> 00:40:04.719
<v Speaker 3>keep pushing to the hardware and watching it run on

680
00:40:04.800 --> 00:40:06.199
<v Speaker 3>the native gear, Yeah.

681
00:40:06.039 --> 00:40:08.400
<v Speaker 4>You can. You can keep pushing. If you are on

682
00:40:08.519 --> 00:40:11.440
<v Speaker 4>Visual Studio, when you hit that five, it will go

683
00:40:11.760 --> 00:40:18.000
<v Speaker 4>and uploads the assemblies that you have on your application,

684
00:40:19.159 --> 00:40:20.719
<v Speaker 4>and it's real quick.

685
00:40:21.239 --> 00:40:21.519
<v Speaker 3>Nice.

686
00:40:21.559 --> 00:40:24.840
<v Speaker 4>If you have a simple yellow World, it takes five

687
00:40:24.920 --> 00:40:28.679
<v Speaker 4>seconds to push that to the to the market control

688
00:40:28.920 --> 00:40:30.880
<v Speaker 4>and hit the first breakpoint.

689
00:40:30.960 --> 00:40:32.719
<v Speaker 2>So are we talking about visual studios?

690
00:40:33.199 --> 00:40:35.719
<v Speaker 3>These break points actually running on the ESP thirty two.

691
00:40:36.079 --> 00:40:40.239
<v Speaker 4>It's running on the SP thirty two with a yeah, it's.

692
00:40:40.519 --> 00:40:41.960
<v Speaker 2>So are we talking about visual studio?

693
00:40:42.039 --> 00:40:42.199
<v Speaker 6>Here?

694
00:40:42.480 --> 00:40:43.320
<v Speaker 2>Did I miss something?

695
00:40:43.480 --> 00:40:46.079
<v Speaker 4>A visual studio? And there is also an excession for

696
00:40:46.199 --> 00:40:47.079
<v Speaker 4>visual studio code?

697
00:40:47.239 --> 00:40:47.519
<v Speaker 2>Great?

698
00:40:47.679 --> 00:40:49.880
<v Speaker 3>Wow, so you can you're looking at your code and

699
00:40:50.000 --> 00:40:52.760
<v Speaker 3>visual studio. You set a break point you're actually pushing

700
00:40:52.760 --> 00:40:55.639
<v Speaker 3>onto the SP thirty two hardware. Yeah, you know, it

701
00:40:55.719 --> 00:40:58.760
<v Speaker 3>hits that sensor value that you were flagging for. The

702
00:40:58.920 --> 00:41:01.559
<v Speaker 3>classic one is when the temperature goes above X. So

703
00:41:01.599 --> 00:41:03.480
<v Speaker 3>I set a breakpoint for that, and I put my

704
00:41:03.519 --> 00:41:06.599
<v Speaker 3>hand on the sensor running on the actual hardware, and

705
00:41:06.679 --> 00:41:09.480
<v Speaker 3>the breakpoint pops up on my PC exactly and you

706
00:41:09.559 --> 00:41:10.360
<v Speaker 3>stare in awe.

707
00:41:10.679 --> 00:41:14.599
<v Speaker 4>Yeah, yeah, that's exactly. You can set all everything except

708
00:41:14.639 --> 00:41:17.920
<v Speaker 4>the fancy stuff like hot reloads and all that, because yeah,

709
00:41:18.960 --> 00:41:21.159
<v Speaker 4>but all the stuff that you have and you are

710
00:41:21.280 --> 00:41:24.320
<v Speaker 4>used to on your visual studiybox session you have there.

711
00:41:24.599 --> 00:41:27.800
<v Speaker 4>You can set breakpoints, conditional breakpoints. You can change the

712
00:41:27.880 --> 00:41:31.599
<v Speaker 4>value the value of a variable, you can inspect objects,

713
00:41:32.320 --> 00:41:35.199
<v Speaker 4>you can go with the execution back and forth, and

714
00:41:35.320 --> 00:41:38.679
<v Speaker 4>the code lines. All the heads is they are working

715
00:41:39.039 --> 00:41:43.239
<v Speaker 4>on a plane, simple USB connection and actually running on

716
00:41:43.320 --> 00:41:44.119
<v Speaker 4>the Mac control.

717
00:41:44.320 --> 00:41:47.480
<v Speaker 3>It's awesome, it is. Yeah, it's fantastic. But it just

718
00:41:47.559 --> 00:41:50.400
<v Speaker 3>means you're not struggling. You know. I've had this experience

719
00:41:50.400 --> 00:41:51.920
<v Speaker 3>where IVE done everything in the emulator and then you

720
00:41:51.920 --> 00:41:57.079
<v Speaker 3>push the hardware and you are wrong. Something's going on right,

721
00:41:57.199 --> 00:41:59.679
<v Speaker 3>So it's I am very prone to wanting to run

722
00:41:59.719 --> 00:42:02.320
<v Speaker 3>in the heart hardware. It's just that often it slows

723
00:42:02.360 --> 00:42:06.159
<v Speaker 3>the cycle down so so much. You make a change,

724
00:42:06.159 --> 00:42:08.559
<v Speaker 3>you got to wait for the push. So as long

725
00:42:08.599 --> 00:42:10.719
<v Speaker 3>as it's quick, I'd rather always work on the hardware.

726
00:42:10.840 --> 00:42:14.360
<v Speaker 4>Yeah, yeah, this, this does happen because this this is

727
00:42:14.440 --> 00:42:17.719
<v Speaker 4>dot net, uh and dot net is great on on

728
00:42:17.800 --> 00:42:22.480
<v Speaker 4>that and that's that's part of the value proposition of

729
00:42:22.599 --> 00:42:27.000
<v Speaker 4>dot net. As I said at the beginning of the show,

730
00:42:27.920 --> 00:42:31.320
<v Speaker 4>you can have your team being very productive using this

731
00:42:31.599 --> 00:42:36.320
<v Speaker 4>because the the iteration cycles are much slower, and if

732
00:42:36.320 --> 00:42:38.440
<v Speaker 4>you are as in c r C plus plus to that,

733
00:42:39.320 --> 00:42:42.639
<v Speaker 4>you need a very skilled engineer to work with that.

734
00:42:43.320 --> 00:42:45.800
<v Speaker 4>And if you need to change something on the on

735
00:42:45.840 --> 00:42:48.599
<v Speaker 4>the code, you would have to wait for that team

736
00:42:48.679 --> 00:42:51.400
<v Speaker 4>to to go and do their thing and build the

737
00:42:51.519 --> 00:42:56.639
<v Speaker 4>next firmware. And flash it with this a regular dot

738
00:42:56.719 --> 00:42:59.800
<v Speaker 4>NETLP can do it by itself. You go and change

739
00:42:59.800 --> 00:43:01.880
<v Speaker 4>what you have to change on the code. You hit

740
00:43:01.960 --> 00:43:05.320
<v Speaker 4>that five and you have your next iteration going, what was.

741
00:43:05.280 --> 00:43:09.599
<v Speaker 2>The last big update you did to the nano framework

742
00:43:09.679 --> 00:43:14.000
<v Speaker 2>and what was the you know, the big the big change.

743
00:43:14.880 --> 00:43:20.079
<v Speaker 4>It's currently in public preview, and that was adding support

744
00:43:20.199 --> 00:43:22.599
<v Speaker 4>for generics.

745
00:43:21.480 --> 00:43:26.679
<v Speaker 3>Wow, that's a resource intensive capability.

746
00:43:26.960 --> 00:43:30.199
<v Speaker 2>It is it is so you didn't have you couldn't

747
00:43:30.280 --> 00:43:31.840
<v Speaker 2>use of t before.

748
00:43:32.360 --> 00:43:36.519
<v Speaker 4>No, no, no, because when all this started, there weren't

749
00:43:36.559 --> 00:43:41.199
<v Speaker 4>generics on the full dot net. So this is all

750
00:43:41.280 --> 00:43:41.679
<v Speaker 4>it is.

751
00:43:41.719 --> 00:43:44.159
<v Speaker 2>So are you using a custom version of c sharp

752
00:43:44.280 --> 00:43:44.760
<v Speaker 2>or something?

753
00:43:46.159 --> 00:43:49.800
<v Speaker 4>Until now, we simply didn't have support fortun ICs, so

754
00:43:49.880 --> 00:43:53.639
<v Speaker 4>we would have to use the code we have to

755
00:43:53.679 --> 00:43:57.639
<v Speaker 4>go without gen x uh with the support for gun erics,

756
00:43:57.679 --> 00:44:01.159
<v Speaker 4>if we can use the all the fun stuff that

757
00:44:01.840 --> 00:44:02.800
<v Speaker 4>allows you to do and.

758
00:44:02.800 --> 00:44:03.679
<v Speaker 3>C sharp I gets.

759
00:44:03.679 --> 00:44:06.360
<v Speaker 2>My question is can we use other c sharp features

760
00:44:06.440 --> 00:44:07.519
<v Speaker 2>like link or.

761
00:44:08.000 --> 00:44:11.079
<v Speaker 4>That library is under development right now so we'll be

762
00:44:11.119 --> 00:44:13.639
<v Speaker 4>able to fuse link with nane of their work.

763
00:44:13.719 --> 00:44:17.880
<v Speaker 2>Yes, I see, so it's it is nan It's limited

764
00:44:17.960 --> 00:44:19.880
<v Speaker 2>in terms of what it can do, even though the

765
00:44:19.960 --> 00:44:20.599
<v Speaker 2>language is.

766
00:44:20.599 --> 00:44:26.159
<v Speaker 4>Modern Yes, yeah, yeah, and and this is something that

767
00:44:26.599 --> 00:44:29.360
<v Speaker 4>it took a long time to develop. If all, we

768
00:44:29.360 --> 00:44:33.679
<v Speaker 4>won't believe it, but this is started back in COVID. Wow.

769
00:44:34.119 --> 00:44:39.800
<v Speaker 4>So it's it's really crazy the amount of engineering that

770
00:44:40.079 --> 00:44:46.599
<v Speaker 4>goes back there and making this this happen. And interestingly

771
00:44:47.000 --> 00:44:52.840
<v Speaker 4>it it doesn't add that much to the to the

772
00:44:52.920 --> 00:44:56.519
<v Speaker 4>execution engine or to the requirements on the run and

773
00:44:56.599 --> 00:45:02.679
<v Speaker 4>all that because the way it's engineered at the sea

774
00:45:02.719 --> 00:45:08.280
<v Speaker 4>sharp language and the metadata and all that makes it

775
00:45:08.360 --> 00:45:14.000
<v Speaker 4>possible to run on on the market controller, which is

776
00:45:14.039 --> 00:45:14.679
<v Speaker 4>pretty neat.

777
00:45:15.519 --> 00:45:17.639
<v Speaker 3>I mean, is there really even a conversation here about

778
00:45:17.679 --> 00:45:19.960
<v Speaker 3>the version of dot net you're running?

779
00:45:21.800 --> 00:45:24.800
<v Speaker 4>No, and even with the sea sharp language is kind

780
00:45:24.800 --> 00:45:30.320
<v Speaker 4>of that. When that question pops up, the usual answer

781
00:45:30.719 --> 00:45:36.000
<v Speaker 4>is it depends. And the thing you can you can

782
00:45:36.159 --> 00:45:40.440
<v Speaker 4>set your your sea sharp project to the latest version

783
00:45:40.519 --> 00:45:45.880
<v Speaker 4>of the language and most of the features will work

784
00:45:46.760 --> 00:45:48.920
<v Speaker 4>if it's not support and we don't even keep a

785
00:45:48.960 --> 00:45:53.039
<v Speaker 4>list of the unsupported things because it would be hard

786
00:45:53.079 --> 00:45:58.119
<v Speaker 4>to maintain. But if something it's not working and breaks,

787
00:45:58.239 --> 00:46:03.079
<v Speaker 4>you immediately will not is that it's it's because of

788
00:46:03.119 --> 00:46:06.599
<v Speaker 4>that and you can get away from from it.

789
00:46:07.039 --> 00:46:09.400
<v Speaker 3>Okay, So what is the error messages you look like,

790
00:46:09.639 --> 00:46:11.639
<v Speaker 3>you know, how does it behave when you hit you're

791
00:46:11.719 --> 00:46:13.440
<v Speaker 3>using a feature that is not implemented.

792
00:46:13.840 --> 00:46:16.639
<v Speaker 4>Most of the time, it won't even compile. Our will

793
00:46:16.800 --> 00:46:21.280
<v Speaker 4>so you will immediately that you are off track.

794
00:46:21.480 --> 00:46:26.079
<v Speaker 3>Okay, that's pretty very straightforward. And the same viewpoint on

795
00:46:26.119 --> 00:46:28.559
<v Speaker 3>the c sharp language features, like, it's not a specific

796
00:46:28.639 --> 00:46:29.679
<v Speaker 3>version of c sharp.

797
00:46:29.840 --> 00:46:34.320
<v Speaker 4>It's not. We tend to use the lightest one that's

798
00:46:34.320 --> 00:46:40.320
<v Speaker 4>out there and it's uh, it just works. And that's

799
00:46:40.360 --> 00:46:43.159
<v Speaker 4>not on us, it's on Rosslyn and visual suited and

800
00:46:43.199 --> 00:46:48.519
<v Speaker 4>all that. So it's amazing all this being possible.

801
00:46:49.199 --> 00:46:54.159
<v Speaker 3>Yeah, noo. Question, uh what about l MS, Like if

802
00:46:54.199 --> 00:46:56.039
<v Speaker 3>you are you using any of this tooling to do

803
00:46:56.119 --> 00:46:57.639
<v Speaker 3>work with nano framework.

804
00:46:57.559 --> 00:47:01.239
<v Speaker 4>Do you? Yes, we have we have an m CP

805
00:47:01.400 --> 00:47:07.119
<v Speaker 4>server on our embedded server library which allows you to

806
00:47:08.519 --> 00:47:14.760
<v Speaker 4>expose prompts and capabilities from a market controller and using

807
00:47:14.840 --> 00:47:19.280
<v Speaker 4>the m c P you can have any l ll

808
00:47:19.400 --> 00:47:23.840
<v Speaker 4>M interacting with the with the device, which kind of

809
00:47:24.719 --> 00:47:27.559
<v Speaker 4>brings this to the to the next level of I T.

810
00:47:28.119 --> 00:47:32.280
<v Speaker 4>You now can have intelligent Internet of Things on which

811
00:47:32.320 --> 00:47:36.400
<v Speaker 4>you can have the machine talking with the l l

812
00:47:36.480 --> 00:47:40.400
<v Speaker 4>M answering to two questions from the machine using those prompts,

813
00:47:40.519 --> 00:47:43.960
<v Speaker 4>and you can, hey, give me the temperature for the

814
00:47:44.039 --> 00:47:48.960
<v Speaker 4>sense this and that so. And because it provides the prompts,

815
00:47:49.840 --> 00:47:52.760
<v Speaker 4>the l l M doesn't have to guess and you

816
00:47:52.840 --> 00:47:58.519
<v Speaker 4>can ask exactly what he wants to know about what

817
00:47:58.519 --> 00:48:02.760
<v Speaker 4>whatever the device is doing and providing, which is very

818
00:48:02.960 --> 00:48:03.440
<v Speaker 4>very nice.

819
00:48:03.679 --> 00:48:06.079
<v Speaker 3>Does the m c P enumerate the capabilities of the

820
00:48:06.079 --> 00:48:09.880
<v Speaker 3>embedded hardware for the l M just to keep it

821
00:48:09.920 --> 00:48:12.000
<v Speaker 3>in sort of in parameter.

822
00:48:11.840 --> 00:48:15.159
<v Speaker 4>Yeah, this is. You can do that using a very

823
00:48:15.159 --> 00:48:21.039
<v Speaker 4>simple C sharp class and you you decorate the methods

824
00:48:21.480 --> 00:48:25.599
<v Speaker 4>with an attribute on which you have the description, Hey,

825
00:48:26.199 --> 00:48:29.199
<v Speaker 4>ask me this to get the temperature of the sense

826
00:48:29.239 --> 00:48:34.519
<v Speaker 4>of blah blah blah, or send this to enable this

827
00:48:34.760 --> 00:48:39.920
<v Speaker 4>gp I O to do this and and all all those,

828
00:48:40.880 --> 00:48:44.599
<v Speaker 4>all those prompts, and the l M is able to

829
00:48:44.800 --> 00:48:50.280
<v Speaker 4>give you to to interact with the device knowing beforehand

830
00:48:50.719 --> 00:48:53.480
<v Speaker 4>what it's capable of doing and what it's not.

831
00:48:53.760 --> 00:48:56.280
<v Speaker 3>Awesome, So what's next for the nano framework?

832
00:48:57.760 --> 00:49:02.440
<v Speaker 4>What's next? We am to to be able to get

833
00:49:04.199 --> 00:49:06.800
<v Speaker 4>in sync with the with the full dot net on

834
00:49:06.840 --> 00:49:10.480
<v Speaker 4>the project system, because we are still using the the

835
00:49:10.519 --> 00:49:17.239
<v Speaker 4>old CSP project format uh. And we also want to

836
00:49:17.239 --> 00:49:21.800
<v Speaker 4>to improve on the on the debugging experience because this

837
00:49:21.960 --> 00:49:27.039
<v Speaker 4>is still using the old debug version of visual Studio,

838
00:49:27.880 --> 00:49:31.599
<v Speaker 4>and want to keep up with with the new stuff.

839
00:49:31.639 --> 00:49:35.519
<v Speaker 4>So we are looking forward to to move to the

840
00:49:35.639 --> 00:49:39.880
<v Speaker 4>to the next version with generics with be pretty much

841
00:49:41.079 --> 00:49:45.519
<v Speaker 4>compair with with the full dot net and that's the

842
00:49:46.039 --> 00:49:46.920
<v Speaker 4>that's our plan.

843
00:49:47.159 --> 00:49:50.880
<v Speaker 2>So it's an open source project. Are you looking for contributors?

844
00:49:51.079 --> 00:49:51.239
<v Speaker 3>Oh?

845
00:49:51.320 --> 00:49:56.880
<v Speaker 4>Yes, absolutely, We love prs and we love contributors and

846
00:49:58.079 --> 00:50:02.039
<v Speaker 4>if if ands sponsors commercial sponsors.

847
00:50:01.719 --> 00:50:03.440
<v Speaker 3>Yeah, I see you have a couple of sponsors, but

848
00:50:03.519 --> 00:50:05.760
<v Speaker 3>I would think with all of these different companies using

849
00:50:05.800 --> 00:50:07.760
<v Speaker 3>this you have more sponsors.

850
00:50:08.280 --> 00:50:13.119
<v Speaker 4>Yeah, that would be the the ideal world. But it's

851
00:50:13.159 --> 00:50:19.480
<v Speaker 4>not just like with most I would say open source projects.

852
00:50:20.519 --> 00:50:26.440
<v Speaker 4>That's that's an issue. Companies like to use open sources.

853
00:50:26.519 --> 00:50:31.280
<v Speaker 4>They rely on open source, but they don't give back

854
00:50:31.360 --> 00:50:35.280
<v Speaker 4>to the to the project. And we all know that

855
00:50:36.719 --> 00:50:41.400
<v Speaker 4>that story after the companies relying on a guy doing

856
00:50:41.480 --> 00:50:45.039
<v Speaker 4>the development solo on a very eage component and when

857
00:50:45.079 --> 00:50:47.800
<v Speaker 4>that breaks, they go in off the door of that

858
00:50:47.880 --> 00:50:51.360
<v Speaker 4>guy that has to fix everything and they don't contribute

859
00:50:51.400 --> 00:50:52.639
<v Speaker 4>back to the project.

860
00:50:53.239 --> 00:50:56.039
<v Speaker 3>But they do complain bitterly that they will stop using

861
00:50:56.079 --> 00:50:58.039
<v Speaker 3>your library if you don't fix it immediately.

862
00:50:58.480 --> 00:51:03.119
<v Speaker 7>Yeah, that's the thing with it's we all know this story.

863
00:51:03.159 --> 00:51:07.519
<v Speaker 7>It's free lacking free speech, not the free beer, because

864
00:51:07.559 --> 00:51:10.079
<v Speaker 7>they have those people that come and knock at your

865
00:51:10.159 --> 00:51:13.039
<v Speaker 7>door and go to the fridge for the beer and

866
00:51:13.079 --> 00:51:16.440
<v Speaker 7>they don't like the brand. They complain about the color

867
00:51:16.599 --> 00:51:19.960
<v Speaker 7>of the bottle and this is not cold or hot enough,

868
00:51:20.679 --> 00:51:23.079
<v Speaker 7>and they don't give back anything.

869
00:51:23.199 --> 00:51:25.639
<v Speaker 2>We've had to say that to people who complain about

870
00:51:25.639 --> 00:51:27.920
<v Speaker 2>our podcasting, will give your money back.

871
00:51:28.760 --> 00:51:38.079
<v Speaker 8>Yeah, but it's something that companies I think some of

872
00:51:38.119 --> 00:51:45.719
<v Speaker 8>them don't even realize the power and how how interesting

873
00:51:45.800 --> 00:51:50.880
<v Speaker 8>this is because on our framework, for example, we try

874
00:51:50.960 --> 00:51:53.119
<v Speaker 8>to every new release.

875
00:51:52.880 --> 00:51:55.559
<v Speaker 4>That we put us there, we obviously do our best

876
00:51:55.639 --> 00:51:59.079
<v Speaker 4>to make to make sure that it's bog free and

877
00:51:59.119 --> 00:52:01.679
<v Speaker 4>all that, but every now and then I slips. And

878
00:52:03.360 --> 00:52:07.039
<v Speaker 4>what you see on the discord surf is that when

879
00:52:07.880 --> 00:52:11.159
<v Speaker 4>anytime that happens, it doesn't take you more than one

880
00:52:11.199 --> 00:52:16.079
<v Speaker 4>on two hours, someone out there will think you, hey,

881
00:52:16.239 --> 00:52:19.239
<v Speaker 4>this is not working for me. You broke the w

882
00:52:19.480 --> 00:52:23.559
<v Speaker 4>tooth or whatever, and we can immediately fix it. And

883
00:52:24.239 --> 00:52:28.519
<v Speaker 4>this is powerful for commercial use. You have a small

884
00:52:28.679 --> 00:52:32.039
<v Speaker 4>army of testers out there working for you for free and.

885
00:52:32.079 --> 00:52:34.920
<v Speaker 2>Lots of fun. Well, I just ordered mine, so I'm

886
00:52:34.920 --> 00:52:37.199
<v Speaker 2>gonna tell us about the book.

887
00:52:37.519 --> 00:52:42.920
<v Speaker 4>Yeah, the book. It's it's I'm very happy about about that.

888
00:52:44.039 --> 00:52:45.639
<v Speaker 3>It just come out in January.

889
00:52:45.840 --> 00:52:49.760
<v Speaker 4>Yes, it was. It was published on the officially published

890
00:52:49.800 --> 00:52:52.119
<v Speaker 4>on the last day of the of the year.

891
00:52:52.639 --> 00:52:52.880
<v Speaker 3>Nice.

892
00:52:54.000 --> 00:52:58.199
<v Speaker 4>So it's it was kind of a marathon. I was

893
00:52:58.239 --> 00:53:00.840
<v Speaker 4>reached out by by a prayer to you to write

894
00:53:01.000 --> 00:53:05.559
<v Speaker 4>because there was nothing about nano firmwork and the closest

895
00:53:05.599 --> 00:53:09.719
<v Speaker 4>thing was with micro framework a long time ago. And

896
00:53:09.760 --> 00:53:16.679
<v Speaker 4>this was kind of this lack of literature about about this. Uh.

897
00:53:16.719 --> 00:53:20.519
<v Speaker 4>And so they reached out to me and having wrote

898
00:53:20.840 --> 00:53:24.239
<v Speaker 4>the book, which I said, yes, of course, let's spread

899
00:53:24.239 --> 00:53:26.079
<v Speaker 4>the word about nano firmwork.

900
00:53:26.920 --> 00:53:29.360
<v Speaker 3>You've got the definitive work. Then this is the book.

901
00:53:29.639 --> 00:53:31.679
<v Speaker 4>Yeah, that's this is the work.

902
00:53:32.960 --> 00:53:36.280
<v Speaker 3>It's awesome. Well, thanks so much, Ise. This is really

903
00:53:36.320 --> 00:53:38.320
<v Speaker 3>exciting and glad to see it's going on. So well,

904
00:53:38.679 --> 00:53:39.320
<v Speaker 3>great stuff.

905
00:53:39.360 --> 00:53:43.000
<v Speaker 2>Thank you again, Thank you for having me. All Right,

906
00:53:43.119 --> 00:53:46.679
<v Speaker 2>all right, we'll talk to you next time. That networks.

907
00:54:06.679 --> 00:54:09.400
<v Speaker 9>Dot net rocks is brought to you by Franklin's net

908
00:54:09.519 --> 00:54:13.480
<v Speaker 9>and produced by Pop Studios, a full service audio, video

909
00:54:13.519 --> 00:54:17.599
<v Speaker 9>and post production facility located physically in New London, Connecticut,

910
00:54:17.840 --> 00:54:22.679
<v Speaker 9>and of course in the cloud online at pwop dot com.

911
00:54:22.840 --> 00:54:25.000
<v Speaker 6>Visit our website at d O T N E t

912
00:54:25.239 --> 00:54:29.239
<v Speaker 6>R O c k S dot com for RSS feeds, downloads,

913
00:54:29.400 --> 00:54:33.079
<v Speaker 6>mobile apps, comments, and access to the full archives going

914
00:54:33.119 --> 00:54:36.519
<v Speaker 6>back to show number one, recorded in September two thousand

915
00:54:36.519 --> 00:54:36.800
<v Speaker 6>and two.

916
00:54:37.400 --> 00:54:39.760
<v Speaker 9>And make sure you check out our sponsors. They keep

917
00:54:39.840 --> 00:54:43.000
<v Speaker 9>us in business. Now go write some code, See you

918
00:54:43.039 --> 00:54:43.480
<v Speaker 9>next time.

919
00:54:44.360 --> 00:54:49.960
<v Speaker 7>You got javans dot
