What's going on everybody got Kyle and Shawn here relating sports cards. We are ripping. This is 2023 prism first off the line Three box number four random team style Did a ram eyes for the break? I have Eric W with the Patriots down to Eric W with the ramps. Good luck everybody Let's see what we got see some more nice shimmers. Let's see a big rookie one of the big QB's Saloon us so far box one got two more three boxes after this one than a half case And then we are on to personals for the night We are full-on personals guys if you order one now We'll go tomorrow Been full for a couple hours now. Good Q going blue shimmer silver Tyson Tyson Campbell and blue shimmer is gonna be Montez sweat for the commanders number to 25 He got traded right the 25 Montez Jalen Carter and Shawn Clifford 21 points 20 assists geez man That's absurd That's a that's efficiency right there No turnovers. There's a prismatic Joey And that'll be red shimmer or at a red wave of Jordan poyer to 149 Overshown well McDonald fireworks to a E And we got a blue ice that was gonna be Jonathan Mingo rookie for the Panthers to 99 There's a say flowers rookie come on a chain Yeah, I'd say so I Mean Markel's not playing Vaughn so I got you Jeff. I can look Man, I got y'all look it up my man There's a Dallas Goddard on the red wave auto to 35 nice one there Eagles. I got you Jeff We got you I got you and red wave is gonna be Jeremy Shockey a little throwback for the G-men the 35 red wave And Is on I got you my man. Let's see This one You're in this one. Mr. Jeff. Who do we got wait a second one second? Oh, no, this is hey Oh, you had heritage high number. Okay. Um, you were in heritage. That was earlier today earlier today Jeff You had um, you had heritage high number. I had a I could get you. Yeah, you wouldn't get a You had the D-backs in heritage. Yeah, so let me get the link to the video for you I can do that real quick. You had the D-backs this morning or this afternoon. There you go, Jeff There's a link to the break. I want to check it out All right. Good luck here guys. Keep on rolling There's a Geron Hall that one's gonna be a 35 on the rookie auto Vikings. Nice one there bikes their rookie QB Geron Hall in the red shimmer rookie auto. That one is 35 We've got Brandon cooks to orange to one or two 49 Cowboys Brandon cooks and this is gonna be a Alex singleton to 15. No, not yet. Jason. I haven't seen a color blast yet Alex singleton on the camo to 15.  They play fun basketball. It's not the most defense But there's a blue wave that one's gonna be BJ. Oh, Jalari the 25 BJ Nolan Smith It's the fifth quarterback they're going to there's a lockdown Shaq later Got a Ken Walker silver and purple ice kank our Mike Mike Evans to 25 fire the cannons Deuce Vaughan silver prison break is Joe burrow like that design and a 175 John Randall for the Vikings John Randall Felton Kincaid rookie prison break Bryce Nice Bryce and red shimmer 35 rookie is a Chris Rodriguez for the Commanders Chris Rodriguez score a touchdown this weekend silver cow pits and a 49 James Connor For the Cardinals there on the purple power and Bryce young base rookie Jaden re can joke you saying the same thing. It was like brawl over his back Tony Pollard and there's Buddha Baker on the orange for the Cardinals to 49 Skironsky and Quentin Johnston. Alrighty guys box two. Good luck. Here's me the last one of this case two more three boxes and then a half caser of a half caser of visions There's a true tranquil red wave and 149 Cam Smith DTR Jerry Walker's out of Houston, right? He was a rookie He's at Houston, right? Remember him dropping the drop the bit. I was here. Here's our first redemption It is will Anderson nice one there rookie Otto Silver. Let me for the Texans third pick in the draft nice will Texans there and the 25 we got Patrick Willis Bees for the Niners Blue shimmer tank big speed Zach Harrison. Yeah. Oh, no No, that's Texans rookie prismatic Bijan and that is gonna be a Travian Williams on the blue ice to 99 Yeah, I thought I remembered him. It's uh And then Marcus Sasser at Houston last year pretty solid They did not do good in the tournament though. I remember them blowing it There's a silver Romeo Dobbs and Calvin Austin on the purple to 249 Any other jacks we've got Anton Harrison and Tank Bigsby. Hmm. I don't remember Trying to think I don't know. I don't think they have Parker. I haven't seen Parker Washington yet See Parker Washington yet There's a Joe Burrow all purpose. There's Ramon J. Stevenson and Red Shimmer CJ Mosley I'll keep an eye out that know that I know Johnny or now Johnny. Geez CJ Mosley of 35 Red Shimmer Keep an eye out for it Diabe Haven't seen a Parker Washington yet. Now.  Oh boy. Oh boy.  I'm on now I'm on now There's a Christian Walker that was gonna be Red Shimmer auto second year for the Packers nice one there 235 on the Red Shimmer auto and gold shimmer is gonna be Chandler Jones on the gold shimmer Raiders He got a 10 the raiders Chandler Jones is not a Mack Jones friend. That is confirmed Cedric Tillman, but shoved him into the dirt last year He's I'm dirty on that one luminance car too. Nice CJ Stroud. There we go on the rookie throwback Silver for the Texans will mag that Texans first throwback CJ on the silver. There we go Texans Raiders rookie Trey Tucker and orange wave is gonna be a Kenny pick it to 60 little king. There's Anton Harrison Bijan Who's got the Texans in this one that is a? Andy nice one there Andy It really has it really has It has been tough for old Mack Jones. There's a Josh Downs nice one there purple ice Colts 225 Sam LaPorta base working Devon weather spoon Merchant ETN and nice for the fins. We got Devon a chain On the Red Shimmer to 35 very nice one for the Dolphins to a Dolphins. Here we go. He Miami Very nice one there Miami Chase Brown and Kendra Miller And it's John H John H with the fins John Just go to Johnny There's a prismatic silver CMAC and Patty Mahomes nice one there orange to 149 the chiefs Anaconda and Luca Ben Ness All righty guys one more Good luck everybody last one of our first case Yeah, I would think so Paul. I don't know though. I don't know though. It's probably close It's probably pretty dang close Right guys last one on this case for Break for throwback out of that's gonna be John Riggins for the Redskins there commanders 16 out of 35 on the throwback. How's it go? 35 there's a blue shimmer Christian Wilkins to 25 eat Dolphins Eric Gray. Oh, did he? Sean's got a big big hate list here for sure all of the bills all of them Silver Ricky will Anderson John Riggins I'm not sure yet Ray. The checklist isn't complete yet. Josh Allen to 249. There's a deal I'm not sure yet. We haven't seen a party yet. I'm not sure if he signs in this one Purple ice is Shaq Barrett for the bucks 225 225 225 sounds like 225 is 225 To 225 That's what I'm saying man. There's a CJ prison break and Red shimmer is gonna be Javon curse Titans don't mess with him free the 35 red shimmer not mess with Javon curse and a Jameer Gibbs base the Lions true gold Come on true gold Blue ice 225 is Josh Jacobs. Which way is it? Oh, it's a knee is it 225 It's a dolphin it is true gold Jalen Ramsey. Boom. That's my boy. That is black and gold. I think No, that's two to ten. That is a true gold Very nice. Go nose as John H another nice dolphin there Jalen Ramsey they were showing a stat that uh It was like the dolphins defense with Ramsey without Ramsey is quite different Turnovers everything man They're showing that yesterday.  He's uh, it's a lockdown TJ Watt And there's a blue shimmer h8 to Ralph to 199 Are you in here Miami? Are you in here? Mike Piazza Aren't you supposed to be sleeping? Oh Here's Donnie we going live we got to go live Donnie It's going on get this guy over to more Hamlin and gold shimmer. It is gonna be Ken Walker Nice one there for the seabirds Cam Walker action to 10 Jordan a on their second year Ken. Well Anderson and manual forps No, I'm only gonna throw you when I can hear you I can't listen to you. Oh, what we missed it dang it Yes, down to go back go back. I'll throw you when I can hear you talking prismatic lamjack and a Derek Forrest for the commanders to 175. I didn't realize it was almost 11 I guess that makes sense. Donnie's off Stream not realize it was almost 11 Moving say there's a Mike William Silver and Jalen waddle on the purple To 125 another fin man a lot of fins in this three boxer go doll Josh downs Michael Wilson Yeah, hey, I am having fun time. That's a good a good day really really fun schedule. That's some good hits to man There's a all purpose. That one's gonna be ridder Silver Jason Kelsey. There's Donnie's boy the Eagles and channel Jones on the red shimmer Another shimmer for a Jones to 35 Hey, exactly either or either or Sometimes it's both, you know We've hit two one-on-ones neither were like the biggest rookies one was a One was working for the Vikings one was a Jerry Snead for the Chiefs biggest hit so far is probably the CJ CJ silver throwback Those are pretty hard to hit and it's only Pollard height And I say no Connell on the blue ice nice one Raiders. It's a 99. We'll get a mag on that Starting QB for their raiders. I was told Donnie has a very good one of those Joshua W with our raiders Yeah, he's been really good man. He's been a really solid corner for him The other one I forget Jayce told me a second ago. I forget already again I'm gonna look it up. I'm gonna find it It was Ivan pace linebacker for the Vikings was the other 101 Yeah, guys like that stream if you are enjoying it. I always appreciate that. Thank you Mike Piazza.  I saw in there. He loved the camo. Nice one tank Bigsby Rookie out of Auburn. Nice one there and Stetson Bennett on the back Alrighty already guys that'll do it for the first First case that was the first four Some more in here All right guys, we'll get the new case open next number five going just a second blue ice as we had Josh Jacobs Travian Williams Mingo to 35 we had bread shimmers Rodriguez shocky a chain nice one their dolphins Chandler Jones CJ Mosley Javon curse to 25 Patrick Willis Christian Wilkins Montez sweat Oh, Jalari to 15 Alex Singleton for the Broncos to 10 We had gold shimmer Ken Walker Chandler Jones true gold Jalen Ramsey. Oh, no The end of 15 rookie to 25. Sorry. It's 25 is the aqua or navy camo Hank Bigsby Now for autos we had John Riggins to 35 Christian Watson Jaren Hall Dallas Goddard and will Anderson Lee prison rookie silver And we had a no-conal blue ice and 99 that's when there are raiders And we had our throwback CJ Stroud for the Texans nice one there Mr. CJ that's gonna be for Andy CJ Stroud All righty there guys that'll do it for case or break number four. We'll get number five going here just a moment


