1
00:00:00,659 --> 00:00:01,930
Hello, alleged human.

2
00:00:02,160 --> 00:00:05,840
This is the Chaos Lever Podcast, and I was on vacation

3
00:00:05,840 --> 00:00:08,860
last week, so there's no new episode this week.

4
00:00:09,010 --> 00:00:12,700
But instead, I thought we could revisit a favorite topic of mine.

5
00:00:12,700 --> 00:00:17,209
And when I say favorite, I mean that I hate it and I want to burn it with fire.

6
00:00:17,630 --> 00:00:21,620
We are going to talk about the supercloud by listening to

7
00:00:21,620 --> 00:00:25,349
an episode that Chris and I recorded on October 4th, 2022.

8
00:00:26,599 --> 00:00:30,580
So sit back, Pop open a can of something strong

9
00:00:30,760 --> 00:00:33,640
and enjoy this episode about the super cloud.

10
00:00:35,210 --> 00:00:35,470
All right.

11
00:00:35,470 --> 00:00:38,079
So anyway, you were watching a TV show about taking over the world.

12
00:00:38,470 --> 00:00:40,510
And I was inspired as one is.

13
00:00:40,910 --> 00:00:44,579
That was hilarious because the ELM that was presented in the

14
00:00:44,580 --> 00:00:48,439
show, the Earth Liberation Movement, was like this pseudo

15
00:00:48,440 --> 00:00:52,275
terrorist Eco organization, and they were all treating them like,

16
00:00:52,315 --> 00:00:55,574
Ah, ridiculous, these climate people with their climate stuff.

17
00:00:56,175 --> 00:00:57,704
And I was like, shit.

18
00:00:59,394 --> 00:01:00,664
Man, when was this filmed?

19
00:01:00,714 --> 00:01:04,004
I'm guessing this was like 2005 ish time frame.

20
00:01:04,004 --> 00:01:07,534
So, you know, I mean, solid 15, 17 years old.

21
00:01:07,614 --> 00:01:08,214
Doesn't matter.

22
00:01:08,254 --> 00:01:08,504
Sure.

23
00:01:08,534 --> 00:01:10,315
The point is, it felt outdated.

24
00:01:10,654 --> 00:01:14,244
They were making fun of like, people firebombing SUVs and stuff.

25
00:01:14,244 --> 00:01:15,094
And I'm like, no.

26
00:01:15,245 --> 00:01:15,914
Oh, sweetie.

27
00:01:17,245 --> 00:01:18,455
That's hilarious.

28
00:01:18,575 --> 00:01:22,205
It's like, A, the actual terrorist organizations we have to worry

29
00:01:22,205 --> 00:01:26,485
about are, they're not the Earth Liberation Foundation or whatever.

30
00:01:27,035 --> 00:01:29,005
It's probably the white nationalists.

31
00:01:29,235 --> 00:01:34,174
And also, climate change is a real thing and it's a big problem now.

32
00:01:34,860 --> 00:01:37,400
So you can put that in your pipe and smoke it y'all.

33
00:01:37,950 --> 00:01:39,330
I mean, that's your opinion.

34
00:01:40,340 --> 00:01:41,940
Well, just like facts.

35
00:01:42,650 --> 00:01:44,640
Oh, okay, 2006.

36
00:01:44,709 --> 00:01:46,369
I was very close.

37
00:01:46,380 --> 00:01:47,200
I had to look it up.

38
00:01:47,200 --> 00:01:48,720
Yeah, that's not bad.

39
00:01:48,760 --> 00:01:52,530
And I mean, I remember that term or that the name of that series,

40
00:01:52,570 --> 00:01:55,560
but I thought it was A movie, first of all, when you said it.

41
00:01:56,260 --> 00:01:57,960
Like, Numbers was definitely a movie, right?

42
00:01:58,010 --> 00:01:59,190
Probably with Jim Carrey.

43
00:01:59,820 --> 00:02:01,420
Might have been filmed in black and white.

44
00:02:01,540 --> 00:02:03,760
I don't know what you're talking about.

45
00:02:03,810 --> 00:02:05,240
I can't even tell if you're doing a bit.

46
00:02:05,799 --> 00:02:06,899
It's a bit of a bit, yes.

47
00:02:06,900 --> 00:02:11,560
I just melded, like, five things together from the late 90s, early 2000s.

48
00:02:13,430 --> 00:02:13,930
Okay.

49
00:02:14,240 --> 00:02:15,350
Showtime!

50
00:02:16,400 --> 00:02:17,620
Thank you, that's all I got.

51
00:02:19,840 --> 00:02:21,520
Have you seen the new Sonic movies?

52
00:02:21,920 --> 00:02:22,210
Oh yeah.

53
00:02:22,210 --> 00:02:22,960
There's two of them.

54
00:02:23,180 --> 00:02:23,520
Okay.

55
00:02:23,540 --> 00:02:27,080
So you've seen both of them, and you know that Jim Carrey is excellent in both.

56
00:02:27,080 --> 00:02:27,144
Yes.

57
00:02:27,675 --> 00:02:31,725
Yes, he, not only is he great casting, in my opinion, for Dr.

58
00:02:31,725 --> 00:02:33,565
Robotnik, he's the only casting.

59
00:02:34,055 --> 00:02:38,525
There are very few other people I can think of that could potentially

60
00:02:38,525 --> 00:02:41,594
fit the bill, and they would have done it in completely different ways.

61
00:02:41,775 --> 00:02:44,524
So, I mean, like, could you imagine Dennis Hopper?

62
00:02:45,220 --> 00:02:45,840
As Dr.

63
00:02:45,840 --> 00:02:46,380
Robotnik.

64
00:02:46,920 --> 00:02:49,330
I'm just, well, I mean, he does have the, the major

65
00:02:49,830 --> 00:02:52,230
negative on that front is that he is not alive.

66
00:02:53,140 --> 00:02:54,480
That's got to imagine it.

67
00:02:54,480 --> 00:02:59,440
And if he's, if he had the forethought to sell his likeness to

68
00:02:59,739 --> 00:03:02,929
AI, which we can get to later, it wouldn't even be a problem.

69
00:03:03,840 --> 00:03:05,210
You heard about the Bruce Willis thing, right?

70
00:03:05,480 --> 00:03:07,350
Yeah, it's, there's a little bit of fake

71
00:03:07,350 --> 00:03:08,970
news involved in that story at the moment.

72
00:03:10,440 --> 00:03:11,560
Complicated.

73
00:03:11,670 --> 00:03:15,090
Isn't it always when it comes to AI, that's a future episode.

74
00:03:15,090 --> 00:03:15,609
I think.

75
00:03:16,990 --> 00:03:18,249
AI, it's complicated.

76
00:03:18,250 --> 00:03:22,549
Oh, let's get into this one.

77
00:03:22,580 --> 00:03:23,650
Hello, alleged human.

78
00:03:23,660 --> 00:03:25,270
And welcome to the Chaos Labor Podcast.

79
00:03:25,300 --> 00:03:26,030
My name is Ned.

80
00:03:26,540 --> 00:03:27,890
I'm definitely not a robot.

81
00:03:28,440 --> 00:03:32,260
I abide in a ranch style domicile of my own volition.

82
00:03:32,530 --> 00:03:34,700
It has nothing to do with the fact that stairs

83
00:03:34,700 --> 00:03:37,760
are a frightening and insufferable mystery.

84
00:03:38,079 --> 00:03:39,359
Everyone has their thing, right?

85
00:03:39,869 --> 00:03:42,619
Vacuum cleaners frighten the dogbot and stairs?

86
00:03:43,379 --> 00:03:45,109
Oops, never mind.

87
00:03:45,639 --> 00:03:47,499
I just, I don't like stairs.

88
00:03:47,899 --> 00:03:51,040
With me is Chris, who is also here.

89
00:03:51,379 --> 00:03:52,939
How do you feel about stairs, Chris?

90
00:03:53,579 --> 00:03:55,980
I mean, I can go both down the stairs and

91
00:03:56,019 --> 00:03:58,420
up the stairs at whatever speed I choose.

92
00:03:59,180 --> 00:04:02,889
So, you know, that's how legs work when you're, um, alive.

93
00:04:04,499 --> 00:04:06,619
Going upstairs is perfectly fine.

94
00:04:07,089 --> 00:04:09,069
Going downstairs is a terrifying nightmare.

95
00:04:09,149 --> 00:04:10,279
I think we can all agree on that.

96
00:04:10,795 --> 00:04:12,015
So you're an opposite cow.

97
00:04:14,424 --> 00:04:15,465
That's why they have ramps.

98
00:04:17,805 --> 00:04:18,755
Is that really true?

99
00:04:18,894 --> 00:04:22,184
I feel like that's urban, not even urban legend, like rural legend.

100
00:04:22,375 --> 00:04:23,225
Rural legend.

101
00:04:25,675 --> 00:04:27,045
I feel like there's a name for that already.

102
00:04:27,045 --> 00:04:28,205
An old wives tale.

103
00:04:28,625 --> 00:04:32,055
You've got to imagine for a cow, they would at least be perplexed.

104
00:04:32,600 --> 00:04:35,110
I think that's the constant state for a cow.

105
00:04:36,380 --> 00:04:37,380
Grass?

106
00:04:38,990 --> 00:04:40,450
Repeat for 40 years.

107
00:04:42,720 --> 00:04:46,130
Oh, I'm glad we're laughing because the rest of

108
00:04:46,130 --> 00:04:49,150
this episode is just going to be me cursing a lot.

109
00:04:49,150 --> 00:04:51,159
So let's do that.

110
00:04:51,170 --> 00:04:51,870
Strap in.

111
00:04:52,070 --> 00:04:54,119
Let's talk about some tech garbage.

112
00:04:55,070 --> 00:04:55,950
Supercloud.

113
00:04:56,130 --> 00:04:56,650
Trademark.

114
00:04:56,650 --> 00:04:56,690
Supercloud.

115
00:04:56,690 --> 00:04:56,704
Trademark.

116
00:04:57,195 --> 00:05:00,875
Trademark, TM, R, copyright, all those things.

117
00:05:01,544 --> 00:05:04,525
It's a thing now, so I guess we need to address it.

118
00:05:05,164 --> 00:05:05,474
Fuck.

119
00:05:05,945 --> 00:05:06,534
Cool.

120
00:05:06,714 --> 00:05:07,434
Let's do that.

121
00:05:08,124 --> 00:05:09,765
I mean, yay!

122
00:05:12,124 --> 00:05:15,775
In the not too long ago, I think we mentioned Supercloud briefly

123
00:05:15,775 --> 00:05:20,104
in a larger discussion of hybrid, on premises, and other things,

124
00:05:20,124 --> 00:05:23,534
and my original take was something along the lines of, this is a

125
00:05:23,534 --> 00:05:26,695
stupid term that someone invented so they could own and promote it.

126
00:05:27,060 --> 00:05:30,409
The term adds nothing substantive to the discussion on the future of

127
00:05:30,409 --> 00:05:34,989
technology, conflates multiple terms we already don't have a solid definition

128
00:05:34,989 --> 00:05:39,679
for, and adds a fluffy, confusing buzzword to the marketing hellscape

129
00:05:40,120 --> 00:05:44,900
vendors can glom onto and abuse until it is more meaningless than it started.

130
00:05:45,390 --> 00:05:46,140
There

131
00:05:46,190 --> 00:05:47,460
is an AI idea.

132
00:05:47,719 --> 00:05:51,680
We need to put together a fluffy, confusing buzzword bot.

133
00:05:52,275 --> 00:05:53,975
I think that's already taken care of for us.

134
00:05:54,474 --> 00:05:56,434
Well, yeah, but that's by IT Dude Bros.

135
00:05:56,474 --> 00:05:57,674
This would be by

136
00:05:57,675 --> 00:05:59,094
AI.

137
00:05:59,094 --> 00:05:59,275
We've

138
00:05:59,304 --> 00:06:01,054
always wanted to put the IT Dude

139
00:06:01,075 --> 00:06:02,025
Bros out of business.

140
00:06:02,155 --> 00:06:03,034
Okay, well, that's fair.

141
00:06:03,124 --> 00:06:03,514
Yes.

142
00:06:04,130 --> 00:06:08,380
And yet, despite all of this, all the angry things that I said into

143
00:06:08,380 --> 00:06:13,669
a microphone that clearly some people listen to, you, it persists.

144
00:06:13,929 --> 00:06:15,489
Supercloud persists.

145
00:06:15,859 --> 00:06:17,169
And also, no, I'm not listening.

146
00:06:17,379 --> 00:06:19,460
Okay, well, I mean, it was the royal you.

147
00:06:21,319 --> 00:06:23,749
So since we can't simply nuke it from

148
00:06:23,749 --> 00:06:26,889
orbit, I supposed we have to engage head on.

149
00:06:27,430 --> 00:06:32,100
With a robust discussion on the origin of the term, the evolving use

150
00:06:32,150 --> 00:06:36,510
of the term, a working definition that is definitely, completely, and

151
00:06:36,510 --> 00:06:41,159
entirely too long, and the popularity of the term now and in the future.

152
00:06:41,510 --> 00:06:45,189
But first, a word from our sponsor, Pedantry!

153
00:06:46,085 --> 00:06:48,825
Tired of being an easy going person people

154
00:06:48,825 --> 00:06:50,825
enjoy talking to at social gatherings?

155
00:06:51,085 --> 00:06:55,255
Exhausted by the constant bother of interfacing with fellow human beings?

156
00:06:55,465 --> 00:06:58,974
Sick of being pleasant and reasonable at company retreats?

157
00:06:59,215 --> 00:07:03,474
Try Pedantry, a product of Misanthropy Incorporated.

158
00:07:03,750 --> 00:07:04,850
I can't say words.

159
00:07:05,500 --> 00:07:08,760
With Pedantry, you can ignore even the most well

160
00:07:08,760 --> 00:07:11,580
intentioned person by correcting their grammar.

161
00:07:11,990 --> 00:07:16,280
You can lose and alienate loved ones by picking apart their sentence structure.

162
00:07:16,530 --> 00:07:20,440
You can even be ostracized by critiquing your friend's pronunciation.

163
00:07:20,989 --> 00:07:25,560
Yes, Pedantry is here to make your life as lonely and miserable as possible.

164
00:07:25,760 --> 00:07:30,925
Sign up now, and we'll send you a hefty supply of grammar Nazi Absolutely free.

165
00:07:31,455 --> 00:07:32,675
There was actually a couple of split

166
00:07:32,675 --> 00:07:34,175
infinitives in there that we need to talk about.

167
00:07:35,195 --> 00:07:35,825
At least one.

168
00:07:37,345 --> 00:07:41,235
Did you know that rule was made up by like some German

169
00:07:41,324 --> 00:07:45,174
editor in like the 1800s and everybody was just like, yeah,

170
00:07:45,185 --> 00:07:47,115
that's the rule we're going to follow from here on out.

171
00:07:47,660 --> 00:07:48,070
Yeah,

172
00:07:48,130 --> 00:07:52,180
he noticed that in Latin, you never split infinitives.

173
00:07:52,250 --> 00:07:54,750
Therefore, that should be a rule in all the

174
00:07:54,750 --> 00:07:56,830
other languages that were descended from it.

175
00:07:57,200 --> 00:08:01,870
The trouble is, the way that words are structured in Latin, you literally

176
00:08:01,870 --> 00:08:02,290
can't.

177
00:08:02,830 --> 00:08:03,680
Exactly.

178
00:08:04,110 --> 00:08:07,870
And also, English is not completely derived from Latin,

179
00:08:08,380 --> 00:08:11,870
as any cursory overview of the language will show you.

180
00:08:12,230 --> 00:08:16,100
But anyway, I've reached a point in my life and career.

181
00:08:16,370 --> 00:08:19,550
where I've recognized that, you know what, being pedantic

182
00:08:19,600 --> 00:08:23,850
and exacting about language is not always the best solution.

183
00:08:23,880 --> 00:08:26,120
I know that that is heresy, Chris.

184
00:08:26,180 --> 00:08:27,140
But mostly?

185
00:08:27,650 --> 00:08:29,169
Probably not even mostly.

186
00:08:29,780 --> 00:08:35,530
Are there situations that call for using your lexicon with exacting precision?

187
00:08:36,000 --> 00:08:36,600
Certainly.

188
00:08:36,970 --> 00:08:40,350
Is that situation a casual conversation with a colleague or friend?

189
00:08:40,850 --> 00:08:42,789
No, Chris, it's not.

190
00:08:44,900 --> 00:08:46,079
This is going to bother you so much.

191
00:08:46,079 --> 00:08:46,490
I love it.

192
00:08:47,030 --> 00:08:48,290
Words mean things.

193
00:08:48,815 --> 00:08:51,355
But what they mean is constantly evolving and

194
00:08:51,355 --> 00:08:53,855
changing based on how humans use language.

195
00:08:54,475 --> 00:08:59,495
There's no right way, except what we've collectively decided is right.

196
00:09:00,114 --> 00:09:02,914
Remember, language isn't physics or mathematics.

197
00:09:03,194 --> 00:09:06,054
There's no natural law or inherent rules.

198
00:09:06,605 --> 00:09:11,585
Just humans being silly and trying badly to communicate with each other.

199
00:09:12,314 --> 00:09:16,485
Just remember, language literally evolves.

200
00:09:18,275 --> 00:09:20,765
Oh, you really wanted to get the literally in there, didn't you?

201
00:09:21,065 --> 00:09:21,825
I appreciate it.

202
00:09:22,245 --> 00:09:23,975
I just wanted to decimate your argument.

203
00:09:24,364 --> 00:09:25,935
Do you even know what decimate means?

204
00:09:26,595 --> 00:09:27,885
It means multiply by 10.

205
00:09:29,785 --> 00:09:31,765
For the most part, I've stopped correcting people

206
00:09:31,775 --> 00:09:34,765
on the use of on premises versus on premise.

207
00:09:35,075 --> 00:09:36,785
I don't care.

208
00:09:36,855 --> 00:09:37,965
I know what you mean.

209
00:09:38,265 --> 00:09:41,334
I also don't care whether you've capitalized VMware properly.

210
00:09:41,725 --> 00:09:43,405
And neither does OneNote, by the way.

211
00:09:44,115 --> 00:09:46,094
I'm convinced Microsoft does that on purpose.

212
00:09:46,734 --> 00:09:47,374
SMI.

213
00:09:48,134 --> 00:09:51,582
And I've just accepted that AI and ML, like literally

214
00:09:51,582 --> 00:09:55,355
and figuratively, are going to be used interchangeably.

215
00:09:57,295 --> 00:10:00,515
And for most situations, that's fine.

216
00:10:00,925 --> 00:10:02,255
Oh, I couldn't care less.

217
00:10:02,754 --> 00:10:04,004
You mean you couldn't care more?

218
00:10:04,445 --> 00:10:05,435
Or couldn't I?

219
00:10:06,844 --> 00:10:10,205
And yet, Supercloud really chaps my ass.

220
00:10:10,755 --> 00:10:13,474
Part of this discussion is an attempt to define

221
00:10:13,485 --> 00:10:16,545
Supercloud and how it's used, but the other part is a

222
00:10:16,545 --> 00:10:20,174
personal exploration of why this term bothers me so much.

223
00:10:20,824 --> 00:10:22,824
Cue the soft soothing zen music.

224
00:10:23,524 --> 00:10:27,444
There better be a, like a pan flute, or I'm just going to flip a table.

225
00:10:27,859 --> 00:10:28,560
Not this one.

226
00:10:28,560 --> 00:10:31,219
This one's too heavy, but I'll find a table and I'll flip it.

227
00:10:31,280 --> 00:10:32,119
God damn it.

228
00:10:33,520 --> 00:10:33,949
Okay.

229
00:10:34,040 --> 00:10:37,689
I tried to go into this with happiness, sunshine, and