I am making sure of it! It started off as a dream, I was a kid. A fantasy, not a reality. And then I said, what are my limits? So I touched the rim, and I never looked back. I committed. I said I was going to make it happen. And I did. Now I dunk harder than I ever thought possible. And I pushed myself mentally and physically higher than I ever thought I could. Chase your dream, never give up, and don't listen to anyone. Slow down. Slow down.


Welcome back to Las Vegas everybody my name is Dave Vellante I'm here with John Ferrier and we are running SuperCloud 5 which is a cross-continent connection we got content pumping in from HPE Discover in Barcelona. John and I are here in the ground in Las Vegas and and we've got the the crew in Palo Alto Savannah and Lisa doing live live hits is unbelievable. I have had many a reinvent where I've spent the week in whether it was Barcelona or Frankfurt or London at HPE Discover. I'm here with two folks from HPE Brian Falves here he's vice president of North America HPE services sales and Joseph George, Cube alum, global VP of strategic alliances both at HPE so guys we're we're here like I said I've done Barcelona many times during this this year but you guys got a lot going on over there but why are you here? Yeah why are we here it's a it's a common question actually because we we look a little odd out in the show floor we're the only you know company like ourselves among our competition that are actually here exhibiting supporting the show the reason we're here is because our company strategy is the world you know the world will be hybrid and we're delivering the hybrid cloud experience and so it it makes sense to be at AWS to pick up in that hybrid. So if I were AWS yeah right the cloud they say the fullness of time everything's gonna go in the cloud we've heard that many many times if I'm AWS I'm changing my mentality of what the cloud is they've talked a lot this week about we're meeting customers where they are so the definition of cloud is changing and I would be all over guys like you yeah say because you got customers they're loyal they're not moving their data into the cloud so you got to move the cloud to the data and that's what you guys are doing right so what are the conversations like with customers in that regard? Yes it's interesting and you're right it's not a it used to be we talked about this a few weeks ago supercomputing the cloud conversation used to be I've got stuff in this data center we're gonna move it to another data center and partnering with our friends at AWS we're realizing that our customers are telling us that the journey to cloud is an exploration of applications and data and where they need to reside and how quickly we need to respond with outcomes so think about an emergency room all the stuff that's going on there x-rays and you know all sorts of analysis around conditions and symptoms you got to get a response quick so there's not an hour five minutes to even send all that data somewhere else it's got to operate on the edge there are some things you want to keep in your data center because it's IP it's sensitive it's confidential it's competitive advantage for a lot of our customers or in a co-location data center and there's some things absolutely you want to put in the public cloud so if we have a more robust intelligent conversation that says let's look at your applications let's look at your data let's figure out where they need to reside are they going to be mobile after a year do we do things change does it need to go from one public cloud provider to your data center doesn't it go from the edge to your data center doesn't you go from the data center to your public cloud those are all the organic life living life-giving conversations we're having now with customers when it comes to the cloud it's a much more thorough open robust conversation okay so I get the the need for you to partner with AWS I think about snowflake for instance so for years it was kind of one of this these types of relationships because every year AWS was out something that was a snowflake ripoff we separate compute from storage they're still doing it they announced clean rooms we had clean rooms okay yeah we've heard that years ago from snowflake but they partnered together and it makes sense and now they're happy they're not even front of me's they're both making money and I get it because snowflake selling software AWS is selling infrastructure service but you guys are infrastructure companies so explain how that relationship I'll disagree right great so explain how that relates how you make money in that relationship because we're a cloud company we're not an infrastructure company infrastructures absolutely at the core and historically what we've done but our value proposition is cloud there's this kind of false false narrative out there or false decision about you know are you should something be in should use public cloud should use private cloud or on-prem the answer is all of it right it's this idea this notion we have of hybrid by accident versus hybrid by design and what happened is years ago everybody was going to the cloud they all had cloud first strategies we're going to take this to the cloud and then they started doing that activity of moving workloads and data to the cloud or figured out this is hard it's expensive right there's the management of change that goes with it there are certain regulatory reasons of myriad reasons why things would need to stay on-prem and so they ended up building out you know an on-prem infrastructure component build out a cloud component then edge became prolific and so now your cloud is everywhere so it's not you know it's no longer oh I tried to go the cloud and some apps didn't make it it's for my future planning my future growth supporting my business leaders in my company I need to have a multi cloud strategy I need to be hybrid and so that's hybrid by design you need to design for and what each be does especially where you know a lot of customers have multiple public clouds what each be does is consider us the gap fillers right you work with HPE greenly cloud platform you can see all of those clouds we bridge all of those together you can bridge your edge your Colos your own data centers all those devices and even create kind of a true unified you know data fabric right all of those locations can appear as one pool of data this is the new conversation so I'm paying you for that that that that value right that that's that's so you're shifting the way in which you charge or I mean you're still selling underneath the covers you still have storage and compute and everybody sure as everybody you got to have it but snowflake is buying it and renting it if you have it right you do have it you have to have it but but but they don't make they don't make storage for instance you do so but you're also but you're saying but you're selling that value layer on top vendor it's a vendor what we're talking about is our vendors us as vendors when you when you talk to the customers they're like I've got these applications I've got this data that I need to have secured I need to have this kind of response time in outcomes when you have that as your foundation for your discussion it changes it says okay well some things need to live on the edge be born on the edge be operated on outcome based on the edge doesn't go anywhere else some things absolutely can be in a public cloud some things need to stay in my data center in my four walls for this reason security etc when you start having that conversation it opens up so many doors for our customers when they're trying to deal see see patients they're manufacturing products for customers they're trying to do cyber security on financial transactions it's a whole different conversation and but this is the conversation we think our customers actually want and I buy that totally but but if I'm if I'm a customer and I'm gonna leave my data on-prem or at the edge I'm gonna be wanting to pay you guys because you're better at it yeah okay can we quote you can we look at outposts I mean AWS is selling they would love to sell outposts that was an indication and I would say this the the the the time it took to get to outposts where it is today I think was in many ways a failure and it gave it gave you guys it was a tap on the shoulder like hey here we come and then it gave you time I think to create things like GreenLake that didn't you didn't create GreenLake overnight that was a lot of hard work and effort years and years and it was and it was a lot of like okay we're gonna do some services tricks over here and then but now everything you do is GreenLake eyes you got API's and your partnerships are all plugging into those API's so so they would like to sell outposts but frankly you got a better stack yeah I've been you know selling GreenLake you know for almost 10 years here at HPE and you know it used to be flex capacity so it was kind of a consumption model for infrastructure it has evolved and transformed so far beyond that and really what it is now is what customers are coming and literally knocking at our door and saying this is what I need from you is the experience they everybody's accustomed to and and values the tools and the orchestration capabilities of control plane that comes with using public cloud AWS Azure whatever it is right and when they turn and they say okay I'm gonna have like you were talking about I need all this data that's gonna have to stay on-prem or these workloads and apps that stay on-prem they're like okay accept that but geez I want that continuity of that experience the way I derive the way interact with and drive value on public cloud I want that in my on-prem my private cloud I want that from you HPE that's the critical differentiator is that software layer the GreenLake cloud platform that sits over the infrastructure so now you know for since the the day this company was started you know we we put an audio oscillator in a box and brought it over to Disney right and we've been putting stuff in boxes and bring it over to customers for 75 plus years now you do a GreenLake enter into a GreenLake relationship with HPE you get a login right that's your interaction console I can log in I've got a console I have all the orchestration automation and tools that I need I've got identity and access management built in and I'm off to the races and I'm driving value right from that underlying infrastructure at the same speed at which I can drive value from working with imagine the customer's perspective now right it was okay by these systems or in running my data center or work with the a public cloud vendor and put stuff up there I have concerns across the board but now imagine just a layer where you're taking applications data users etc. and putting it into a portal with HPE GreenLake and then determining where these things need to reside at that point in time with the flexibility to manage portability of things over time right it really is us as an industry getting back to listening to what customers are actually saying we talk about all things we are building as a vendor community now it's time for us to stop and listen to what our customers are saying where they say we have privacy concerns we have sensitivity concerns we have security concerns how do we manage across the whole portfolio and I think this is what HPE GreenLake offers and we call that abstraction we call it abstraction layer we call it super cloud that's right that's was was our sort of term to to find that abstraction layer so again I get it and it's a real clear value there we sort of help think through that concept and in a lot of customers were saying we want to pay for that okay so I get that but then why does other than the fact that AWS wants to take your customers why does AWS want to work with you in that regard because they you know look at outpost they understand that the world is hybrid I think I you know some some good friends in the industry who worked at at Amazon for years and the old mantra was get a customer signed up and pull all of their apps and data and workloads you know as quickly as possible I remember those guys they pounded on my head to take and then they burned out and it didn't work well it doesn't work and then they all found out they they kind of experienced their own end of hybrid by accident like oh man this this doesn't work and it became acknowledged that you know the the best customer you know might have 60% of the workloads right and data in AWS and so they that's why they responded with outpost and said we need to have an on-prem option meanwhile Antonio at HPE was preaching already for years the world will be hybrid and today the world is hybrid as we all know and so we've been building the software assets and acquiring the companies and tools we need to deliver cloud experience for your on-prem private cloud that rivals and is has this this continuity with their customers experience with public I mean it's even down to have heard them come in and say look I have these young buck developers when they come in and they're they're delivering their value to my company and they're working in public cloud they understand how to do that I don't want to have to like give have this like reverse compatibility when they turn back to the old infrastructure on-prem I want the same experience I want them to be able to interact with infrastructure that's where that's why AWS is a partner of ours because they're seeing the same things I think five years ago is a different story I think AWS without post as an example realizes there's a need that's out there so this notion is be you know remember AWS is that was a HP Discover in Las Vegas just in June the partnership is growing because they see that that need as well now you guys announced the LLMs as a service at it's government you said you're gonna ship it this year and getting close we got about a month to go and so but you were the only ones to announce that so it as part of GreenLake so that we were a thumbs up on that yeah my question is when you start to think about you know the the cubes research did a gen AI power law and we basically the premise was to get size of model on the vertical axis but but you've got this long tail of industry specificity and domain specificity on the horizontal axis and our premise was you're gonna see a lot more models smaller models along there and a lot of those gonna be on-prem and at the edge are you seeing demand for that are you actually seeing people deploy that what can you give us the update on that yeah I'll start so I'll say that the customers are interested in building a lot of their own LLMs it kind of comes back to IP and data if there's an LLM that a customer generates generally their view is not it's not something that's made for my competitors to use as well it's something for us plus our applications our specific scenarios are slightly different we want some that's very tuned for our company so there's a lot of demand for that we're seeing a lot with you know gen AI all over the place right there's a lot going on chat GPT etc these are all great examples of LLMs that are being developed so there is an appetite for it but again I think that the time that's going by is helping our customer set understand what LLM means to them can they can go and access something that's very public but it could be a wide swath of data some that's applicable some that's not applicable to their their sense or they create their own LLM and they're able to ping from it it's very very specific to what they're looking can you deliver the same level of innovation and LLM optionality that we're seeing in the cloud in your hybrid environments are you going to be able to keep pace and do that yeah absolutely and and I think you know just to you know maybe a point of an extra clarification on our our large language model in the cloud it's really about kind of democratizing access to to AI and making it accessible to customers of all sizes because if you want if you're you know a huge bank in New York and you want to train a large language model you have the resources to come out and buy the best of high-performance computing you know assets and resources stand up and one of your data centers hire a hundred people to go make it all happen right and just you know click your fingers if you're a smaller organization you need to get your model trained up you might start with a you know a public model you're going to add your data to it you need a place to get that training done at speed the speed is in the game in this business you don't have time or the money or the resources to spin this huge thing up what HPE GreenLake for large language model does is provide it's basically it's a it's a multi-tenant cloud it's like a public cloud environment where you can log in put it to use use the infrastructure use the tools use our expertise develop your model and then shut it off you don't have to make the big investment I think it's pretty noble in its approach again in democratizing access to AI and for our customers to compete everybody can have a large language model the differentiator what makes one company better than another is how you train love that your own data we love that announcement we're gonna see GA this year I believe which year TBD we're in FY 24 the reason I inferred calendar say that is because we've seen a high correlation between GA and uptake in this business I'm sorry guys you got to go last yeah I want one last comment on that one thing that was different than kind of everything you would see on clouds there's a super computer back there right this is something that we we have one on for years HPE, Cray, SGI all these capabilities number one on the on the top 500 list there's a super computer back there so when you're in AI running the cloud you're trying to get to the rightest answer fastest super computers help you do that and that's why in the power law you might see some camel humps along that x-axis because super computers of a lot of data all right guys thanks so much for coming on thank you right there from more from super cloud 5 from Las Vegas Dave Vellante John Furrier we'll be right back after this short break


Rpo right run a little Rpo. I Softed why am I doing this?  I think the only reason not the only reason not to the only reason not to use campus heroes was fifty-fifty That's it. If you're not fifty-fifty then you should have campus heroes.  It's just so so real. It's so nice to have a run that actually works Oh no Ramsey Hmm. Oh no Ramsey like how far do I put you out there to stop stretch dude?        Come on man. Oh My god, dude, like we got a block better than this.  Oh, this is bad man.     I tell you that I Sucked why am I doing this?   We lost God damn it.  All right. Well, I'm officially never running the bubble again.  I can't lie.   It's just Now he gets the ball thing pretty sure.  This is real game man.  I gotta I gotta do something else this ain't it.   Why would they not do that right boys? Like why would they not block the two linebackers in the middle of the field? Travis Kelsey with a tutty. Let's go Travis didn't think you'd see that one today. How about this big fumble right here? I'm not that I'm not showing teeth. I'm a strip. All right.    No, I don't want to rob Calvin 100% I still like this defense. Okay, I'm just worried about curl Really out there. Let's go man. We'll get seven to end the game man. Go get seven to end the game I'm Diffie now It's a good game. It's a good fight from the boys at home It's a good fight from the boys at home. It's a good fight from the boys at home here Oh, this is sad man. All right, dude. Keep running We have one completion. Oh my god, that's tough. All right, let's recover on one side kick here I don't like McKinnon being out here Calvin