230
00:10:37,689 --> 00:10:41,329
rainbows in my blood and just like feeling the Zen, feeling

231
00:10:41,329 --> 00:10:44,079
the flow, feeling the vibe, and I did not get there, Chris.

232
00:10:44,480 --> 00:10:45,850
So what you're saying is you're lying to the

233
00:10:45,850 --> 00:10:46,340
listeners

234
00:10:46,369 --> 00:10:46,559
and

235
00:10:46,559 --> 00:10:46,869
yourself.

236
00:10:47,599 --> 00:10:50,380
You went into this with malice aforethought, and we both know it.

237
00:10:50,589 --> 00:10:51,060
Okay,

238
00:10:51,530 --> 00:10:52,190
I tried.

239
00:10:52,430 --> 00:10:53,670
An attempt was made.

240
00:10:53,670 --> 00:10:59,469
So I'd like to first acknowledge that the term SuperCloud has been

241
00:10:59,469 --> 00:11:03,939
around since at least 2016, and if you google slash DuckDuckGo

242
00:11:04,249 --> 00:11:08,819
it, you will get a website from Cornell that is an actual software

243
00:11:08,829 --> 00:11:12,800
project to allow For application migrations between clouds.

244
00:11:13,410 --> 00:11:15,400
Having nothing to do with the way it's being used now.

245
00:11:15,910 --> 00:11:18,659
The second hit is actually an MIT web page about a

246
00:11:18,659 --> 00:11:21,870
project they called SuperCloud that was meant to enhance

247
00:11:21,870 --> 00:11:26,890
collaboration between MIT Lincoln Labs, students, and faculty.

248
00:11:27,509 --> 00:11:29,549
So again, nothing to do with this term.

249
00:11:30,100 --> 00:11:32,500
But my point is that the term is not exactly new.

250
00:11:32,600 --> 00:11:33,940
People have thought of it before.

251
00:11:34,530 --> 00:11:36,844
And we can trace the origin of its use to Microsoft.

252
00:11:37,165 --> 00:11:41,075
In the current context, back to a post on SiliconANGLE

253
00:11:41,575 --> 00:11:45,765
called The Rise of Supercloud, which is not written in title

254
00:11:45,765 --> 00:11:49,314
case, just to poke the pendant in me a little bit more.

255
00:11:49,875 --> 00:11:50,415
Thanks.

256
00:11:51,235 --> 00:11:55,374
So, if you're not familiar with SiliconANGLE, and hey, if they can't capitalize

257
00:11:55,394 --> 00:11:59,295
things right, then I can't be bothered with their name capitalization either.

258
00:11:59,665 --> 00:12:01,185
You'll appreciate that if you're looking at the

259
00:12:01,185 --> 00:12:05,390
Google Doc, which, You aren't, but here we are.

260
00:12:06,160 --> 00:12:06,780
Just roll with it.

261
00:12:07,349 --> 00:12:11,630
They are an industry analysis and news firm that is probably best known

262
00:12:11,630 --> 00:12:16,759
for theCube, which is usually recorded live at various tech conferences

263
00:12:16,910 --> 00:12:21,739
with hosts like Dave Valente and John Furrier chatting with vendors,

264
00:12:21,909 --> 00:12:25,689
other analysts, or themselves about what's going on in the tech industry.

265
00:12:26,064 --> 00:12:27,844
Sometimes the microphones are even on.

266
00:12:28,774 --> 00:12:29,584
Usually on.

267
00:12:30,724 --> 00:12:31,984
It's a professional outfit.

268
00:12:32,025 --> 00:12:33,375
They wear suits, Chris.

269
00:12:33,545 --> 00:12:35,094
That's how you know it's serious.

270
00:12:35,684 --> 00:12:37,104
I saw a TV show about that.

271
00:12:38,314 --> 00:12:40,794
Ironically, it was not a serious TV show.

272
00:12:42,354 --> 00:12:43,914
And I used irony properly.

273
00:12:44,244 --> 00:12:44,934
Huzzah.

274
00:12:46,324 --> 00:12:49,930
As someone who has done some work as an analyst, I can

275
00:12:49,930 --> 00:12:53,260
say that your primary job is to make shit up and try to

276
00:12:53,260 --> 00:12:57,209
make it catchy so your brand or your firm gains traction.

277
00:12:57,800 --> 00:13:00,680
I'm sorry, I believe you mean a percentage of my share?

278
00:13:00,680 --> 00:13:03,249
Ouch.

279
00:13:03,710 --> 00:13:07,750
For example, uh, consider the Magic Quadrant from Gartner.

280
00:13:08,360 --> 00:13:09,099
You know it?

281
00:13:09,440 --> 00:13:11,090
You love it?

282
00:13:11,550 --> 00:13:14,060
You might even think there's some hard science behind it.

283
00:13:14,560 --> 00:13:16,740
I assure you, there is not.

284
00:13:17,240 --> 00:13:20,860
For all the talk of qualitative versus quantitative measurement

285
00:13:20,899 --> 00:13:25,769
of vendor products, most of it is just a gut feeling and a guess.

286
00:13:26,325 --> 00:13:27,495
When I say most, I mean all.

287
00:13:28,065 --> 00:13:31,765
Well, you did say magic, so It's in the name.

288
00:13:32,945 --> 00:13:39,285
So analysts, as a job, you have to take multiple briefings a week from vendors,

289
00:13:39,715 --> 00:13:44,835
and you absolutely do not have time to test drive any of these solutions.

290
00:13:45,375 --> 00:13:49,755
In most cases, you do try to apply a skeptical eye to what the

291
00:13:49,755 --> 00:13:54,605
vendor is telling you, but not too skeptical, because you have to

292
00:13:54,605 --> 00:13:58,635
stay in the good graces of the vendor if you want future briefings.

293
00:13:59,300 --> 00:14:01,740
Hmm, that's not a perverse incentive or anything.

294
00:14:01,850 --> 00:14:03,710
Ugh, I mean, it is fraught.

295
00:14:03,939 --> 00:14:04,610
I'll say that.

296
00:14:05,310 --> 00:14:10,500
So, you take the briefing, maybe you read some of the white papers, the

297
00:14:10,500 --> 00:14:14,990
marketing, whatever, you peruse the website, and then you do a quick write

298
00:14:15,000 --> 00:14:18,520
up and move on with to the next briefing that you have on your calendar.

299
00:14:19,030 --> 00:14:23,565
Now, analyst firms make money In two ways, broadly.

300
00:14:23,935 --> 00:14:27,545
The main way is by selling their analysis to companies

301
00:14:27,715 --> 00:14:30,715
who don't want to or can't do the research on their own.

302
00:14:31,365 --> 00:14:33,934
They also make money by doing research for the same

303
00:14:33,934 --> 00:14:37,425
vendors that they are supposed to be impartially judging.

304
00:14:38,785 --> 00:14:40,815
I'm going to admit, it is a weird industry.

305
00:14:41,344 --> 00:14:44,285
I'm not accusing anyone of unethical behavior.

306
00:14:44,735 --> 00:14:48,925
You 100 percent can maintain your morals and still get paid.

307
00:14:49,285 --> 00:14:52,235
But it does introduce the potential for pay to

308
00:14:52,235 --> 00:14:56,755
play and other, shall we say, below board behavior?

309
00:14:57,584 --> 00:14:58,814
So that was quite a tangent.

310
00:14:58,954 --> 00:15:00,534
Why did I even get into all that?

311
00:15:01,354 --> 00:15:02,175
Irish coffee?

312
00:15:02,364 --> 00:15:02,764
Yeah.

313
00:15:04,345 --> 00:15:04,485
Woo!

314
00:15:05,374 --> 00:15:05,865
Uh, no.

315
00:15:06,265 --> 00:15:07,194
The super cloud.

316
00:15:07,245 --> 00:15:08,144
That's, that's where.

317
00:15:08,145 --> 00:15:08,644
Oh, yeah.

318
00:15:08,645 --> 00:15:08,985
Yeah.

319
00:15:08,995 --> 00:15:09,794
Forgot about.

320
00:15:09,885 --> 00:15:10,145
Alright.

321
00:15:10,145 --> 00:15:14,974
So, analyst firms need you, the ostensible

322
00:15:14,984 --> 00:15:17,784
customer, to trust what they are saying.

323
00:15:18,334 --> 00:15:20,165
They need to be thought leaders.

324
00:15:20,734 --> 00:15:23,594
They need to be on the cutting edge of what's happening in the industry.

325
00:15:23,975 --> 00:15:27,335
And there's no better way to do that than making up a new

326
00:15:27,335 --> 00:15:30,965
term and convincing everyone it's useful and relevant.

327
00:15:31,725 --> 00:15:33,655
Gartner has their magic quadrant.

328
00:15:34,005 --> 00:15:36,524
Forrester has the wave.

329
00:15:37,425 --> 00:15:39,934
And I guess SiliconANGLE has rolled out the supercloud?

330
00:15:40,405 --> 00:15:41,665
Rerolled it, I guess.

331
00:15:42,155 --> 00:15:43,264
Rickrolled it?

332
00:15:43,265 --> 00:15:44,845
Because we never got to give it up.

333
00:15:44,845 --> 00:15:47,155
They might never let it down.

334
00:15:47,255 --> 00:15:47,795
I don't know.

335
00:15:48,355 --> 00:15:49,405
Why supercloud?

336
00:15:49,835 --> 00:15:52,034
Didn't we already have enough cloudy terms, Chris?

337
00:15:52,405 --> 00:15:53,185
One would think.

338
00:15:53,665 --> 00:15:55,655
Let's review some of my favorite examples.

339
00:15:56,065 --> 00:15:56,885
Hybrid cloud.

340
00:15:56,994 --> 00:16:00,135
Running applications in your data center and the public cloud.

341
00:16:00,515 --> 00:16:01,295
Multicloud.

342
00:16:01,494 --> 00:16:03,635
Running applications in multiple clouds.

343
00:16:03,935 --> 00:16:04,674
Private cloud.