A couple days ago I had a little like, just a little tender spot, nothing that doesn't come throughout the season. You know, I was fortunate to get three days off in a row without pitching a game and then I came down here to play catch today.  It's just, even if it's just a little sore spot, so I came in or I told Larry out there and let Booney know and just ask him if I could try to get a day. I know it, of all days, it turned out to be this game and, you know, I wish I could have been there to help him out and hopefully tomorrow, you know, I'll be ready to go. If you were, it's just one day. Yeah, I mean, I've only had three or four days. I mean, today would be my fourth day, so hopefully, you know, if they need me, I should be there tomorrow. If, if you get another day, I get another day, you know, take it, take it, see what happens tomorrow. That was a sore spot different from, from something that tells you that you're injured.  I mean, that's, that's the way I look at it. You know, throughout the year, you deal with aches and bruises and stuff like that. This one just was sticking with me for a little longer. I mean, if I had to pitch today, I could have gone out there and done it, but I don't feel like I would have been at 100% and I wouldn't, I don't want to give this team anything but that. What do you think of the job that guys like AJ Cole and Chad Gray did of working themselves in and out of trouble, kind of, kind of like you're a groudini act, giving me anxiety out there in the bullpen. I'm watching it. I'm like, man, now I know what it feels like when people are watching me pitch in 11 and 12 and 13 and 10 and nine, all the years before, pretty much.