344
00:16:04,874 --> 00:16:07,015
Running applications in a non public cloud.

345
00:16:07,284 --> 00:16:07,975
Public cloud.

346
00:16:08,395 --> 00:16:11,145
Running applications in a public cloud.

347
00:16:11,384 --> 00:16:12,995
Multitenant environment.

348
00:16:13,514 --> 00:16:14,484
Community Cloud.

349
00:16:14,834 --> 00:16:16,734
Running applications in a cloud that has

350
00:16:16,734 --> 00:16:18,714
really strict rules about who can use them.

351
00:16:19,185 --> 00:16:20,535
Fuuuuuuuuuuuuuuuuck.

352
00:16:20,645 --> 00:16:21,135
Cloud.

353
00:16:21,504 --> 00:16:22,454
How I feel every morning.

354
00:16:23,895 --> 00:16:25,335
We've got a lot of terms here.

355
00:16:25,814 --> 00:16:29,375
that define a lot of ways to deploy and manage applications

356
00:16:29,425 --> 00:16:32,564
and all of them seem to have this cloud term attached.

357
00:16:33,155 --> 00:16:34,084
What's that all about?

358
00:16:34,365 --> 00:16:35,845
Why so much cloud, Chris?

359
00:16:36,475 --> 00:16:38,245
Well, I mean, we're talking about the cloud.

360
00:16:38,245 --> 00:16:40,075
One would assume that the word would show up

361
00:16:40,075 --> 00:16:41,184
every once in a while.

362
00:16:41,834 --> 00:16:44,324
See, the term cloud has been used into oblivion.

363
00:16:45,015 --> 00:16:47,075
If I had to define it, I think of cloud as

364
00:16:47,075 --> 00:16:49,855
an operational model more than anything else.

365
00:16:49,965 --> 00:16:54,025
You know, it's about things like automation, elasticity, self

366
00:16:54,025 --> 00:16:58,745
service, I And Measuring Consumption, you know, that NIST definition.

367
00:16:59,365 --> 00:17:01,695
It wasn't so bad, like, they did a pretty good job.

368
00:17:03,045 --> 00:17:05,155
Yeah, I mean, what ended up happening is that the

369
00:17:05,155 --> 00:17:09,305
language turned Cloud into a verb as well as a noun.

370
00:17:09,565 --> 00:17:12,495
And that's where a lot of the problem comes in as you're mixing definitions.

371
00:17:13,045 --> 00:17:16,065
Which is why we had so many names for things that

372
00:17:16,065 --> 00:17:18,265
don't have all that much difference between them.

373
00:17:18,785 --> 00:17:22,625
Right, but it's different implementations of the same operational model.

374
00:17:22,625 --> 00:17:22,675
Right.

375
00:17:23,335 --> 00:17:26,125
It mostly has to do with where your applications are running.

376
00:17:27,665 --> 00:17:31,805
So, Supercloud, as a term, came to exist because Silicon Angle

377
00:17:31,845 --> 00:17:35,395
analyst John Furrier was trying to invent a term to describe

378
00:17:35,435 --> 00:17:39,125
a trend he and others had observed in the tech landscape.

379
00:17:39,645 --> 00:17:44,685
Simply put, there were a bunch of technology vendors building new platforms

380
00:17:44,695 --> 00:17:50,615
based on the primitives of the public cloud vendors, like AWS, Azure, and GCP.

381
00:17:50,825 --> 00:17:54,265
So, we're talking about Infrastructure as a Service coming from any of

382
00:17:54,265 --> 00:17:58,955
those vendors, or maybe even Platform as a Service, like RDS or Azure SQL.

383
00:17:59,655 --> 00:18:03,265
And these vendors were building higher level abstractions.

384
00:18:03,570 --> 00:18:08,080
And offering those to customers as an alternative of building it themselves.

385
00:18:08,810 --> 00:18:12,780
Now, if that sounds suspiciously like, uh, SaaS, you're not wrong.

386
00:18:13,250 --> 00:18:16,309
Cause it is X as a service X as a service.

387
00:18:16,309 --> 00:18:16,639
Sure.

388
00:18:17,270 --> 00:18:21,639
So I also noticed this trend of what I would call cloud native

389
00:18:21,639 --> 00:18:26,659
companies and products that aren't SaaS in the traditional sense, but

390
00:18:26,659 --> 00:18:30,770
they are using public cloud primitives to build out their platform.

391
00:18:31,210 --> 00:18:33,910
And when I use the word platform, I'm using that.

392
00:18:34,480 --> 00:18:40,230
For a reason, I'm talking about a set of technologies that another company would

393
00:18:40,230 --> 00:18:45,330
use to build their product or application that they would offer to end users.

394
00:18:46,159 --> 00:18:49,669
In the same way that Oracle has a database platform used

395
00:18:49,669 --> 00:18:52,520
by thousands of companies to build their applications.

396
00:18:53,270 --> 00:18:56,270
A super cloud offering would do the same, but with

397
00:18:56,280 --> 00:18:59,169
the added benefit of offering it as a service.

398
00:18:59,820 --> 00:19:01,629
I mean, you can get Oracle as a service.

399
00:19:02,400 --> 00:19:05,009
I feel like a lot of this would be cleared up

400
00:19:05,009 --> 00:19:07,600
in 30 seconds with a whiteboard demonstration.

401
00:19:08,070 --> 00:19:08,499
It might.

402
00:19:09,219 --> 00:19:11,539
Since this is an audio medium, I'm going to do

403
00:19:11,539 --> 00:19:13,709
an audio whiteboard, which takes a lot longer.

404
00:19:14,159 --> 00:19:15,859
Pictures of a thousand words, etc.

405
00:19:15,899 --> 00:19:16,120
Yeah.

406
00:19:17,299 --> 00:19:20,049
So the cognitive dissonance here lies in the

407
00:19:20,049 --> 00:19:23,379
difference between a platform and an application.

408
00:19:23,679 --> 00:19:27,419
And I'll be the first to admit that that is a tenuous distinction at best.

409
00:19:27,989 --> 00:19:31,740
And it harkens back to the old defense of, I know it when I see it.

410
00:19:32,779 --> 00:19:34,270
Maybe some examples are in order.

411
00:19:34,679 --> 00:19:35,929
That might clarify things.

412
00:19:36,519 --> 00:19:38,689
So, an example would be Snowflake.

413
00:19:39,100 --> 00:19:41,770
They built out a data warehouse and analytics

414
00:19:41,830 --> 00:19:45,540
platform that sits astride the public clouds.

415
00:19:46,040 --> 00:19:51,745
Now, your average end user is not going to directly interface with Snowflake.

416
00:19:51,965 --> 00:19:54,795
Instead, they're going to use an application that leverages

417
00:19:55,035 --> 00:19:58,505
the Snowflake platform, but that fact is abstracted

418
00:19:58,595 --> 00:20:02,004
from the end user, hidden from the consumer entirely.

419
00:20:02,535 --> 00:20:05,055
Another example is, uh, Aviatrix.

420
00:20:05,404 --> 00:20:09,309
They are building a multi cloud networking abstraction solution.

421
00:20:09,530 --> 00:20:13,840
Now, you might use that as the transport for your applications,

422
00:20:14,320 --> 00:20:17,020
but again, this is never going to be customer facing.

423
00:20:17,030 --> 00:20:20,510
The customer who's using your apps has no idea that you're using

424
00:20:20,520 --> 00:20:24,870
Aviatrix to manage the network transport across your clouds.

425
00:20:25,575 --> 00:20:29,004
Now, the differentiation here is traditional software

426
00:20:29,004 --> 00:20:33,155
as a service is generally end user or customer facing.

427
00:20:33,345 --> 00:20:38,134
Think Canva, Office 365, NetSuite, etc.

428
00:20:38,414 --> 00:20:41,294
All of these offerings are consumed by non

429
00:20:41,335 --> 00:20:43,785
technology professionals to get their work done.

430
00:20:44,204 --> 00:20:47,005
In some cases, solutions like Salesforce.

431
00:20:47,085 --> 00:20:51,655
com have drifted into the platform territory, But as I said,

432
00:20:51,745 --> 00:20:55,434
the distinction between platform and SaaS can be a bit tenuous.

433
00:20:55,965 --> 00:20:58,335
Especially for the Salesforce example.

434
00:20:58,725 --> 00:21:00,795
Like that might even end up being its own definition.

435
00:21:00,805 --> 00:21:02,395
Salesforce as a service.

436
00:21:02,945 --> 00:21:06,685
Well, the thing about Salesforce is they bought a whole platform.

437
00:21:07,474 --> 00:21:08,855
So what's the name of it?

438
00:21:08,895 --> 00:21:09,475
Heroku.

439
00:21:09,824 --> 00:21:10,654
They bought Heroku.

440
00:21:10,665 --> 00:21:13,745
So that was like, Hey, this is literally a platform

441
00:21:13,755 --> 00:21:16,034
people build applications on on a regular basis.

442
00:21:16,045 --> 00:21:17,984
So they do have that, but also we're going

443
00:21:17,984 --> 00:21:19,665
to call this Salesforce too.

444
00:21:20,724 --> 00:21:25,574
Also within the larger Salesforce umbrella, they bought like a web

445
00:21:25,574 --> 00:21:29,895
application firewall company, I think at some point, and they also.

446
00:21:30,210 --> 00:21:35,060
Just their actual service has a bunch of programming platforms inside of it.

447
00:21:35,070 --> 00:21:38,320
So it's just like, yes, it is a platform, but it's also a service.

448
00:21:38,340 --> 00:21:39,160
It's confusing.

449
00:21:39,370 --> 00:21:39,700
Anyway.

450
00:21:40,630 --> 00:21:41,589
Maybe they're a cloud.

451
00:21:41,809 --> 00:21:42,290
Maybe they're a service.

452
00:21:42,309 --> 00:21:42,880
Oh god.

453
00:21:43,790 --> 00:21:44,960
It's a cloud inside a cloud.

454
00:21:45,080 --> 00:21:45,529
Dear god.

455
00:21:46,490 --> 00:21:50,429
So, There is a working group definition of Supercloud

456
00:21:50,439 --> 00:21:52,689
you can check out, links in the show notes, etc.

457
00:21:53,310 --> 00:21:56,050
And it attempts to put some formal constraints around

458
00:21:56,060 --> 00:21:59,259
the term Supercloud and what it is intended to mean.

459
00:21:59,629 --> 00:22:04,179
And they allow, they lay out three key characteristics or essential

460
00:22:04,280 --> 00:22:07,489
properties that a Supercloud offering would have to include.

461
00:22:07,890 --> 00:22:12,590
First one, run a set of services across more than one cloud.

462
00:22:12,850 --> 00:22:13,470
Maybe.

463
00:22:13,900 --> 00:22:19,439
Okay, Purpose Built SuperPaaS Layer is the second one, which is a new term!

464
00:22:19,580 --> 00:22:20,520
SuperPaaS!

465
00:22:20,659 --> 00:22:21,149
Fun!

466
00:22:21,820 --> 00:22:24,110
Wait, so we're using a new term to define

467
00:22:24,110 --> 00:22:24,730
a new term?

468
00:22:24,760 --> 00:22:25,300
Yes.

469
00:22:25,610 --> 00:22:26,129
Yes, we are.

470
00:22:26,130 --> 00:22:27,549
Mm hmm.

471
00:22:27,910 --> 00:22:30,559
I swear this is not an Ouroboros type situation.

472
00:22:31,029 --> 00:22:33,450
The last one is Metadata Intelligence.

473
00:22:34,075 --> 00:22:35,785
You probably want me to define that too.

474
00:22:36,225 --> 00:22:36,855
I think we should.

475
00:22:37,005 --> 00:22:38,595
Yeah, let's take it from the top.

476
00:22:38,595 --> 00:22:38,625
Okay.

477
00:22:39,035 --> 00:22:41,105
So the first one is pretty intuitive.

478
00:22:41,315 --> 00:22:44,245
You know, it's a service.

479
00:22:44,245 --> 00:22:45,115
It's multi-cloud.

480
00:22:45,115 --> 00:22:46,255
It's multi-cloud, right?

481
00:22:46,285 --> 00:22:48,415
This application is available across multiple clouds.

482
00:22:48,445 --> 00:22:49,255
Okay, I get that.

483
00:22:49,255 --> 00:22:49,945
That's easy enough.

484
00:22:50,405 --> 00:22:53,075
The second one is a new made up term called Super

485
00:22:53,075 --> 00:22:55,505
Paths Super platform as a service, which no.

486
00:22:56,130 --> 00:22:56,510
Nope.

487
00:22:57,900 --> 00:22:58,440
Stop it.

488
00:22:58,510 --> 00:23:00,330
That's also just multi cloud.

489
00:23:00,620 --> 00:23:02,980
They're trying to describe a platform that spans multiple

490
00:23:02,990 --> 00:23:05,380
clouds and hides the underlying cloud primitives.

491
00:23:05,610 --> 00:23:08,290
That's what a platform is.

492
00:23:08,910 --> 00:23:10,160
We have a word for it.

493
00:23:10,640 --> 00:23:11,210
Don't need a new one.

494
00:23:12,090 --> 00:23:14,060
It would just be a multi cloud platform.

495
00:23:14,220 --> 00:23:14,770
Yes.

496
00:23:15,170 --> 00:23:18,970
The third property simply means that the SuperCloud offering

497
00:23:18,990 --> 00:23:22,740
is aware of the underlying components and it can make informed

498
00:23:22,740 --> 00:23:28,139
decisions based on regionality, cost, reliability, etc.

499
00:23:28,600 --> 00:23:30,610
And that's um, that's just cloud native.

500
00:23:31,155 --> 00:23:31,975
Already has a term.

501
00:23:32,415 --> 00:23:32,795
Right.

502
00:23:33,045 --> 00:23:33,595
Okay.

503
00:23:34,535 --> 00:23:35,735
So those are the properties.

504
00:23:35,885 --> 00:23:38,025
There's also three deployment models.

505
00:23:38,505 --> 00:23:41,705
Single cloud instantiation, which really seems

506
00:23:41,705 --> 00:23:43,985
to contradict the first essential property.

507
00:23:44,275 --> 00:23:45,015
Yeah.

508
00:23:45,994 --> 00:23:51,344
Multi cloud slash multi region and global instantiation,

509
00:23:51,825 --> 00:23:54,595
which again seems like the same thing twice.

510
00:23:54,965 --> 00:23:56,965
So that's a super cloud of super clouds?

511
00:23:57,045 --> 00:23:57,995
Of super clouds.

512
00:23:58,360 --> 00:23:58,860
Nice.

513
00:23:58,860 --> 00:23:59,620
It's a super, super set.

514
00:24:00,120 --> 00:24:01,770
Which actually just gets you back to the empty

515
00:24:01,770 --> 00:24:03,710
set, which is different than the null set.

516
00:24:04,060 --> 00:24:04,150
Ah.

517
00:24:05,070 --> 00:24:07,550
It's too early in the morning for math, we're just going to power on through.

518
00:24:08,569 --> 00:24:10,550
Putting that CS degree to work, baby.

519
00:24:11,110 --> 00:24:15,060
No mention of transubstantiation, which, weird, but okay.

520
00:24:15,619 --> 00:24:18,169
Trying to pick those terms apart.

521
00:24:18,490 --> 00:24:21,160
The key here, I think they're trying to make, is the

522
00:24:21,160 --> 00:24:24,830
distinction of the control plane versus the data services.

523
00:24:25,354 --> 00:24:28,024
So, the deployment model is mostly referring

524
00:24:28,024 --> 00:24:30,725
to how the control plane itself is deployed.

525
00:24:31,245 --> 00:24:34,065
As a consumer, I shouldn't have to care about that at all.

526
00:24:34,375 --> 00:24:36,264
As long as your control plane is available and I

527
00:24:36,264 --> 00:24:39,814
can access it, why do I care how it's deployed?

528
00:24:40,275 --> 00:24:42,574
Give me the right number of 9s and everything

529
00:24:42,574 --> 00:24:44,515
else is just an implementation detail.

530
00:24:44,525 --> 00:24:48,920
Like for instance, Does Office 365 tell me where their control plane is running?

531
00:24:49,420 --> 00:24:49,860
No!

532
00:24:50,650 --> 00:24:51,730
Not even if you ask.

533
00:24:52,260 --> 00:24:52,950
Exactly.

534
00:24:53,550 --> 00:24:54,180
So that's it.

535
00:24:54,439 --> 00:24:59,130
We get three properties of the super cloud and three deployment models.

536
00:24:59,670 --> 00:25:00,960
That contradict each other.

537
00:25:01,530 --> 00:25:02,850
So if I can summarize.

538
00:25:04,405 --> 00:25:07,004
Supercloud is a distributed platform used to build

539
00:25:07,034 --> 00:25:09,605
applications from abstractive cloud primitives.

540
00:25:10,065 --> 00:25:13,295
It's a platform for building applications.

541
00:25:13,874 --> 00:25:16,375
It's a platform.

542
00:25:16,875 --> 00:25:19,065
You ever say the same word so many times

543
00:25:19,065 --> 00:25:21,004
that it just kind of starts to lose meaning?

544
00:25:21,665 --> 00:25:26,985
Platinum, Constantly, Orange, Toy Boat, Toy Boat, Toy Boat, Toy Boat, Toy Boat.

545
00:25:28,085 --> 00:25:32,225
So Supercloud is as Supercloud does.

546
00:25:32,845 --> 00:25:35,735
Does this new term need to exist?

547
00:25:36,375 --> 00:25:36,975
No.

548
00:25:37,075 --> 00:25:37,765
No.

549
00:25:37,984 --> 00:25:38,294
Sweet.

550
00:25:38,325 --> 00:25:38,994
Episode over.

551
00:25:39,144 --> 00:25:39,524
Bye.

552
00:25:39,934 --> 00:25:40,424
Good work.

553
00:25:40,664 --> 00:25:40,914
Thanks.

554
00:25:41,164 --> 00:25:41,425
Just kidding.

555
00:25:41,434 --> 00:25:42,404
Let's go get sandwiches.

556
00:25:43,284 --> 00:25:48,005
In the working definition document, they address that very question in an FAQ.

557
00:25:48,345 --> 00:25:49,595
And I thought I would just quote it.

558
00:25:50,645 --> 00:25:53,395
Quote, There is broad agreement that clouds in

559
00:25:53,404 --> 00:25:56,445
the 2020s are different from clouds in the 2010s.

560
00:25:57,215 --> 00:25:59,695
Lot more cumulonimbus, I think.

561
00:26:00,035 --> 00:26:00,875
Sorry, that was an aside.

562
00:26:01,815 --> 00:26:07,595
That something new is happening within the AWS and other cloud ecosystems.

563
00:26:07,835 --> 00:26:13,605
beyond traditional IaaS and PaaS, and isn't just SaaS running in the cloud.

564
00:26:14,045 --> 00:26:18,124
Supercloud is an attempt to describe a new architecture that integrates

565
00:26:18,425 --> 00:26:22,405
infrastructure, unique platform attributes, and software to solve

566
00:26:22,415 --> 00:26:26,944
specific problems that public cloud vendors aren't directly addressing.

567
00:26:26,945 --> 00:26:29,785
Supercloud is an evocative term that

568
00:26:29,805 --> 00:26:32,395
catalyzes debate, conversation, and thought.

569
00:26:33,060 --> 00:26:34,500
So, that's the end of the quote.

570
00:26:35,250 --> 00:26:38,400
Basically, what that tells me is, this is a term for stirring the pot.

571
00:26:38,880 --> 00:26:39,870
It's exciting.

572
00:26:39,980 --> 00:26:41,420
It gets the people going.

573
00:26:42,429 --> 00:26:46,510
It's a term that elevates the profile of those who invented it.

574
00:26:46,925 --> 00:26:51,425
It's a term that can be trademarked and used for marketing purposes, if desired.