Hi, maenai Cameron. I'm the track chair for coding and development, Drupalcom Pride, and it's my absolute honour to introduce one of the featured speakers in my track, Alex Pott. Those of you who attended Driz's keynote this morning would have had a bit of an intro to Alex when Driz thanked him, but for those who weren't, Alex is one of only five Drupal 8 core committers and the most recently appointed I think in April. So a core committer is someone in a very privative position, being one of the few people who can accept changes to the core of Drupal itself. So for Drupal 8 we've only got Angie Byron, Nathaniel Catchpole, Jennifer Hodgdon and the docs team, Driz, of course, and Alex who can commit code. So since April he's already done more than 1,200 commits, which is a blistering pace, I think Driz had 50 a week this morning. And to put that in perspective I think until then there was only about 2,000 commits on the Drupal 8 trunk. So came to core development through his work on the configuration management initiative, which some of you may know about, which he became interested in when he was working as lead developer on the Royal Mail project. Talked to Greg Dunlop, became part of that initiative and then was invited by Driz to be a core committed. He's now working full-time in London on Drupal 8 and he's an absolutely lovely guy. It's really my honour to introduce him. So the theme of the conference is one to many. Alex is going to talk about how Drupal 8 has incorporated ideas, technologies and indeed libraries from the wider PHP community and what that means for Drupal now and in the future. So Alex, take it away. Good afternoon everyone. So as the Prime Minister said I'm here to talk about the Drupal 8 story, how we've gone from not invented here to proudly found elsewhere and we're looking for ideas from outside of the Drupal community, outside of PHP on how to make Drupal better. So that's who I am. He's introduced me so that slide is rather redundant. So we'll move on to who are you. I'm hoping that most of you are Drupal developers who are new to Drupal 8 and that I'm going to talk to you about why we're making the changes that we've made to Drupal 8, how to talk in Drupal 8 so that when you come to issues and you look at the way that the code's written, you understand what it's trying to do and I'm going to talk about some of the advantages about the changes that we've made from a developer perspective. So in order to talk about why we've made the changes to Drupal 8 we have to go back in time. So I don't know how many of you know how Drupal started but Drupal was started in a dorm at a university by user one sitting there going, hey I want to make a slash dot for my dorm. And so that's what he set out to do. He made the drop.org and him and his friends posted messages and started to share the software. This has impacts on the way that Drupal is written and the way that the internet was in 1999 also has impacts. Google was in beta, everyone was using Internet Explorer 5. There were some advanced things going on on the internet like SETI at home but it was all bespoke software and the internet was full of tables and it just was a different world. And people were using these to access the internet and these to make phone calls. We're not in that world anymore. So looking at what we have today we have a Drupal that's sitting at the heart of the internet getting requests from iPhones, from kiosk applications, from desktops of course, from all sorts of other frameworks and systems. Yet at the moment Drupal 7 assumes the moment it's making a response to a request that it's this desktop. That's what it does. And in Drupal 7 in order to get around this services module does all sorts of evil things like just exiting straight from Cota and anything you've got that's going to fire at the end of a response on termination, that won't fire. That's Drupal 7 for HTML. So at the beginning of the cycle for Drupal 8 Larry Garfield said that Drupal basically needs to evolve and quickly from the first-class web CMS into a first-class REST server that includes the first-class web CMS. And this has a fundamental impact on the way in which we have to architect Drupal to work. And so I'm going to talk about what that is. At the same time the tools on which we've built Drupal have been changing. So PHP is no longer PHP 4 that it was back in 1999. It's embraced concepts and techniques such as OO namespaces and anonymous functions that we need to embrace because that's PHP. That's the fundamental language that we're using. So Drupal 8 is object-orientated because PHP is object-orientated. So if you don't get classes, objects and interfaces then now's the time to start to learn. So I'm going to show you why that's important in quite simple numbers. Drupal 7 has 380 classes. Basically it's all the DB layer. Drupal 8 at the moment has 2,816 classes and it's only going to grow. So if you want to develop on Drupal 8 getting comfortable with OO code is going to be mandatory. So one of the key things that was introduced in PHP 5.3 which Drupal 8 is the lowest version that Drupal 8 is going to work on is namespaces. And what namespaces allow us to do is to use classes with the same name, like database, but take them from different places. So with PHP 5.3 and its new object orientation and namespaces, people were sitting around saying well actually this now allows us to share code between our projects. So in 2009, some people came together under the framework interoperability group so-called PHP FIG and proposed PSR0 which is a way in which projects can share their classes and share objects and share functionality so that we don't all have to do the same thing. Which basically says that if we're going to have an object we're going to namespace it like this. We're going to have a vendor name, Drupal a namespace, database and a class name, connection for example. And so what this allows us to do in code is to use our objects like this. So at the top of our code we write use, Drupal, user, entity, role and then in my code I can create a new role just by going new role. Then automatically PHP will be able to include the role file in your directory structure which at the moment is buried quite deep because it's PSR0 and it will load this file automatically for you when it needs the class. So we have autoloading and we have namespaces but the next bit that really meant that PHP projects could start to share code was the advent of Composer. And what this is is it's a dependency management tool for projects. So it allows us to say that my Drupal project needs code from symphony, it needs code from Zend or any framework or any part of PHP that we want we can pull in in a way that allows the autoloader to load those classes for us. So at the moment Drupal 8 is relying on 11 or so symphony components but it's not just symphony as I was saying we're using doctrine for parsing annotations we're using easy RDF for managing our RDF stuff we're using guzzle for making HTTP requests we're using the Zend framework to manage RSS aggregation and we're using twig for templating so we're pulling in all this extra code to handle problems that we don't need to solve problems that other people have solved for us. So now with vendor we actually have over 5,000 objects in Drupal 8 that you can instantiate and use to solve your problems. So we have all these new objects and we have the new PHP ecosystem built around object orientation, namespaces and autoloading but that means that we now need to use some new words to talk about the way Drupal 8 works and I think language is a really important thing if we use different words to talk about the same things then we end up with confusion and I think that we need to use a model based language a language where the words represent things that we can all think about and share and understanding in so that we can come together and create a great Drupal 8 and great websites and products built off it so I'm going to go through some of the words that you'll hear a lot in Drupal 8 and then show you the code that creates these things. So services what services are are basically global objects that provide functionality to your code so a classic service would be something like a cash back end the mailer or the module handler which will allow you to not care about how it does it but just get the database connection install a module you can go create I have the module handler just install and services have to live somewhere in Drupal 8 and so services live on the container and so the container is the collection of all of the global objects that you can access and the advantage of using a container and specifically the symphony container is that it means that we can inject the dependencies into the services what that allows us to do is to remove the assumptions that your code is making about what it needs so it allows us to remove all of the hard coded dependencies and then it makes it possible to change them so if we want to swap out the HTTP client currently in core we can and then your code just because having the HTTP client injected can just use the new one because you know that it's going to implement the same interface and this allows us to write clutter free and testable code because the less your code actually knows about the rest of the application the more reusable it is by others and by yourself so in Drupal 8 to set up a service all we do is we declare stuff in our well we can declare stuff in core.services.yaml which is basically this is saying okay I've got my config factory service it's going to instantiate this class and it's going to have the storage and the context injected in which are other services here's the database service it creates a connection and in order to create that connection it uses a factory and the arguments are the default settings these are the default settings from your settings.php you don't have to just use yaml to register services you can programmatically register them in PHP and what this allows us to do is to swap things out at different times so when we're installing Drupal the module handler isn't the cached module handler but when it's in runtime we're using the cached module handler so it's really flexible and we can now change things at different states and the impact of this is amazing in terms of what we can do with now the upgrade path the updater has a completely alternate module handler that prevents you from firing hooks so we've told you in Drupal 5 and 6 and 7 don't fire hooks from your upgrade path it's actually now impossible to fire hooks from your upgrade path and this is a big win because it means that we've broken it before it's more robust you're going to hear a lot about requests and responses these are symphony objects that we've used to model the way in which Drupal works so a request is made and a response is returned to the browser when a request is made we discover a route if you're American or root if you're English and the root is there what controller to use in order to create the response and again the routes are declared in YAML so here is the user-autocomplete route so slash user-autocomplete here is the controller to use and here is what permission it requires it's declarative this is the equivalent of the routing part of hook menu in Drupal 7 and here is the controller we see dependency injection in action we inject the user-autocomplete service into the controller and then the controller just calls get matches so that means in order to test the user-autocomplete service which is there is the declaration in the services YAML file we actually don't need a request or we can mock the request so our our auto-completion for users is now divorced from our request handling in Drupal 7 in order to test this code you would have needed to fire up a web browser now we don't, now this is testable in other ways you're going to hear a lot about plugins and all plugins are is a group of similar objects that can be used in a part of Drupal so a good example is blocks so not every block does the same thing but when you place a block on a page it provides a view a view as in as in some HTML to put on the page and the thing that's special about plugins is that they are discovered so we have discovery mechanisms and what discovery mechanisms in Drupal 7 basically you replace is all of the hook something info so hook entity info, hook field format info, hook field widget info hook image toolkits they're all gone in favour of a common discovery method or we have two at the moment and one of them is annotations which we've borrowed from doctrines so I'm going to show you some of an annotation I'm going to show you a block and try and show you why this is really really nice so in Drupal 7 we have our system block view and at the moment as a developer I'm wanting to work on the power by block I have to read all this code it's going into a switch and I'm going oh yeah that's great, there's my theme Drupal 8 we don't need that the hook view we don't need the hook block info all we have is the annotation in the same place as we're telling it how to render the block so we have an app plugin here's the ID that appears in the admin interface and here's the function that just returns the theme block and so in order to create a block you can just copy this file change the ID the admin label do what you want on the output and then the system will automatically discover it for you another big change in Drupal 8 is entities and basically everything is an entity that has a life cycle that can be created and then deleted at some point or kept around and the important thing about an entity is that it's uniquely identifiable so we have content entities which are pretty similar to Drupal 7 there's obviously nodes, users, comments but we've also now got contact messages and menu items but we also have configuration entities like views, vocabularies contact categories fields, menus and roles and what's nice about configuration entities is that they use the CMI system in order to be managed so we have the user authenticated role looking like this so it's really easy to read this file and see what permissions it has and we can copy that file up to production into a staging directory import it and make the changes and it's also nice about using the entity system to manage things like roles is that we can then put helpful methods on the role entity so we can implement has permission so you create your role or you load up the role the authenticated role and you ask it does it have a permission and this actually helps us fix bugs at the moment this code reads the code for should I search comments depending on whether the authenticated or anonymous user has access to comments now looks like this and it's much easier to read this role does it have this permission has the permission access comments and if the role IDs are this I can't index comments because the authenticated user doesn't have access to comments but the anonymous does and Drupal 7 the code was like this we carried straight out the database and we made we loaded up a huge array the array key is going to be the permission name and then we're going to see if the role ID has it and when we moved to Drupal 8 we changed what these constants were and we ended up introducing a bug that if you created a role like administrator that was less than authenticated user it would actually fall in here you'd never be able to index your comments so by having interfaces which declare helpful methods on your entities we're able to actually make the code more readable and easier to debug so everything is different in Drupal 8 but that also is getting us some other wins a lot of people say that Drupal 8 is more complicated but I'm going to make an argument that it's actually less complexity I've shown you that the blocks are less complex I've shown that it's possible with config entities to manage configuration in a less complex way but I also think it's measurably less complex so if we have a look at how we can measure complexity there's a measure in computing called cyclomatic complexity which basically just measures the numbers of decision points in code so this function here has four decision points the decision to call the function each if or else if so if we have a look at what that would mean for a function 1 to 4 cyclomatic complexity is low complexity that didn't look very complex 5 to 7 moderate complexity 8 to 10 high complexity more than 11 it's just very very complex if we have a look at but we can move this measure to actually every line of code in a project and so generally there's been some studies and it shows that here are the the kind of measures that we would look for so you know Drupal's not going to be a low complex application never has been but it would be nice if we were in the moderate complexity range so if we have a look at Drupal 6 actually Drupal 6 was very complex lots of functions did an awful lot lots and lots of features and abilities to do different things and so when you were trying to work out what does that function do you have to reload a code and you weren't always sure what it's going to do Drupal 7 we got better we got a lot better and now in Drupal 8 we're actually in the sweet spot of measurable complexity where you're looking at most functions that they're just doing a single thing they're not doing lots and lots of different things but actually you know what you would say here is the number of lines of code has gone up by 300,000 so what does this really mean we've actually got a lot more decision points and what's really really interesting and you couldn't make this up is that Drupal 6 is actually 77% less complex in this measure of numbers of decisions than Drupal 7 and Drupal 8 is 77% more complex than Drupal 7 so how am I losing my argument well maybe not because actually if I take Drupal 7 and I remove the modules that have been removed like blog, dashboard, open id, poll, profile, php but I add in views, email, link telephone features entity reference C tools and Wiggy's Wig which is just a selection of some of the functionality that you would have to bring into core to have the same feature set as Drupal 8 we actually get to a point where the number of decision points is more in Drupal 7 so I think that in order to achieve Drupal 8's functionality in Drupal 7 you're going to have a more complex site and so just to really focus in on one of the changes that we made in Drupal 8 and how we've benefited from going and using other libraries we can have a look at this function which is really hard to change it has a cyclomatic complexity of 41 which is over that 10 measure but also there was an issue that was studded in 2004 took 12 years and over 400 comments to actually get a commit into Drupal 8 it was fixed for Drupal 8 but we now we don't even have the function in Drupal 8 we just use guzzle and what's amazing is that in order to actually test that code ourselves we would actually have to write 25 billion tests to actually fully test Drupal H2 request it's not possible and what's even more funny is that that issue is now broken we can't actually use proxies in core but in order to use proxies in core we actually only require this code so we can actually take the guzzle HP client modify it, just add the proxy settings whatever we want straight on there and because we're using dependency injection everywhere to inject the HP client into every service that needs it we just benefit so issues that took 12 years of arguing can be solved in 5 lines of code in Drupal 8 I think that's pretty cool another thing that we've done is we brought in PHP unit and so we finally have a way of testing our code in ways that doesn't rely on the simple test browser and what's really good about that is that we're testing all of our code and all of our functionality on a browser that no one ever uses that doesn't really make sense and we're trying to make it test things that we don't need to have all of that we're not isolating what we're actually testing and it's slow so PHP unit to actually run all the tests at the moment takes 4 seconds to make nearly 2,000 assertions simple test takes an hour and a half on test spots to make 50,000 assertions so it's a big improvement if we can move much more of our testing to PHP unit we're going to benefit we're going to benefit in other ways because it's not just about speed we get more information back on what we're testing so it's possible in PHP unit to produce coverage reports so here's the datetime plus class and I know that we've got all of these methods in there and I know that this method 80% of the lines are being hit by my test so I can actually look and say hey, we're missing test coverage for this format class because there's only 33% of the lines actually tested it's brilliant and it's really lovely and I can say that in the tests for crate from array we've got nothing that's testing that we throw this exception correctly because that line is red and all the other lines are green so they're being hit by my tests so I've spent a lot of time talking about what we've brought in from PHP but it's not just about PHP what Drupal 8 has changed you heard this morning what Dries was talking about we have 6 new front-end libraries Modernizer which wasn't mentioned and we've got massive efforts to clean up front-end performance one of my favourite facts about Drupal 8 which is not PHP related is that in order to do a request in Drupal 7 just install and request a node you'll actually make 24 requests for different assets in Drupal 8 that's now only 13 it's a lot of work that people have done on that so if I wanted to know more about some of the things I've been talking about I can't recommend PHP the right way .com enough to have a look at how PHP has changed in the past 3 or 4 years to embrace object orientation and new design patterns if you want to see about how to create a framework like the way that Drupal 8 has used symphony then FABPOP framework will bring up an amazing series of tutorials on using symphony components and talking about the way that we use language Eric Evans' domain-driven design is a great book so also now I'm on stage I would like to thank everyone who's contributed to my get-tip because I don't know how many of you actually know about how I'm funded and only work on Drupal 8 but it's my own money and contributions from the community so thank you everyone for giving me money because it's just cool Last but not least come to the sprints on Friday we need more help there's lots to do in Drupal 8 there's going to be big decisions made and we're going to produce an amazing project and I would really like you all to be a part of it so yeah thank you everyone any questions so Eddie it's just asked me what do you think the biggest remaining challenges are to tackle with Drupal 8 so from my perspective it's finishing CMI I really want to see that finished I think that there are challenges around the upgrade path making sure that it works in all situations we've done a lot to improve the testing on upgrade paths but there's always more work to be done because most people don't have a Drupal 7 site there's just Drupal 7 core they've got contrary modules they've got everything there so we have to do work so I think those are the two big challenges for me personally but for Drupal as a whole this morning he laid out that we have challenges around complexity and DX and we really really want to improve that as well Angie so Angie asked me what things get me the most excited I think for me the most exciting thing is the consistency handling different things that are similar within the Drupal universe so how we handle role configuration and how we handle views and the methods are the same so if I want to know what's the UUID of a view I call the UUID method if I want to know what the UUID of the role is because they're both config entities they have the same methods and this is nice because it answers a little bit more obtuse than it needs to be because if you look at nodes and users in order to get their ID in Drupal 7 land you go node arrow UUID for the user node arrow NID for the node and user arrow UUID for the user but in Drupal 8 you just call the ID method and it will return your ID you have to know less and if you have an IDE that autocompletes that ID method is there so once you know it once you've learnt it for nodes you know it for users you know it for views you know it for everything so I think there's a consistency there that we haven't had before so the question is Drupal versions prior to Drupal 8 were largely procedural and Drupal versions and Drupal 8 and the future might be largely OO which was as a site builder I was building sites for a university I wanted a tool that I could click together stuff I didn't have a comparison of different things I was like oh Drupal looks good at that point I had not looked at the code I didn't know whether it was procedural or I didn't care what I cared is that I had this amazing ability to create content types and click it together in a way that just worked and it was solving my problems then I got to this point where I was like oh it's not solving my problems anymore I need to change something and then I was like oh this is procedural code okay that's fine but I don't think that changes if you're a site builder and you get into coding and it's now oh you're not going to sit there and go oh I wish it was procedural you're going to say okay this is the paradigm so I'm not sure that it changes that much so the question is do I think that other projects will join to use Drupal components and yeah if we get it right if we provide valuable things back to the PH community sure in fact in the last month or so the Drupal 8 initiative lead for blocks has been doing a lot of work on plugins and symphony and he's been talking a lot in the symphony channels and they're very interested in our plugin system because they don't have an equivalent system so yeah I think that if we don't give code back to the wider PHV community we've kind of failed it's not a one-way street well thank you everyone thanks for coming