575
00:26:52,024 --> 00:26:52,835
And it's desired.

576
00:26:53,355 --> 00:26:53,675
Right.

577
00:26:54,375 --> 00:26:55,165
What do you mean, if?

578
00:26:55,795 --> 00:27:00,344
It's a term that is both useful for debate and useless for anything practical.

579
00:27:00,955 --> 00:27:04,464
It's the change my mind Steven Crowder meme.

580
00:27:04,544 --> 00:27:08,445
Worse yet, it might even be the Ben Shapiro of cloud terms.

581
00:27:09,015 --> 00:27:10,405
Whoa, too far.

582
00:27:10,685 --> 00:27:11,324
Whoa.

583
00:27:11,824 --> 00:27:12,245
Yeah.

584
00:27:12,475 --> 00:27:12,794
Okay.

585
00:27:13,685 --> 00:27:14,135
Fair enough.

586
00:27:14,165 --> 00:27:15,225
That might've been too far.

587
00:27:15,245 --> 00:27:16,125
I'll take that one back.

588
00:27:16,775 --> 00:27:19,475
No one deserves to be called the Ben Shapiro of anything.

589
00:27:19,975 --> 00:27:20,405
Thank you.

590
00:27:20,835 --> 00:27:21,165
Okay.

591
00:27:21,704 --> 00:27:23,464
And shit, you know, it's working.

592
00:27:23,984 --> 00:27:24,975
I'm talking about it.

593
00:27:25,514 --> 00:27:27,984
It was discussed in an it round table at

594
00:27:27,984 --> 00:27:30,745
cloud field day 15 link in the show notes.

595
00:27:31,345 --> 00:27:35,635
I've heard it mentioned on podcasts in articles and blog posts.

596
00:27:35,975 --> 00:27:41,969
Now, most of them are dismissive of the term at best, but They are engaging.

597
00:27:42,420 --> 00:27:43,610
Does that make me culpable?

598
00:27:44,100 --> 00:27:45,429
Am I part of the problem?

599
00:27:46,239 --> 00:27:47,860
I've been telling you that for years.

600
00:27:48,620 --> 00:27:50,320
That's because we're all pundits now, Chris.

601
00:27:51,800 --> 00:27:53,179
Gotta feed the content machine.

602
00:27:54,550 --> 00:27:58,769
If you're an analyst or a marketing firm, supercloud is a term that will likely

603
00:27:58,780 --> 00:28:04,419
be used to imply or imbue some mystical properties on a product or service.

604
00:28:04,820 --> 00:28:09,060
Leverage the supercloud with pedantry from Misanthropy Inc.

605
00:28:10,310 --> 00:28:12,120
Subsidiary of Salesforce.

606
00:28:13,260 --> 00:28:13,899
Probably.

607
00:28:14,209 --> 00:28:15,169
They just acquired us.

608
00:28:15,520 --> 00:28:16,129
1.

609
00:28:16,129 --> 00:28:16,510
6 million.

610
00:28:17,919 --> 00:28:19,629
Is it useful to practitioners?

611
00:28:20,215 --> 00:28:21,035
Probably not.

612
00:28:21,475 --> 00:28:26,275
If I am an application architect and I need a data platform, I can evaluate

613
00:28:26,275 --> 00:28:31,515
Snowflake, AWS Aurora slash Redshift, and Oracle and decide which one meets

614
00:28:31,515 --> 00:28:35,415
my requirements without throwing some kind of weird terminology into the mix.

615
00:28:35,990 --> 00:28:39,990
If I'm, I don't know, working on a platform team at an enterprise,

616
00:28:40,409 --> 00:28:45,320
I might be interested in a super cloud type product to integrate

617
00:28:45,330 --> 00:28:49,219
into the platform I offer to my product teams in my organization.

618
00:28:50,060 --> 00:28:53,580
But again, the super cloud terminology itself, not all that useful.

619
00:28:54,060 --> 00:28:57,079
Especially since we've already got words for all of that.

620
00:28:57,219 --> 00:28:57,780
I know.

621
00:28:58,250 --> 00:29:02,190
Does the term group similar offerings into a category

622
00:29:02,250 --> 00:29:04,980
where they can be compared fairly on their merits?

623
00:29:05,475 --> 00:29:08,754
Not really, which would actually be a useful thing to do.

624
00:29:09,324 --> 00:29:11,365
What does NetApp vs.

625
00:29:11,544 --> 00:29:12,685
Snowflake vs.

626
00:29:13,135 --> 00:29:14,504
VMware have to do with each other?

627
00:29:15,175 --> 00:29:19,175
Ooh, ooh, we can compare the swag bags we get at conferences.

628
00:29:19,435 --> 00:29:20,185
Ooh, that's true.

629
00:29:20,714 --> 00:29:23,275
In my experience, NetApp has been the best with the swag.

630
00:29:24,040 --> 00:29:25,120
I was going to say one time

631
00:29:25,120 --> 00:29:25,179
I

632
00:29:25,179 --> 00:29:25,929
got a wind up

633
00:29:25,929 --> 00:29:26,649
dancing robot.

634
00:29:27,449 --> 00:29:30,909
I got a like a raspberry pi robot assembly from them.

635
00:29:31,150 --> 00:29:33,790
Yeah, stop bragging about how many raspberry pies people give you.

636
00:29:33,839 --> 00:29:35,509
So many, so many.

637
00:29:36,459 --> 00:29:38,030
None of these vendors have anything to do with each

638
00:29:38,030 --> 00:29:40,260
other, but they all could have a super cloud product.

639
00:29:41,479 --> 00:29:45,690
So what we're really doing here is grouping together disparate product offerings

640
00:29:45,740 --> 00:29:49,640
and rolling them into a useless category for comparison and evaluation.

641
00:29:49,810 --> 00:29:53,450
So I think it also fails as a term used by analysts as well.

642
00:29:54,085 --> 00:29:58,125
Yeah, which is why I have a feeling, A, if it does

643
00:29:58,125 --> 00:30:01,025
continue to be used, it's going to evolve again.

644
00:30:01,625 --> 00:30:04,295
But B, I kind of feel like it's just not

645
00:30:04,305 --> 00:30:07,465
going to get used because it's not precise.

646
00:30:08,025 --> 00:30:08,815
Well, that's never stopped

647
00:30:08,815 --> 00:30:09,315
anybody.

648
00:30:10,665 --> 00:30:12,715
But I mean, at the end of the day, it is what it is.

649
00:30:13,275 --> 00:30:17,745
Which is everything and nothing at the same time, which is a paradox.

650
00:30:17,875 --> 00:30:18,755
Isn't it ironic?

651
00:30:19,285 --> 00:30:23,775
Don't you think I do and Atlantis would agree that this is really just a

652
00:30:23,775 --> 00:30:28,815
marketing term with a touch of self promotion from Silicon angle And we already

653
00:30:28,815 --> 00:30:32,855
have a term for what they're talking about and it's called cross cloud platform.

654
00:30:33,355 --> 00:30:34,635
What are you multi cloud?

655
00:30:35,135 --> 00:30:37,145
I'm building a multicloud Cloud is great.

656
00:30:37,495 --> 00:30:39,625
Yes, I'm building a multi-cloud platform.

657
00:30:39,835 --> 00:30:40,345
Done.

658
00:30:40,635 --> 00:30:41,025
Did it.

659
00:30:41,115 --> 00:30:41,865
Have a term.

660
00:30:41,955 --> 00:30:42,975
Don't need another one.

661
00:30:43,035 --> 00:30:43,605
Thanks a lot.

662
00:30:43,605 --> 00:30:44,055
High five.

663
00:30:44,265 --> 00:30:44,685
Nailed it.

664
00:30:44,685 --> 00:30:45,015
Boom.

665
00:30:45,195 --> 00:30:45,735
Nailed it.

666
00:30:46,175 --> 00:30:49,475
So I will be happy to never mention Supercloud again.

667
00:30:51,660 --> 00:30:52,250
Like a fish?

668
00:30:53,020 --> 00:30:53,410
Hmm.

669
00:30:53,740 --> 00:30:54,370
I like fish.

670
00:30:54,600 --> 00:30:55,260
Left shark?

671
00:30:55,660 --> 00:30:56,300
Right shark?

672
00:30:56,610 --> 00:30:58,619
Left shark, right shark, left shark, right shark.

673
00:30:59,100 --> 00:30:59,400
Okay.

674
00:31:00,080 --> 00:31:00,670
Landing round?

675
00:31:01,230 --> 00:31:02,470
Sure.

676
00:31:03,080 --> 00:31:03,880
This is so gross.

677
00:31:04,960 --> 00:31:09,510
Amazon announces pre order for Halo Rise because

678
00:31:09,530 --> 00:31:12,650
Bezos literally wants to watch you sleep.

679
00:31:13,660 --> 00:31:16,040
This has nothing to do with the Halo show.

680
00:31:16,650 --> 00:31:20,040
No, it has to do with the Halo stream of products from Amazon.

681
00:31:20,400 --> 00:31:21,550
I don't know what the hell that is.

682
00:31:21,670 --> 00:31:22,060
Okay.

683
00:31:22,170 --> 00:31:24,610
It's a whole, can I just talk?

684
00:31:24,980 --> 00:31:25,390
Maybe?

685
00:31:25,860 --> 00:31:28,920
Last month brought the announcement that Amazon wanted to buy

686
00:31:28,980 --> 00:31:33,405
iRobot, the company that is most famous for the Roomba, which Bad

687
00:31:33,405 --> 00:31:36,385
enough that now Amazon wants to know what your house looks like.

688
00:31:36,765 --> 00:31:39,815
Now they're releasing a sleep tracker slash alarm clock

689
00:31:39,845 --> 00:31:42,755
combination that observes your night moves from the

690
00:31:42,765 --> 00:31:47,015
bedside table, and of course, can integrate into Alexa.

691
00:31:47,175 --> 00:31:49,035
Will it help me work on my night moves?

692
00:31:49,805 --> 00:31:53,145
So you could, in theory, have an automation for the Halo Rise

693
00:31:53,145 --> 00:31:56,395
to, I don't know, alert a smart outlet to power on as you wake

694
00:31:56,395 --> 00:31:59,825
up, thus brewing coffee at the moment you gain consciousness.

695
00:32:00,325 --> 00:32:00,975
Why not?

696
00:32:01,465 --> 00:32:04,025
I have little to say about the sleep tracker itself.

697
00:32:04,590 --> 00:32:07,430
Except to remind people that all consumer sleep tracking

698
00:32:07,430 --> 00:32:10,760
devices are based on inference and averages, and most sleep

699
00:32:10,770 --> 00:32:14,260
doctors recommend against relying on them for anything at all.

700
00:32:14,720 --> 00:32:17,010
If you're having problems, go get a sleep study.

701
00:32:18,130 --> 00:32:21,990
For example, my sleep tracker has recorded me having exactly zero

702
00:32:22,230 --> 00:32:25,700
REM sleep for the past five days, and that can't possibly be accurate

703
00:32:25,730 --> 00:32:28,790
because I feel completely biscuit doppelganger banana nosedive.

704
00:32:30,805 --> 00:32:31,255
I'm back.

705
00:32:31,765 --> 00:32:36,545
The problem I have with this is Amazon's increasing intrusions into

706
00:32:36,735 --> 00:32:41,885
all aspects of our lives, and that is by their own admitted design.

707
00:32:42,775 --> 00:32:48,280
They want their Skynet to be All of our individual Jarvis's.

708
00:32:48,550 --> 00:32:53,850
They also want to misuse all of our most personal information for their profit.

709
00:32:54,520 --> 00:32:58,360
For me to trust this kind of uniform visibility into my life would require

710
00:32:58,360 --> 00:33:03,700
Amazon to have ever been responsible regarding people's PII in the past.

711
00:33:04,330 --> 00:33:09,090
You would think that this would be, I don't know, important to Amazon?

712
00:33:09,960 --> 00:33:12,680
Well, TLDR, it isn't.

713
00:33:13,510 --> 00:33:17,440
Unfortunately, much like Facebook, keeping your data safe is a

714
00:33:17,440 --> 00:33:21,950
bar that Amazon has consistently and repeatedly failed to clear.

715
00:33:22,290 --> 00:33:22,830
Yay?

716
00:33:23,890 --> 00:33:24,920
No, not yay.

717
00:33:25,610 --> 00:33:29,160
Reason number zero, not to run Exchange yourself.

718
00:33:29,600 --> 00:33:33,630
Late on Thursday, September 29th, Microsoft announced a zero day

719
00:33:33,640 --> 00:33:37,880
vulnerability for Microsoft Exchange servers that ranked a whopping 9.

720
00:33:37,930 --> 00:33:39,970
8 on the CVE scale.

721
00:33:40,090 --> 00:33:41,180
So close to 10.

722
00:33:41,180 --> 00:33:42,549
Thought you could have done it.

723
00:33:42,730 --> 00:33:44,840
You know, with a little more gumption, they could have gotten there.

724
00:33:45,380 --> 00:33:47,200
So that's um, bad.

725
00:33:48,050 --> 00:33:49,570
Yes, I have it written down here.

726
00:33:49,875 --> 00:33:51,005
That is bad.

727
00:33:51,575 --> 00:33:52,605
How bad is it?

728
00:33:53,395 --> 00:33:57,755
There are roughly 220, 000 exchange servers running out in the

729
00:33:57,755 --> 00:34:01,615
wild that are internet accessible and vulnerable to the exploit.

730
00:34:01,855 --> 00:34:05,305
Or exploits, rather, since this is a combo attack.

731
00:34:06,095 --> 00:34:10,885
The first is a server side request forgery vulnerability which allows the

732
00:34:10,885 --> 00:34:15,995
attacker to trigger the second, A remote code execution through PowerShell.

733
00:34:16,435 --> 00:34:20,655
Attackers will need valid credentials of at least one email user to

734
00:34:20,655 --> 00:34:25,345
successfully run this attack, so hopefully none of your users have weak or

735
00:34:25,345 --> 00:34:30,905
reused passwords and can't be fooled by phishing or social engineering attacks.

736
00:34:31,385 --> 00:34:35,435
As far as we know, this set of exploits only affects on premises

737
00:34:35,465 --> 00:34:38,845
Exchange servers and not Microsoft's Exchange Online service.

738
00:34:39,500 --> 00:34:43,370
However, if you happen to be running in hybrid mode, which I know

739
00:34:43,370 --> 00:34:47,480
a lot of you are, that pesky hybrid server that you put in a corner

740
00:34:47,480 --> 00:34:51,520
and forgot about, that is still very much vulnerable to this attack.

741
00:34:52,340 --> 00:34:55,710
Microsoft has an advisory post up that details the

742
00:34:55,710 --> 00:34:59,450
vulnerabilities and suggested mitigation strategies.

743
00:34:59,915 --> 00:35:04,485
They all basically boil down to adding a URL rewrite to prevent access

744
00:35:04,505 --> 00:35:09,005
to PowerShell through the AutoDiscover service and disabling PowerShell

745
00:35:09,045 --> 00:35:13,275
access for non admin users, which you probably should have done anyway.

746
00:35:13,730 --> 00:35:16,700
As of this recording, there is no patch for the vulnerability,

747
00:35:16,920 --> 00:35:20,150
but Microsoft is scrambling to get one out the door ASAP.

748
00:35:20,420 --> 00:35:23,710
On an unrelated note, I am available to assist with Office

749
00:35:23,760 --> 00:35:27,420
365 migrations for the low, low price of 400 an hour.

750
00:35:27,690 --> 00:35:30,980
Send inquiries via Carrier Pigeon to NEDS, Northeast

751
00:35:30,980 --> 00:35:33,520
Bay Station Care of Cybernetics Incorporated.

752
00:35:34,440 --> 00:35:36,580
A subsidiary of Salesforce.

753
00:35:36,910 --> 00:35:37,990
A subsidiary, uh,

754
00:35:42,480 --> 00:35:47,100
OpenAI removes waitlists and gives full immediate access to DALI.

755
00:35:47,850 --> 00:35:53,280
Man, the world of AI generating apps is moving fast.

756
00:35:53,720 --> 00:35:56,180
Once upon a time, we had only ever heard of DALI.

757
00:35:56,790 --> 00:36:00,390
Well, I mean, really it was crayon because DALI was only

758
00:36:00,390 --> 00:36:05,540
available to a select few artists, technologists, AI researchers.

759
00:36:06,000 --> 00:36:07,640
That all changed this week though.

760
00:36:08,000 --> 00:36:10,860
OpenAI has decided to grant full public access

761
00:36:10,860 --> 00:36:13,550
to DALI, completely removing the waitlist.

762
00:36:14,130 --> 00:36:17,600
According to OpenAI, this is to expand DALI's capabilities

763
00:36:17,600 --> 00:36:20,110
through widespread use and training, with the company saying

764
00:36:20,110 --> 00:36:23,990
effectively, we need to put it out into the world and let it learn.

765
00:36:24,725 --> 00:36:28,355
Realistically, though, this is probably because competitors in the

766
00:36:28,375 --> 00:36:33,015
AI image generating space, such as Midjourney and Stable Diffusion,

767
00:36:33,025 --> 00:36:36,745
are absolutely eating Dali's lunch when it comes to popularity.

768
00:36:37,505 --> 00:36:43,055
The decision feels fraught, as OpenAI wasn't supposed to just chase users.

769
00:36:43,765 --> 00:36:46,855
The company was designed to work for the benefit

770
00:36:46,885 --> 00:36:50,525
of all humanity and other such high minded goals.

771
00:36:51,175 --> 00:36:54,385
Many hand wringing Twitter users have said that this is going to

772
00:36:54,395 --> 00:36:58,155
be instantly problematic, as this widespread access could lead

773
00:36:58,155 --> 00:37:01,345
to misuse, such as creating offensive or pornographic images.

774
00:37:01,965 --> 00:37:05,545
There is also concern that OpenAI could be overwhelmed with requests,

775
00:37:05,585 --> 00:37:09,330
and that the quality of images Generated could suffer as a result.

776
00:37:09,940 --> 00:37:14,980
Twitter user, at Tim O'Brien, states, The accumulation of ethical debt will

777
00:37:14,980 --> 00:37:19,630
be immediate, while the mop up of the resulting mess will go on in perpetuity.

778
00:37:20,100 --> 00:37:20,620
Love it.

779
00:37:21,170 --> 00:37:22,130
Doesn't that just

780
00:37:22,230 --> 00:37:24,170
describe society, though?

781
00:37:24,550 --> 00:37:25,620
Really, really does.

782
00:37:26,340 --> 00:37:29,660
C and C are looking mighty rusty.

783
00:37:29,880 --> 00:37:31,540
Or rather, they aren't.

784
00:37:32,020 --> 00:37:33,000
Now I'm going to say this up front.

785
00:37:33,650 --> 00:37:35,800
Programming languages don't die.

786
00:37:36,290 --> 00:37:39,220
Just ask any COBOL programmer and they'll answer

787
00:37:39,220 --> 00:37:41,600
in the affirmative all the way to the bank.

788
00:37:42,250 --> 00:37:47,060
So while the death of C or C is not exactly nigh, There is a

789
00:37:47,060 --> 00:37:50,930
young upstart taking the systems programming world by storm.

790
00:37:51,270 --> 00:37:51,860
Rust.

791
00:37:52,340 --> 00:37:57,050
The Rust programming language is considered memory safe by default, meaning

792
00:37:57,060 --> 00:38:00,710
that it won't allow you to make common memory management mistakes like

793
00:38:00,920 --> 00:38:06,280
invalid heap and stack access, memory leaks, and mismatched memory allocation.

794
00:38:06,280 --> 00:38:11,350
These are the kinds of errors that make up the vast majority of CVE

795
00:38:11,360 --> 00:38:17,725
security problems, and it is all too easy to do so in C or C Rust was

796
00:38:17,725 --> 00:38:21,655
designed with security in mind, while still supporting lower level

797
00:38:21,665 --> 00:38:25,755
programming, and for that reason, it is considered a suitable replacement.

798
00:38:26,315 --> 00:38:28,915
The tipping point for many was the coming inclusion

799
00:38:28,945 --> 00:38:32,235
of Rust in the Linux kernel, starting with version 6.

800
00:38:32,275 --> 00:38:32,615
1.

801
00:38:33,175 --> 00:38:33,724
Side note, 6.

802
00:38:33,725 --> 00:38:36,265
0 dropped this past week as expected.

803
00:38:36,905 --> 00:38:41,215
Now, Mark Russinovich, the CTO at Microsoft Azure, has

804
00:38:41,215 --> 00:38:45,115
said that all of his new projects will be written in Rust.

805
00:38:45,395 --> 00:38:49,025
And, as goes Russinovich, so goes Microsoft.

806
00:38:49,305 --> 00:38:53,295
In fact, Microsoft has admitted that upwards of 70 percent

807
00:38:53,315 --> 00:38:56,995
of its CVEs can be traced back to memory unsafe bugs.

808
00:38:57,900 --> 00:39:00,210
Now, that doesn't mean that anyone's going to go rewrite

809
00:39:00,210 --> 00:39:03,590
the Windows kernel in Rust tomorrow, but future development?

810
00:39:04,420 --> 00:39:08,900
We could definitely see a Rustacean creation in 2025.

811
00:39:09,610 --> 00:39:12,970
Totally unrelated note, guess who started learning Rust this week?

812
00:39:13,680 --> 00:39:14,620
Definitely wasn't you.

813
00:39:14,620 --> 00:39:15,380
You're not a learner.

814
00:39:15,710 --> 00:39:16,310
That's true.

815
00:39:16,900 --> 00:39:17,690
I know Kung Fu.

816
00:39:18,160 --> 00:39:20,160
You're wearing a shirt that says, down with books.

817
00:39:21,010 --> 00:39:21,510
That's right.

818
00:39:21,630 --> 00:39:22,380
Videos only.

819
00:39:23,150 --> 00:39:23,930
And podcasts.

820
00:39:24,660 --> 00:39:25,940
Podcasts are better in every way.

821
00:39:26,990 --> 00:39:28,740
Live it, learn it, love it.

822
00:39:30,180 --> 00:39:33,280
Google, moving forward with Manifest V3

823
00:39:33,300 --> 00:39:36,340
mandate, much to society's general disgust.

824
00:39:36,900 --> 00:39:39,690
Advertising company Google happens to be in charge

825
00:39:39,690 --> 00:39:42,480
of the world's most popular browser, Chrome.

826
00:39:43,090 --> 00:39:47,360
Recently, advertising company Google made a dramatic change to the code base

827
00:39:47,360 --> 00:39:52,350
of Chrome to make it harder to use ad blocking and privacy enhancing add ons.

828
00:39:52,840 --> 00:39:56,290
This is solely and exclusively because Google is an advertising

829
00:39:56,300 --> 00:39:59,270
company first and they can't have us running around blocking

830
00:39:59,270 --> 00:40:02,590
ads or protecting our PII from bad actors now, can they?

831
00:40:03,145 --> 00:40:05,135
Not when that shit can be monetized.

832
00:40:07,065 --> 00:40:09,565
Now, a manifest is simply the underpinnings of

833
00:40:09,565 --> 00:40:12,715
how a browser works with third party extensions.

834
00:40:13,185 --> 00:40:19,315
Manifest v3 changes a lot of APIs and operating procedures to the extent

835
00:40:19,315 --> 00:40:25,065
that extensions written under manifest v2 are incompatible with v3.

836
00:40:26,010 --> 00:40:31,640
In fact, a lot of the processes that were made possible by v2, particularly

837
00:40:31,640 --> 00:40:35,070
ones used by the aforementioned ad blocking and privacy enhancing

838
00:40:35,120 --> 00:40:40,410
extensions, are now much more difficult to implement, some impossible.

839
00:40:40,890 --> 00:40:44,370
This is allegedly being done to enhance security.

840
00:40:44,940 --> 00:40:48,790
And I'm sure it's a total coincidence that advertising company

841
00:40:48,790 --> 00:40:52,070
Google made the biggest changes to the ad blocking functionalities.

842
00:40:53,200 --> 00:40:59,960
And in January 2023, it will be mandatory in Chrome to use only version 3.

843
00:41:00,440 --> 00:41:02,900
It's enough to make people want to switch.

844
00:41:03,700 --> 00:41:05,880
And this time, they might actually do it.

845
00:41:06,560 --> 00:41:10,940
Many third party browser companies such as Brave, Firefox,

846
00:41:11,060 --> 00:41:14,150
and even Chromium based Vivaldi have announced that they

847
00:41:14,150 --> 00:41:17,920
will continue to support v2 extensions indefinitely.

848
00:41:18,150 --> 00:41:19,520
Oh, you sweet summer child.

849
00:41:20,005 --> 00:41:21,975
You really think people are going to switch their browsers?

850
00:41:23,395 --> 00:41:27,185
Speaking of Google, Stadia fragged by friendly fire.

851
00:41:27,695 --> 00:41:31,195
There's an absolutely fire post on TechCrunch about the

852
00:41:31,485 --> 00:41:35,495
unexpected death of Stadia that I recommend everyone go read.

853
00:41:35,905 --> 00:41:40,085
Back in the pre COVID times of 2019, when Chris and

854
00:41:40,085 --> 00:41:43,965
I had an eerily similar podcast, we were skeptical.

855
00:41:44,290 --> 00:41:47,920
If not downright dismissive and derisive towards Stadia.

856
00:41:48,350 --> 00:41:52,660
This was both on technical grounds, the required bandwidth for clients and cost

857
00:41:52,660 --> 00:41:57,560
of running at the edge was probably a non starter, and on historical grounds, i.

858
00:41:57,560 --> 00:41:57,750
e.

859
00:41:57,750 --> 00:42:02,550
Google is unlikely to fight a protracted battle in a crowded space, or really

860
00:42:02,550 --> 00:42:06,170
keep any product going for any significant amount of time, Google Reader.

861
00:42:06,610 --> 00:42:07,330
Rest in peace.

862
00:42:07,780 --> 00:42:08,420
Too soon.

863
00:42:09,020 --> 00:42:13,820
Even so, the platform launched with some AAA titles and a few exclusives.

864
00:42:14,240 --> 00:42:17,550
Google seemed to be making the right moves by creating an in house

865
00:42:17,550 --> 00:42:21,930
game studio and hiring people from the games industry, most notably

866
00:42:21,930 --> 00:42:26,040
Phil Harrison, previously at Microsoft and Sony Computer Entertainment.

867
00:42:26,690 --> 00:42:30,090
However, after the fanfare and confetti settled in

868
00:42:30,090 --> 00:42:34,270
November 2019, the sheen immediately started to fade.

869
00:42:34,750 --> 00:42:35,990
Sales were mediocre.

870
00:42:36,380 --> 00:42:40,900
Marketing was all but non existent, Stadia disappeared from Google

871
00:42:40,900 --> 00:42:45,540
presentations, and the in house studio was shuttered in February of 2021.

872
00:42:46,735 --> 00:42:49,965
They are aware that typical AAA games take at

873
00:42:49,965 --> 00:42:52,555
least four years to develop and release, right?

874
00:42:53,085 --> 00:42:53,355
Right?

875
00:42:55,415 --> 00:42:58,555
Oh, the writing was on the wall, and yet Stadia limped

876
00:42:58,555 --> 00:43:02,295
along for another 20 months, loudly denying the inevitable,

877
00:43:02,365 --> 00:43:05,145
before Google finally gave up the ghost last week.

878
00:43:05,455 --> 00:43:09,365
Stadia will officially shutter in 2023, provide refunds

879
00:43:09,365 --> 00:43:11,665
for those who purchased hardware, and stop charging

880
00:43:11,665 --> 00:43:14,345
those with pro subscriptions during the wind down period.

881
00:43:15,025 --> 00:43:17,305
Alas, another service killed by Google.

882
00:43:17,305 --> 00:43:19,925
I wonder if there's a site tracking that sort of thing.

883
00:43:20,685 --> 00:43:21,035
That site

884
00:43:21,105 --> 00:43:22,575
is getting large.

885
00:43:24,495 --> 00:43:28,375
And it's growing in popularity every time another product is killed by Google.

886
00:43:29,090 --> 00:43:32,090
Which there are so, so, so many.

887
00:43:33,200 --> 00:43:34,880
Hey, thanks for listening or something.

888
00:43:34,880 --> 00:43:37,640
I guess you found it worthwhile if you made it all the way to the end.

889
00:43:37,960 --> 00:43:39,640
So congratulations to you friend.

890
00:43:39,700 --> 00:43:40,960
You accomplished something today.

891
00:43:41,050 --> 00:43:44,830
Now go for a hot air balloon ride and compliment a cloud.

892
00:43:45,350 --> 00:43:47,120
Make it feel super.

893
00:43:47,290 --> 00:43:47,680
You've earned it.

894
00:43:48,770 --> 00:43:52,159
You can find me or Chris on Twitter at Ned1313 or

895
00:43:52,160 --> 00:43:54,560
Hainer80 respectively, or follow the show at Chaos

896
00:43:54,610 --> 00:43:56,950
underscore Lever if that's the kind of thing you're into.

897
00:43:57,270 --> 00:43:59,000
Show notes are available at ChaosLever.

898
00:43:59,040 --> 00:44:01,550
com if you like reading things, which you shouldn't.

899
00:44:02,010 --> 00:44:05,410
Podcasts continue to be better in every conceivable way.

900
00:44:05,690 --> 00:44:07,270
Shirt's forthcoming for that one.

901
00:44:07,820 --> 00:44:10,420
We'll be back next week to see what fresh hell is upon us.

902
00:44:10,560 --> 00:44:11,450
Ta ta for now.