Loads of people are discovering or rediscovering the joys of gardening and are heading in droves to garden centres across the state for plants, products and plenty of inspiration. Top of the purchase list for many gardeners are fruit trees which is wonderful as more and more people are looking to enjoy the delights of homegrown produce. However there is one serious pest out there with the potential to ruin your dream of being able to pick and eat fresh from the tree and that is fruit fly. Whether you have an existing fruit tree or planting a new one there are some very important messages all home gardeners need to know about fruit fly. Sam Luke from Valhanna Nurseries, South Australia's largest fruit tree producer is the ideal person to explain. Being fruit fly free is critical to South Australia's horticultural industries. That risk is $1.3 billion worth of fresh produce, hundreds of businesses and 37,000 jobs. Being fruit fly free reduces the cost of the grower of producing their fresh produce and it also helps us to get a premium price on the export market for the produce that we send overseas. To help us remember what to do the nursery industry have got together with Perza and they've created a label which you'll find on your fruit trees when you buy them from your local garden centre. Take your fruit as soon as it's ripe, collect the fruit off the ground and put it in a green bin and check your fruit for any blemishes and maggots. Garden centres will also have helpful information flyers to help you remember what to do to prevent fruit fly in your garden. It's really important to support our local South Australian growers. Buy our local fresh produce and learn how to prevent fruit fly in your backyard. For more information or if you have any questions about fruit fly call the fruit fly hotline on 1300 66010 or check out the comprehensive fruit fly website. Remember everyone including gardeners no matter what size your yard has a role in protecting South Australia from fruit fly. Hello. Hello. Hello. Hello. Hello. Hello. Hello.


All right, let's kick it off. First up.  These are non addressable LED strips. You see that MOSFETI in the background? That's an RGB LED driver. This is an LED strip that has analog LEDs in it, so not a neopixel. You've got four wires that's plus 12 volts, green, ground, red, ground, blue ground. If you go back, you'll see the whole strip changes color all at once. It's going to be less expensive than Neopixels. And also a lot of people have ready to go 12-volt LED drivers built into architectural or home or automotive stuff. And so for those uses, this LED strip is handy because you don't need a separate controller. However, one thing to note is that this is a side light LED strip. So the light comes out the edge, not at the front. We have a separate one that has the light that comes at the front. But for some people, like they want to have, especially if you want to curve it around an unusual rounded shape, this is going to do a much better job because you can, of course, attach this to the edge of some wood or laminate or metal. And the light will come out in a nice thin strip. So analog RGB LED strip, that's right angle output. Next up, dental tools. Now these are, well, I saw this, somebody tweeted about this. I was like, oh, these are really good for the idea. So whatever you're. We've only needed these multiple times in our lives. It's kind of a classic tool in Allen Ranch and a normal driver. So you get pH 1, pH 2, pH 3. And I think 6 by 0.5 millimeter flathead. The kid actually came with more. And I was like, only these two were really useful. So we're talking these. They're hard steel and they're magnetic tip. And I'll show them the scale so you can see on the overhead. We'll add it. We added a demo, but it didn't come in afterwards. Yeah. So what's nice about these is that if you are working on something where you have to get into an unusual gap and you don't want to take apart the whole thing, like you've done that, you're like, oh no, I forgot one thing. I don't want to take apart the whole robot or whatever. You can get in there and you can wrench it on. One thing to note, obviously, these are not hex wrenches. And hex slash Allen wrenches are designed for torque from the side, whereas flathead might not be too bad. But especially Phillips is not going to be amazingly good at getting torque coming from the side. You have to really press this in so you don't strip the head of the screw. So it's not for high torque situations, but it could be good if you just want to get something kind of finger tight. This would work fairly well. So I like these. They do look like dental tools, but I like you can get it. And I think I wrote in the text description, I think it's a little bit more than a half an inch of clearance you can get in there and open up a screw. It's kind of nice. It's got magnetic tips and knurled grip. OK, next up, we got big nudes by request of people. Can you carry the 600 and one meter version of these nudes? So we do. We have the 1.2 meter and the I think this is the that's the 1.2 meter, but it looks the same. It's got the edge. I'll show this on the overhead. That's the 0.6. And then you have to go to this one. So we got this one, 0.6, this one, 1.2 meter, which is really long. Yeah. And keep going. Show how long it's between the two. It's like 48 inches long. And yeah, let me go to. Here's another way to look at it, too. Quarter, quarter, quarter, quarter. OK, so this is, hold on, I keep the wrong plug. OK, so let's go to the overhead. That's right. Yeah, I mean, it's for a limited use. It's illumination. Yeah, so one thing that's nice about these is that even though they're single sided, the light does kind of come out the other side kind of nicely. And you do see the little dots in person, but they're pretty smooth. And I think, you know, for more than a couple of inches away, it'll look like just one long strand of light. The trade-offs of having such long strips, 0.6 and 1.2 meters is that you need a higher voltage for these. I tried to get them to make them for me in a lower voltage, but they were kind of like, no, you can't do that. So the 0.6 needs 12 volts, and the 1.2 meter needs 24 volts. It's quite a bit. I'll say that even though I have this just plugged in here right into like this is my 12-volt power supply, it gets very hot. I would put a resistor in to try to current limit these to a half an amp each, half an amp through 12 volts or half an amp, just six watts, or half an amp through about 24 volts, which ends up being like 20. It's a little bit 11.5 volts for the 12 and like 22 volts for the 24. So just basically put a little resistance in there so you're not driving it directly, especially since your 12-volt supply might give you a little bit more than 12 volts. Otherwise, they do get a little bit warm. I mean, I don't think they're going to get self-damaged, but they are toasty. So they're expecting either current control. I'm going to be adding a little bit of resistance in there just to slow it down. And of course, you can PWM dim them. That'll also work very well. You'll just need a 12 or 24-volt power supply. We do have in the shop adjustable power supplies that go up to 24. And we have a, this is actually a USB power supply. So it's USB on the other side. You can get either USB-C or USB type A. Pick that up. And I'm going to put us on here. Can you pick it up and hold it up to see what happens here? So bright. Yeah, it's neat. Yeah, I mean, it's meant for light. I mean, it should be, it's illuminative. Not like super bright. You're not going to light up. It's not like a spotlight. It's neat because it's making some of the green screen come through. Give it a little halo. That'd be cool. It's a neat effect. That looks good. Yeah. Ring light. Yeah. Wonder Woman's jump rope. Jump, yeah. Yeah, the long one, especially. The jump rope of truth. Okay. Okay. So, big nudes. Yeah. Big nudes for big nudes. Okay, stars to show. We have two products for that this week. Okay. Please. First one is this swirly grid. This is something that Scott and Jebbler kind of were chatting about. Jebbler designed the open scad version that was 3D printed. And then Scott came in and was like, ooh, this could be made out of PCB material. And, or maybe I said, I don't know. You made it in Kikad or Kikad. And I posted in the product link, you can see the script. If you want to generate your own and manufacture them, go to town. This is an aluminum-backed PCB and it's got this grid on 0.2 inch spacing and each hole is point, sorry. It's 0.2 inch spacing between things and the holes themselves are a little bit more than 0.1 inch in diameter. So the dashes are like 0.11 inch and the holes are 0.1 inch diameter. And by having this, instead of just having pegboard dots, it means that you can handle components that aren't exactly on 0.2 inch gridding because our feathers, for example, are 0.9 by two inches. And a lot of our STEMQT boards are 0.7 by one inch. So you see it's like they're on a 0.1 inch grid but they're not on a 0.2 inch grid. Or maybe you have other dev boards that you want to plug in. So what's nice is that because you can slide the components around, there's always going to be some place that you can connect the components. The only thing is, that demo is still at the office. And also there's numbers because you can, you know, to specify where to have a specific product. You want to just hold that underneath the overhead real fast? Yeah, I can hold it. I can also go in grab.  And so you would go for these two slots and so you could mount it that way. Could do a cool cyber deck thing with all this too. Yeah, this came in kind of interesting. So there's always like some combination of like forward up down slots. You could weave nudes through the holes too. That's true. You can do all sorts of stuff. But it was designed for, you know, feathers and stem acutee specifically because Scott was like, oh, I'm trying to use all these projects. Stacky on the, we call them stackies where if you order these, maybe pick up rubber feet. Yeah. And I recommend, I will say, we have these two M 2.5 nylon screw sets. So M 2.5 is 2.5 millimeters, which means it'll fit very nicely in the 0.1 inch holes and slots and they're nylon. So they're non-conductive. So these standoffs are great pairing because you can use that to keep your boards off of the aluminum backing. Cause remember this aluminum backing is conductive, but it's also nice because you can cut it, you can bend it, you can, you know, file it very easily, would not do that with FR4. Or you can also use it as a ground plane, if you so wish. Okay. So interesting design. Good work, Jeff. Do we'll start the show this week, so as you lead our team, our customers, our community is... The iSpy QDPY. She's a great little rhyme. So this is a board for QDPY and Shao. DevBoards is a little BFF. It's a best friend that fits on the back and we'll let you plug in almost all of our displays and E-Inks now have a TFT displays, E-Ink displays and others have an iSpy connector and that lets you connect to them without doing a lot of wiring. So if you want to add an OLED display, you know, we have the STEMI QT port on the front, but if you want to add a color TFT or an E-Ink, you would want to use one of these because you'll need the SPI port and you'll need DC and chip select and maybe you want to also do the memory select, SD card, backlight, you know, all the pins. So I've documented in the product guide what each pin goes to, but basically you can get iSquad C and SPI through and then TFT, chip select and data command control on the RX and TX lines and then memory, chip select for E-Ink displays if you need it, backlight control if you need it, interrupt for touch screen if you need it, touch screen, chip select and SD chip select. So I can show on the overhead. I've got a little demo. This is an RP2040 QT Pi and then I've got the BFF on the back soldered in and then you see I just plug in this cable very easily.  So the touch screen goes over iSquad C, the IRQ pin is also going through here. So when I touch, it gets an interrupt and then knows to update the drawing and then it updates the TFT. So it uses almost all the capability of the iSpy cable, but you know, no soldering required, just plug in this cable and you're ready to go. So almost all of our screens now have this cable connect, can make it very easy. It's the finest way to drive a screen. Yeah, it's just like, I just wanted to make, people were just struggling with like wiring and the breadboards. This way you can mount this in one place and have your driver chip elsewhere so that the USB can be connected to. You can use a small screen or a large screen, go to town, we'll be doing of course more iSpy displays as well, but had to go through and revise the ball, which is something I've been doing for the last year. That's new products. Ooh. fikjip Bonjour hello han hi hi hi hi hi hi hi


Okay, well, great. Well, thank you for everyone for coming to five actors. So we're gonna get started and I will in the background try to figure out the captioning thing. So today we're gonna be talking about the Interactivity API and we have Mihal Chplinski here to talk us through it and give us a little example of some demos and stuff or a small demo and then we'll kind of open it up for general questions. So if you want to ask a question, you, there should be a little hand raise button down on the bottom of Zoom or you can paste it into chat and I will do my best to make sure everyone's questions get answered and yeah, just a couple of links to share. So here's a link to the, I'm just gonna drop it in chat here. So this is the link to the make posts that is that announces the API and there's also a link to the project repo if you're interested in getting involved so I'm trying to click on it and it's not working. There we go. So couple of links there. And yeah, so like I said, we have Mihal Chplinski here. So I'll get him to explain to us his background and his involvement with the API and then we'll probably just hand it over to him for demos. So over to you. Yeah, thank you so much, Ryan. So yeah, hi, Mihal, I work at Automatic and I'm part of the team that has been involved in the development of the Interactivity API. Prior to that, so prior to working in Automatic worked at a small startup called Frontity which was working on a React framework for Headless WordPress. So that's kind of my background. And yeah, the company got acquired by Automatic and we've stopped working on the framework and kind of diverted our efforts into trying to bring the same kind of developer experience that you would have with Frontity back into WordPress. So the Interactivity API is kind of the first step towards that vision. Yeah, and by the way, I'm from Poland and I live in Peru. So yeah, just a fact about me. All right, should I just go ahead with the demo? Yeah, sorry, yeah, just dive in and I'll track the questions as we go and then after you're sort of the formal demo sections then we can kind of start asking you the hard questions. Yeah, all right. Okay, let me share my screen and all right. So yeah, as part of the proposal for the Interactivity API, we've created a demo site for different kinds of movies and with the Interactivity API, you can get this kind of user experience that you are typically accustomed to from single page applications. Like when you like a particular movie, the number of likes are synchronized with this other movie likes block over here in the header and you can navigate to an individual movie page and you can see the likes are still visible here. So you can take notice that this movie has been liked. The likes are preserved in the header. You can even play the trailer and you can navigate to let's say individual actor page. You can go back to the movies page and yeah, it all just keeps working and like the movie trailer keeps playing and the navigations are instant. And yeah, you can even search for movies. So let's say you search for like avatar. Oh, it's not there actually. Okay, let's search for, I don't know, Marvel. No Marvel movies, okay. Superman, no, Spider-Man, all right. So as you see, the search is instant and it's all built with just WordPress and interactivity API. So let me show you how it interacts with, integrates, sorry, with the block editor. For instance, this is the search template of the, you know, WordPress site in this theme. And if I edit, for example, let's say post template, yeah, I can add here maybe like this movie and maybe let's put it in a, yeah, let's group it actually and let's add another block here and let's add the movie icon. Well, this should maybe be a row instead of a group. Can we, oh, the zoom is, zoom controls are, ah, calling it up for me. So no, convert to, I can convert to a row. Yeah, it actually, it doesn't matter. So it will be, the layout is not perfect but it's just to show the principle that you can edit the search template and now if I go back to my site, I can actually search for, let's say, I don't know, shh. Even without reloading the page, I can search for Schindler's list and I can already see the updated blocks show up here because the content for this search is just the HTML that is part of the search template. So yeah, this is basically like a teaser of the functionality that we want to bring into WordPress and yeah, I'd be very happy to hear people's questions and concerns and yeah, any ideas. So stop sharing. Yeah, I think if anyone has questions, just go ahead and unmute and ask them or if you're more comfortable dropping them in chat, I can facilitate that or I don't know if anyone has their hand raised. I don't see anybody hand raised. So if, yeah. Yeah, I'm happy to get much more technical than this, by the way, just depending on people's appetites. Yeah, I'll just go ahead and ask, like just say that like button, like how much, like, what is the code for something that look like? What are we at switch to do as developers to build that functionality? Sure, yeah, I can, in fact, I have it open up. I can just show it, I can show my screen and show you. Yeah, that'd be great. It's, give me one sec. All right, so this is the repo for the very same demo that you have just seen. And by the way, this code is all up on GitHub as well. So you can take a look there. I don't know if Ryan has dropped the link in the chat perhaps. Yeah, it should be in chat there. I can drop it again though. Okay, yeah, perfect. So there are a few pieces. So of course, you will first need the interactivity API runtime. At the moment, it's distributed as a plugin but we are aiming to merge it into Gutenberg at some point. So there's no definite date. There's no definite timeline yet. At the moment, yeah, you can just install it as a plugin and use it to build your blocks, your interactive blocks. For the interactive blocks, you'll need a couple of things. So first off, you will need block JSON and add interactivity true in order to opt in for your block to be an interactive block, all right? And then you will want to, well, you also want the few script. This has been part of WordPress for a couple of releases now. And you can add your view and render files to... So yeah, let me start perhaps with the render file. So the render PHP file is the file that is used to render the front-end content of your block. And in here, you'll see there are a couple of things that you might not be used to. So for example, this WP store. I was gonna say, yeah, what is the WP store on PHP side? Yeah, on PHP side, this I believe is not mentioned in the proposal itself. This is a way to create initial state on the PHP side on the server so that you can preload your store on the JS side, right, on the client side. You can preload it with some initial values from the server. So you could, for example, do something like, let's say, not selector, but maybe like state. Yeah, let's go with that. And yeah, you could have, you could pass, you know, you could maybe like translate the movie title here. And you could use the... Okay, let's say it's not like movies, but maybe, yeah, okay, let's make it array. And then, I don't know, one is some, I don't know, some movie title. I mean, it's a dumb example, but just illustrate the idea that you can do some pre-processing of your state on the server. Does that make sense? Yeah, totally. Yeah. Yeah, and then your PHP file, you'd add your directives like the data WP context, which will, in our case, let me maybe perhaps remove this so we don't get confused. So in the context, we will store the ID of the movie and then on a click, you'll add it, yeah, you call this action, which is defined in the view file. And this will add this current movie to the array of like movies. Does that make sense? Yeah, that's a great example. And it's simple to follow. So that's what I was concerned about a bit, how complex this is, but it seems pretty straightforward, at least in this example. Okay, yeah, I'm glad to hear that. Yeah, there's a bit of, in your PHP file, there's a bit of PHP, HTML, and like JSON, like Alt and one line of code. So that's a bit odd to see. Yes, so this actually, it's a known concern. So let me go to this way. I think there's already an issue on GitHub. I don't recall who has started working on this to create some helpers specifically for like passing serialized data to the context so that you don't have to do like three different languages on one line, which is a bit unwieldy. Yeah, I could definitely see folks getting like tripped up on that a bit, but outside of that, it looks pretty straightforward. A couple of follow-up questions in the chat that I'll just jump in now before we lose them. But Weston Reuters asking, how has state persisted? Like the life movie state, for example, is that just not currently wired into the user meta, for example? Yeah, so currently in the demo, no, it's not persisted in any way. So you could, I guess you could do it just like you could do, you could do whatever you want. Let me say it like this. So the state that you have in your store, you can store it in local storage. You can store it. It would be feasible, for example, in your actions to hit the REST API to save that liked option to a user meta. But is that part of the current API now? I think, Weston, please correct me if I'm wrong, but I think that's kind of where you're going with this. Is there a mechanism in place now? Yeah, so at the moment, there is no mechanism for it. So there is no way that's built in into the interactivity API to persist it from the client to the server. But yeah, it's something that we're very much aware of that people will want to do in the future. Yeah, so we have, we've been thinking about it a little bit, but it's not, we haven't decided yet if we will do it via the REST API or by, for example, yeah, there is, so I can say this, there is one example that I could maybe show super briefly. We have been working on a very, very early experiment of a comments forum that uses interactivity API and it shows the comments and reloads the comments. Just, Mihail, can you just zoom in a little bit? Can you just make your font size a little bigger? There's just been a request in there. Is that, is that good? I think so. I mean, that's good for me, but M requested it. Yeah, let me just, that's okay. I'll just bring up this example. So we've worked on an example where the comment forum can submit comments back to the server and then using a post request and then get that content, get that content, basically grab that content that's received back from the response and then diff the page and put the comment in the right place on the page. So I think the interesting code will be here in the index PHP perhaps. Let me, no, in the Vue.js perhaps. So I don't know if everybody can see this, maybe I can make it a little bit bigger if that was the request, but there isn't a lot to do it. So it's basically one action which grabs the form data. Obviously it's still an experiment, an entire example. It posts it to WP comments and then gets the response and it will diff the DOM and then do a client-side navigation. So just skipping over a lot of details here. Just want to note that this type of interaction, in this case it has to be also integrated with client-side routing, which is what this navigate function does. This is something basically too, it was a long answer to a question to which I can just say yes, it's something that we are thinking of but it's not the current focus let's say. So we want to make sure that the API is solid as it is first without the server-side persistence and we will add it in the future. But it is currently, you can install this as you're doing now and you could roll your own solutions for persistence at this point, right? Yeah, so you could do something like what is done here in this example, yes. But of course with all the caveats that the API is still very experimental. All of it can break at any point. Related to that original question, there's another question about cache logic that's part of the API, I assume. The question is related to the question above, which was the question about state persistence. Is there any cache logic that is part of the API? I mean something searching, something searching for the same movie more than one time before refreshing the page. Okay, so I wonder what, caching at what level the person had in mind. My guess, just having read that, my guess would be similar to how if you hit a data store and now you hit it the first time and then the second time, if I do entity records for posts, I get the 10 most recent ones and it doesn't hit the server every time I recall that. That's my guess. This question is from Renato de Carly, if I'm de Carly Rosa. So if there's a follow-up stuff in there or if I'm making assumptions I shouldn't, please let me know. Is there a caching layer of any form at this point? Yes, yes. In fact, the pages are in the demo. It's using client-side navigations and the HTML pages for the individual movies, for instance. They are both prefetched and cached locally. So this is why you can navigate instantly to an individual movie page. So the demo is configured in a way that all the links in the viewport will get prefetched. It's also something that we want to make configurable so that if you opt into having client-side navigations, then you can prefetch, for example, all the links. You can prefetch only the links on hover. You can maybe only prefetch them with intersection observer, stuff like that. And so this is the part where the cache gets populated and the pages are being cached for subsequent navigations. There's a question in chat about what about the store? Does it get cached? Does the store get cached? Could... Which part of the store would you... I'm not quite sure what caching in this context would mean. Well, I guess right. So we have that PHP file that populates the initial store, which renders your HTML. I guess does the client-side store get cached too? Is that dynamically generated like when it loads? What's that interaction look like? I don't know if that helps clarify. So the store is populated with the data from the server side. So this store, right, it will... If there exists a WP store, by the way, just noting that this naming is not final, so it's not... It might be WP store, it's likely to be something else in the future version of the API. It will populate the data for the store on the client-side. And this store is not... So if you reload, like if I reload this tab, for example, there is no... this state gets blown away. So you'll see that there are no likes anymore. So the state is not preserved. However, if you're due to what I was showing, perhaps this is what the person meant by this question.  Because we are doing... Perhaps I should explain a little bit what I mean by client-side navigations and how they are used in the API, because this is perhaps a source of confusion. Sure, I think that makes sense. Yeah, the navigations that are happening right now, they are like a single page... They are like navigations in a single page application. And there is no reloading of the whole page. It's just that the HTML for those pages has been prefetched and it's cached, and the interactivity API diffs the page, and in a way... I could say similar sort of conceptually react server components work without going too deeply into technical details now, and then diffs the page, and then patches it with the HTML from this new page. So for this reason, yes, the store is... I wouldn't say cached, but the store is preserved across the navigations, because they are navigations in JavaScript. So all the JS state is preserved on the page. I hope this made sense. I can try to clarify. We got a thumbs up. I think... Yeah, that makes sense, I think, in the sense of... It's cached in the sense of it's a big JavaScript object that's running in the browser. But beyond that, because there's not really a persistence portion in Iron Dev, there would be no way to cache that on the server side. No. So I could... Yes, by the way, there's one thing I could show. In the interactivity plugin, it has just one setting, which is client-side navigation. So if I turn it off and save, and I go back to the page... Oops. Yeah, if I reload the page, let's say I like some movies, great. I'm still on the same page, so the likes show up and they're synchronized. But if I now navigate to a new page, the state gets blown away because I've disabled the client-side navigations. So this is just doing a normal, regular page reload. So the interactive blocks keep working, but we don't have the client-side navigation. We don't preserve the JS state. I hope this helped clarify it a little bit. I have a couple... I have some pre... It makes sense to me from Richard. So I have just a list of questions that we can ask, and maybe we can rapid-fire them through them if you'd like. One question is, how can I learn more about this? Where can we get more info on this? Sure, yeah. So obviously the proposal itself, I think there were a lot of great comments there as well. We've tried to put some effort into the FAQ at the end of the proposal as well to sort of pre-empt questions that people might have about it. And then there... We are actively working on the API on GitHub. So there is a repository that I... I guess you have posted a link to. Yeah, I'll... Yeah, as well as... If you want to look at just examples of how this particular demo has been built, there is also a separate repository for that. And yeah, you can find us also obviously on the WordPress Slack to hit us up with any questions that you might have about it. Cool, so there is... Under the hood, there's some pre-act use going on here. So the question is, why did you use pre-act over react as in the editor? Right, yeah. So there are a few reasons for using pre-act over react for us. So first one, just right off the bat, is the size. So pre-act is about, if I remember correctly, 5 kilobytes or so. And react is... Well, it's significantly more. I don't remember the exact number. React plus reactdom is about 50 kilobytes maybe. I might be misremembering it, but it's significantly more. So it gives us a lot more budget for the JavaScript of the website to fill. And secondly, the pre-act is very extensible. And it has something called pre-act hooks. So not to confuse it with the hooks in the same way that react has hooks. So pre-act has... In fact, I think they're called... Sorry, I think they're called option hooks. Yeah, I should be clear about it. It's a way to extend pre-act itself, which is something that react does not have. And this is what we were able to use to create the directives layer on top of pre-act. And this is what we're also... We're able to use to create these client-side navigations feature as well. And yeah, the react also has... So it's compatible with react through a pre-act compact package. So in case we ever want to reuse the same code across the block editor and the front-end, there is sort of a pathway towards that. And yeah, the... So pre-act is very performant. It's also... There are a number of reasons. It's performant, and it also... It's more HTML-friendly than react. So pre-act is, for instance... Let me phrase it this way. So react has some incompatibilities, for example, with web components, which pre-act does not suffer from. So there are a lot of small, medium reasons that kind of all together pointed towards pre-act for us. The follow-up question to that is, does this mean Gutenberg will move from react to pre-act, the project Gutenberg? Right. No. I think at least in the short to medium term, there are no plans to do that. So I think there would be... And in fact, I don't believe there would be any benefit to that, really, for the block editor. So the reasons that we are concerned with in choosing pre-act for the front-end, they don't really... They're not the same for the block editor. So while the bundle size is important, of course, for the block editor, it's less of a concern for... Sorry, the bundle size is a concern for the front-end. It's a bit less of a concern for the block editor because it's only just loaded once. And yeah, so we have no plans to switch to that. Okay. Great answer. If anyone else has questions, feel free to drop them in. I'm just going to keep going here. But do I need to migrate all of my blocks to use the interactivity API? Right. No. The thing with the reactivity API is that it will work alongside any other blocks using any other system, jpanel.js, jQuery, whatever. So you don't have to migrate all of your current blocks to it. There are some benefits, though, to having all the blocks on your site use the interactivity API if that's a possibility. So, for instance, the client-side navigations that I've been talking about before that I've mentioned, which allow you these kind of seamless page transitions, those will only work if all of the blocks, all the interactive blocks, opt into using the interactivity API. So there is, yeah, if you have other blocks that are using other interactivity mechanisms, there is a likelihood that they might break with using the client-side navigations. So for this reason, they should all, if you want to have these page transitions as a user experience on your site, all the blocks should use the interactivity API. Cool. Next question is, can I use directives in the block editor? Maybe, I don't know, if those who haven't read their proposal and stuff, maybe can you explain what a directive is and then whether or not we can use it in the block editor? Right, right. So, yeah, the directive is, the directive is any of those special attributes that starts with data, WP, for example, WP on, WP class, WP context, those are the directives in our system and you currently, they're not designed for the block editor at the moment. We are thinking of ways that this could happen in the future, but at the moment, you shouldn't use them in the block editor. So that's kind of a brief answer to that. Right. Okay. Sorry, go ahead. Yeah, no, no, go ahead. Yeah. Okay. There's a question coming in from chat. PHP actions and filters while loading a new page through the API on the front end are already totally solved? Question mark or are there challenges to solve there yet? I think this question has to do with the client side navigation and making sure that all those hooks and filters that we know and love are actually being fired. Yeah, yeah, yeah. Yes. So yeah, that's a really good question. PHP actions and hooks indeed are, you can say solved. So what that means is that I think this person is referring to the problem, which happens if you have any sort of JavaScript framework doing the rendering or hydration on the client side. And then you have some PHP actions and hooks that can change the server side markup. So in this case, you'd end up with a with markup on the client side that that's generated, let's say by react. That is different from the markup that's generated by the server because the PHP actions and hooks, they only run on the server, they can't run on the client. But in this system, using directives, all the HTML, so the content, the directives, they are generated on the server side. So there is no hydration per se happening in the same way that there is with let's say with just react. So the any HTML that you, you will modify with with your actions and filters, it will still exist on the client side so you don't have to worry about it. That's awesome. That's such a great question. Thank you for asking that one. Very cool. All right. Oh, okay. This question, how can I preview the interactivity in the editor? Yeah, so the, I think, yeah, you mean how would you. Okay, how would you preview it in the editor there. The editor side of your interactive blocks is basically up to you at this point. So, yeah, you. So yeah, like I was like I mentioned before that we are thinking of ways that you could use the interactivity API and the editor. But, and there is there's some potential for it but for now they're not designed for the editor so you have to your edit JS files, they have to be so this is for example. Right, the movies demo, the edit JS file of this, this movie like button or movie like icon. Yeah, it's just a static emoji so you don't, you can't really see the interaction in the editor just yet.  So what I'm saying, so it makes sense, you could fake it in a sense that like you could re redo. You could do the same interactions, just using react here on the in the editor side and use react blocks to, let's say like do some use state here. And then pass, I guess like an on here like passing on on on click, right. So you could sort of fake it on the editor side but there is currently not a way to to read like, like it was phrased preview the interactions on the editor side. But yeah, it is something that we are we're thinking about and we will work on. Awesome. Next question is, do I need to know react PHP and this new interactivity API. Do I need to. They need to know PHP react. And this new interactivity API. Interactivity API. Right. So you don't. Well, you, you do have need to know PHP and react in order to create custom blocks already. I would say at least custom dynamic blocks. So you if you want to add interactivity to your blocks using the interactivity API, yeah, you will, you will. At least needs to understand how to add directives to your, to your PHP files, but I hope that the API is very straightforward and it's, it's just adding attributes to to HTML generated by PHP and adding a bit of state in your state and actions in your view JS files. This covers, I think a large portion of what what people want to do. And, in fact, you don't have to so if you just want to add the interactivity. On the front end, you don't have to write any react or pre act. Unless, unless you are writing custom directives. So if you only use the built in directives like the data WP on click data on class context. You do not have to actually write any components react or react. That was good. Can I ask how many directives are part of the default package? Yeah, good question. I also, it's about, I want to say, a dozen. So it's, I can, if I go to GitHub, I can tell you exactly. So I think there are, actually, if I, I think in the proposal that we do already mentioned all of them actually, if I scroll down there. Yeah, there is, yes. So the, yeah, these are all the directives that we, we want to have in the runtime eventually, not said just, I just want to be clear that not all of them are implemented yet. So the, for instance, WP error is not implemented yet in the, in the runtime. I think WP. I think all the other ones are, no, yeah, the salt and fill ones, one is not either, for instance, and yeah, it's very likely that in the, if there is like an initial version of the interactivity API as let's say part of Gutenberg that it will initially be a smaller subset of those directives. And to follow up, you mentioned, like writing custom directors, how, what is that, what do you have any examples of that, like that you can share. Yeah, I get a good question. Let me think too. I don't have an example handy, I think, and let me see if there was an example here in the WP demo, I think. Perhaps in the video player was the one. Let me see there. No, I think not. But yeah, I could, yeah, I could show you so let me, let me show you how directive is implemented in the runtime so that you can kind of get a feeling for they are implementable in the very same way that you would extend the, that you would add them in your code. So if you go to, for instance, directives, this is, oh no, sorry, here, runtime, directives. Can we close this? Yeah. For example, let's take something simple, like maybe, yeah, on. So yeah, by creating a directive is a matter of calling the directive function. So this is like a generator. I don't know what to call it for directives. The name for your directive and the second argument is basically it's actually a preact component. So this whole thing is actually a preact component and it might sound a bit weird, but it's actually very, it's a very powerful way to express custom directives. Yeah, well, thanks for sharing that too, because I just wanted to have a visual idea of what we, you know, I'm just thinking through ideas like what can I build with this, you know, and how would I do it. So, thanks for just sharing that part of the code. Yeah, yeah. Sorry, I got caught up in the code there. So I have a question for you. It's on our list, but I'm going to jump over to it. So I write a lot of blocks. And what is the benefit of using this API over what I'm doing now? So for the example of like the blocks that have the heart block, the sort of the life block, like I have a VJS script where I have my whatever JavaScript in there doing whatever. What's the benefit of migrating my existing block over to that? Or why should I go with this instead of just doing what I've been doing up until now? Yeah, so that's a, yeah, that's a, that's a, that's a very good question. So I would say that the benefit number one is standardization. So you, you're opting into a system that we hope will become standard for all WordPress blocks. So what that implies is then that for example, the different blocks, when they use the same system for interactivity, they can communicate with each other. So you can have a gallery block talking to a dropdown block talking to another block and they use, they all use the same basically the same store and actions for talking to each other.  So that's, I think that's one big benefit. Having, yeah, I think having the interactivity API also, also is a benefit, for instance, with the client side navigations that we, that we showed off in the demo. It's, it's not something that you can just bolt onto your, like your page built with just vanilla JavaScript and or jQuery or just some other, any other JavaScript solution you, it's something that you want you have to kind of take into account. As you design your whole page, like if I, if I can phrase it this way. So with interactivity API, it's designed to work with client side navigations from the get go. So you, if, if your blocks all use it, then you get that benefit from just by using it, you can, you can get these smooth page transitions. Yeah. And, yeah, I hope that it's, if the alternative is using, is using react, just react to render your blocks or just use, just use vanilla JavaScript, I think there are advantages to either one, like above either one of those solutions. So if you just use react, then you can't server side render your blocks, right? Because react, you can't run a NodeJS server with WordPress. If you're just using JavaScript, then that's great. But then you are always reinventing the wheel for, for, for, you know, for every, you have to add custom solution for every little thing that you, that you want to add to your block. And you're probably better off using a standard, like, like we're proposing. So yeah, I hope. Yeah, that's, that's a great answer. Yeah, I hope that answers it. Yeah. There's a couple of questions in chat, and I just wanted to get this one out of my head, but so feel free to answer it later, but it's, is there a single store across the entire front end, or can different because you're calling store in every block. What if I had, like, what if I wrote a block and Justin wrote a block and I installed that on both my pages, would the store be the same? Or would there be multiple stores per block? Yeah, good question. Yes. So there, there is, there will be one store. The stores get merged on the client side. So this is perhaps this was not the most clear feature. And maybe it wasn't clear why the stores are structured this way. So they have the, the store function has selectors actions and then they have this, I guess, a namespace, what you could call it, and then the name of your action. The reason for it is, is precisely that that the stores are merged on the client side. And if you have multiple blocks using the store, then you want to sort of, you want to avoid name clashes. You want to avoid, yeah, your, your stores getting over right. That's a, that's a great answer. Sorry, I'm not trying to rush you. We have one more minute and there's still three more questions in chat that I definitely want to get to. Larry is asking as a beginner with API, can you please mention the tools that I'm required to install for learning API testing? I'm assuming Larry is referring to the interactivity API. Maybe just give us a Cole's notes of what you're going to need to get started. And yeah. All right. So if you'd, I assume that you want to use it on your site to write interactive blocks with it. Is that correct? That would be my assumption as well. Yeah. Yeah. Okay. Yes. So you would need the, the interactivity API plugin. So you could get it, for example, from it's not currently in the, in the WordPress, the plugin repository. But you can just get it from the releases page, which I can't see right now. Yeah. Okay. That's because I had zoomed. Okay. Yeah.  I would advise perhaps, or I would suggest to look at the code of the WP movies demo to look at the blocks there and how they are organized and the bits and pieces that you need. So the huge JS file, the rendered JS file and what to include in the block JSON, for instance. Okay. Looks like Larry is asking for more generic stuff. Larry, go ahead and ping me after them after this and I'd be happy to help you out with that. I just want to keep the questions specific to the interactivity API, but I'm more than happy to talk to you about this after Anton also has a question which is related to why should I use this. Are there significant gains or tradeoffs between this and something like Alpine JS that is directed based as well for interactivity. Okay. Yes. Yes. So that's a, yeah, again, a good question. And yeah, that's probably a bit of a longer answer. I'll try to make it as short as possible. Yeah. Alpine is a great framework. It was definitely an inspiration for the interactivity API with Alpine though. Alpine is not compatible with server side rendering of the directives, for instance. So, yeah, I don't want to get, yeah, if we only have a few more minutes, I don't want to get into all the details. I believe that we do specify it in the proposal. It might be a bit, you might have to search for it in the body of the text. The other advantage over just Alpine is that, yeah, with, so we chose basically, let me put it this way. We chose the API to be built on top of Preact rather than just using Alpine, which to me comes with more benefits, like Preact having a bigger community than Alpine, which is just maintained, as far as I understand, is just maintained by one person. With Preact, you get a better syntax for creating custom directives. So, like I was mentioning, I was showing it before. No, this is not it. I think it was on GitHub, perhaps. Yeah, to make it brief. So, to create custom directives, the custom directives are basically just Preact components, which I think is a much more elegant primitive for creating those custom directives than the Alpine way. So, yeah, I think all those reasons, I think to me speak to Preact being a better Preact and the interactivity API that's being built on top of it is a better option. Great. Awesome, awesome, awesome. So we're about four minutes over. If anyone else has any other questions that they'd like to, well, there's a couple more questions. I'll just kind of like throw them out again. We can stay a little bit longer if people ask you. Yeah, that's cool. As long as you have time. Sorry, I'm just assuming you don't have time today. Yeah, that's fine by me. So, a question, is this going to be a plugin or will it be part of core? Right. Our goal is to merge it into Gutenberg and then eventually make it part of core. Yes. At the moment, yeah, we do distribute it as a separate plugin, but it was from the beginning, our goal to make it into Gutenberg and core. What happens with naming conflicts? I can imagine plugins, same toggle actions.toggle, for example. Right. How does the API handle that? So this was the reason for us to introduce this namespacing in the stores. So this is, let's say, I think it's not a hard requirement in a sense that it's, I think it's not enforced by the framework at this point, but we might make it so in the future that in your store, you have selectors, actions, effects, and state, and then a namespace, and then either the name of your action, state or whatever, or some other maybe even more deeply nested object. So this is a simple way to avoid the conflicts. Just quick follow up on that. So let's say that I, like I keep using Justin as an example because he's right there in my viewport, but if I had a store and I use WP movies, I had a store selectors, WP movies, and then a thing called save, how would it handle, like if I did use the same namespace, how would it handle conflicts? Or what's the plan? Maybe you probably haven't hit that edge case yet. And if that is an edge case, I'll just shut up and we can move on. I was wondering, what's the plan there? Yeah, so it would get overwritten by the contents of one or the other block basically. So it's, yeah, there, I think, yeah, it's exactly an edge case. So there's no, we are, we're, at the moment, yeah, we're banking on people using the namespaces for avoiding conflicts for this reason. And it's not, I mean, I think it's not unlike the name block naming scheme or pattern at the moment. So you are encouraged to also like name your block with something like this, right? So that there's no confusion between the block names, right? So it should be something, some namespace slash your block name. Okay, wonderful. I think that's it for all of my sort of pre-baked questions here. I guess we can wrap it up, unless I don't see anything else coming in in chat and I don't see anyone with their hand raised. So let me just say how thank you for taking us through this and for letting me subject you to all of its questions. And if you want to reach out to me, you can on WordPress Slack on Welcher or I'm Ryan Welcher on Twitter. You have to do that and I can help try to help answer questions. Mihael, if you're, are you on Slack? You know, would you prefer people reach out to me and I can reach out to you or how would you like to do that? Yeah, I can. Yeah, I'm very happy to answer questions directly as well. Okay. Yeah, it's. What's your, what is your past? Yeah, maybe just drop your Slack, my Twitter. Yeah, whatever you're comfortable with. If you completely put it on the spot, so sorry for that. Yeah, no problem. And your home phone number, your mailing address and all that stuff, right? Yeah, I'm just trying to remember if it's, yeah, that's it. Okay. Because I have a different one. Yeah, it's just that's my, that's my handle. This should be the link to get into the chat. Oh, thank you, Weston for doing that. Also, well, just a couple of sort of like housekeeping things. I just wanted to mention that the developer blog, a developer that will press.org slash news is now at a beta and it's live. Go read all the awesome stuff that Justin does there. The 6.2 is out. So if you haven't updated, go ahead and update the development of 6.3 is in fan is in the planning stage right now. I'll drop a link here for sort of for the 6.3. Development cycle stuff. A couple of word camps coming out work in Europe is eight June 8th to 10th. Work in US is August 24th 26, and there's lots of local word camp stuff being scheduled. I'll just put links in here. But yeah, but thank you for coming and we have thank you for taking us through this and like I said, if anyone has any questions they can reach out to me and I can wrangle them or however we want to do this but otherwise I think we can call it a meeting. So, thank you. Awesome. Yeah. Thank you so much, Ryan. Yeah, that was great hosting from you. And yeah, I was very happy to be here and answer your questions and yeah peace. Feel free to reach out to me as well directly if you have any questions about the interactivity API. And yeah, be very happy to hear your questions and your feedback. Okay, well, I'm going to end the meeting but thank you everyone and I'm going to be putting the recording up on repress TV as soon as it's sort of ready to go. So, thanks a lot everyone talk to you all soon. Bye.


Live from Las Vegas, it's theCUBE. Covering Dell Technologies World 2019. Brought to you by Dell Technologies and its ecosystem partners. Welcome back to theCUBE's live coverage of Dell World Technologies here in Las Vegas. I'm your host, Rebecca Knight, along with my co-host, Stu Miniman. We have two guests on the segment, both CUBE veterans. So we have Varun Chabra. He is the VP Product Marketing Cloud Dell EMC and Minidzudin, VP Solutions Product Marketing at VMware. Thank you so much for coming on the show. Thanks for having us. Thanks for having us. So we just had the keynote address. We heard from Michael Dell, Satya Nadella, Pat Gelsinger. It's a real who's who of this ecosystem. Break it down for us. What did we hear? What is sort of the most exciting thing from your perspective, Varun? So, Rebecca, what we hear from customers again and again is it's a multi-cloud world, right? Everybody has multiple cloud deployments, right? We saw Pat mention five on average, right? Cloud architectures and customer environments. And what we keep hearing from them is they, there are operational silos that develop as part of the tool set, the SLAs that are different, the machine formats, all of these things just lead to a lot of operational silos and complexity. And what customers are overwhelmingly asking Dell EMC as well as VMware is that how do we reduce this complexity? How do we be able to move workloads together? How do we manage all of this in a common framework and reduce some of that complexity so that really they can take advantage of the promise of multi-cloud?  I feel like everywhere I go, it used to be, it's like Intel and NVIDIA up on stage with the next generation. Well, for the last year, it felt like Pat and Sanjay or somebody like that up on stage. We have the Google Cloud event a couple of weeks ago, there was Sanjay up on stage. Come here, there's Satya Nadella up on stage. So let's talk about that public cloud piece. We know the relationship with AWS, VMware Cloud on AWS sent ripples through the industry and the Google Cloud piece. So tell us what's new, anything different about the Microsoft piece when it comes to public cloud and how does that fit with relation to all the other clouds? Sure, now I'll amplify what we're saying, right? We think about customer choice first and really customer choice, as you know, you've got multiple cloud providers.  Why are they going towards the multi-cloud world? It's because applications are going there and really VMware strategy has been to say, how do we empower customers with that choice? Our AWS partnership is as strong as ever, right? We continue to innovate there and that was our first kind of choice of platform and Pat alluded to this on the stage. We have 4,000 cloud provider partners, right? And the 4,000 cloud provider partners we've built over the years and that include not small names, they include IBM. They've got rack space, some of the biggest cloud providers. So our strategy has always been how do we take our stack and land it in as many public clouds as possible? So we took the first step of IBM then about 4,000 other cloud providers to be it rack space, Fujitsu, Hitachi, then came Amazon. Amazon being the choice of destination for a lot of public clouds. Today we kind of further extend that with Microsoft and a few weeks ago with Google, right? So this really about customer choice and customers when they want the hybrid multi-cloud piece is app driven, right? You've got two worlds, you've got an existing application and you're looking to just get some scale out of that existing application and you're building a lot of native cloud native applications. They want this in multiple places. All right, so if I could just drill down one level deep. So if I'm an Azure customer today, my understanding is the VMware SDDC stack, what does that mean? What do I use? How does that look and feel compared? Do I use the Microsoft system center? Am I using V center? Sure, this is really again an app driven conversation, right? There were multiple announcements in here just to unpack them. It was like, hey, we had the Dell Technologies cloud platform. The Dell Technologies cloud platform is powered by Dell EMC infrastructure and VMware cloud foundation on top. Virtualizing your full compute network storage with vSphere, vSan, and SX and management, right? And the second part was really, we've got VMware cloud on Dell EMC. This is to bring a lot of the workloads which sit in public clouds. We're seeing this repatriation of workloads back on the data center or the edge. This is really driven by a lot of customers and who have built native IP in the public cloud, be it Amazon, be it Azure, who want to now bring some of those workloads closer to the data center or the edge. Now this comes to how do I take my Azure workloads and bring it closer to the edge or my data center? Why is that a need? We have large customers, large customers, multinational, they have 500,000 employees, 90 locations worldwide who've built to IP or when I say IP applications natively in cloud, suddenly for 500,000 employees in 90 locations, they're going ingress, egress traffic to the cloud, public cloud is huge. How do I bring it closer to my data centers, right? And this is where taking Azure workloads, bringing them on-prem, closer, solves that big problem for them. Now, how do I take that workloads and bring them closer is that's where we landed in the VMware on Dell EMC infrastructure because this brings you closer to the data center, gives me either low latency, data governance, and control as well as flexibility to bring these workloads back on-prem, right? So the two tangents that you're driving, both your cloud growth and back to the edge, the second tangent of growth or explosion is cloud-native workloads. You're able to bring them closer to your data center is really the value proposition, right? Well, we heard so much about that on the main stage this morning about just how differently the modern workforce works in terms of the number of devices they use, the different locations they are when they are doing the tasks of their job. Can you talk a little bit about the specifics in terms of customers you're working with? You don't need to name names, but just how you are enabling those people. We get feedback from customers in all industries, right? So, you know, Muneeb can share a few as well. We have large banks that are, you know, they're standardized workloads on VMware today, right? As have many organizations and they're looking for the flexibility to be able to move stuff to the cloud or move it back on-premises and not have to reformat, not have to change their machine formats and just make it a little bit easy. They want the flexibility to, you know, be able to run applications in their bank branches, right? In the cloud, right? But then they don't necessarily want to adopt a new machine format or a new standardized platform. That's really what the Azure announcement helps them do. Just like with AWS, you can now move workloads seamlessly to Azure, use vCenter, use your other, you know, tools that you're familiar with today already to be able to provision your workloads. All right, so, I wonder if we can drill into the stack a little bit here. You know, I went to the Microsoft show last year and it was like, oh, WSSD is very different than Azure Stack, even if you look at the box and it's very much the same. Underneath the covers, there's a lot of discussion of VxRail. We know how fast that's been growing. Can you, I believe there's two pieces of this. There's the VCF on VxRail and then, you know, just help explain- Yeah, so for the Dell Technologies Cloud platform announcement, which is as you said, VxRail HCI infrastructure with VMware Cloud Foundations tightly integrated, right? So that the storage, compute, and networking capabilities of VMware Cloud Foundation are all incorporated and taken advantage of within the HCI infrastructure. This is all about making things easier to consume, right? Reducing the complexity for customers. When they get VxRail, they overwhelmingly tell us they want to use VMware Cloud Foundations to be able to manage and automate those workloads. So we're packaging this up out of the box so when customers get it, they have that cloud experience on-premises without the complexity of having to deploy it because it's already integrated tightly. The engineering teams have actually worked together and then you can then, as we mentioned, extend those workloads to public cloud using the same tools, the same VMware Cloud Foundation tools. And you know, we've built on Cloud Foundation for a while and I'm sure you followed us on the Cloud Foundation. And that has been when, you know, yesterday we talked about consistent infrastructure, consistent operations in this hybrid cloud world and what we really mean is that VMware Cloud Foundation stack, right? So when we talk about VMC on AWS is that Cloud Foundation stack running inside of Amazon. When we talk about, you know, our partnership with Azure is that VMware Cloud Foundation stack running on Azure. When we talk about this 4,000 partners, Cloud Certified, IBM, it is the Cloud Foundation stack. And the key components being the full stack, vSphere, vSat, NSX. And there's a critical part in Cloud Foundation called life cycle management. It's, you know, it's missed quite easily, right? The benefit of running a public cloud, the key three attribute you get is, you know, you get everything as a service. You get all your infrastructure as software. And the third part is you don't spend any time maintaining interoperability between your compete network storage. And that is a huge deal for customers. They spend a lot of time just maintaining this interop. And, you know, VMware Cloud Foundation has this life cycle manager which solves that problem. That is key. Thank you for bringing that up. Because, right, one of the big differences is you talk about public cloud. Go talk to your customer and say, hey, what version of Microsoft Azure are you running? And they'll laugh at you and say like, well, Microsoft takes care of that with me. Well, when I differentiate and I say, oh, okay, well, I want to run the same stack in my environment. How do I keep that up to date? We know the VMware, you know, customers like there's lots of incentives to get them there, but oftentimes they're N minus one, two, or something like that. So how do we manage and make sure that it's more cloud-like and up to date? Yeah, absolutely. So there's two ways to do that. One of them is because the VMware and Dell EMC teams are working on engineering closely together, we're going to have the latest version supported right out of the gate. So you have an update. You know that it's going to work on your hardware or vice versa. So that's one level. And then with VMware Cloud and Dell EMC, we're also providing the ability to basically have hands-off management and have that infrastructure run in your data center or your edge locations, but at the same time, not have to manage it. You leave that management to Dell Technologies and to VMware to be able to manage that solution for you. So really, as Muneeb said, bringing that public cloud experience to your on-premise locations as well. And I think that's one of the big differentiators that's going to come, right? People want to get that consumption model and they're trying to say, hey, how do I build my whole data center, maintain it, but at the same time, I want to rely on Dell and VMware to come and help us build it together, right? And the second part of the announcement was really, hey, VMware, Dell on Dell EMC is that Manishers offered. The demo you saw from Junyang was being able to have a consumption interface where you can kind of click off a button, roll it back into a data center, as well as an edge. Because you have literally very little IT skill sets where in the edge environment. And as edge compute needs become more prolific with 5G IoT devices, you need that same kind of data governance model and data center model there as well. And that really the beauty of coming to VMware and Dell EMC, Dell Technologies Power is to maintain that everywhere, right? It comes down to listening to customers, right? As Dell Technologies is VMware, we have the advantage of working with so many customers, like hundreds of thousands of customers around the world. We get to hear and listen and understand what are the cutting edge things that customers are looking for. And then we can now take that back to customers like Bank of America who may have thought about certain scenarios, right? That we will learn from, but they may not have thought about other industries where things could be applicable to their industry. So that drives a lot of our innovation, where we are very proud about the fact that we're customer focused. Our innovation is really driven by listening to customers and, you know, having smart people just work on those, when they work on those problems.  Customer choice, that's why we're doing what we're doing with multiple cloud providers, right? And I think this is really a key to, if you just look at VMware's innovation, we're already talking about this multi-cloud world where it's like, hey, you've got workloads natively. So we, how do you manage those? We're already ahead in thinking about, you know, Kubernetes with acquisition of Heptio. And if you think about it, you know, we've done this innovation in the cloud space, established this hybrid credibility and we've launched it with Dell Technology now. We're already ahead in this multi-cloud operational model. We're already ahead in this Kubernetes evolution. We'll bring it back with the family and listen to the customers for choice, because at the end of the day, we're able to solve customer problems, right? I think that's another dimension of choice that we offer, which is both traditional applications, as well as applications of the future that will increasingly be customer container-based. Yeah, I just wonder if you can span on a little bit.  It really simplified environment. I go back 15 years ago. One of the things it did is, let me take my old application that was probably long in the tooth to begin with. My hardware's out of date. My operating system's out of date. Stick it in a VM and leave it for another five years. And the users that are like, oh my gosh, I need an update. How do we get beyond that and allow this joint solution to be an accelerant for applications? Yeah, and I think, you know, the application is probably the crux of the business, right? It's the long pole in the tent for making change. Yeah, and applications have evolved. This is actually the evolution journey of IT itself. It's where they used to be like support systems. Now they become actually translated to business dollars.  And you can drive business value from it. And customers are thinking about this, old applications and new applications. And they have to start thinking about where do I take my applications? Where do they need to land? And then make a choice of what infrastructure is the best platform for it. So really to flip the thing on, don't think infrastructure first and then retrospect apps to it. Think apps first and then make a choice on infrastructure based on your application need. And really, like you said, VMware kind of took the abstraction layer away from infrastructure and made sure that your VMs could run everywhere. We're taking the same for applications to say, doesn't matter if it's a VM based, it's a cloud native, we'll give you the same, you know, consistent infrastructure and operations. Okay, last thing, could you just tell us of the announcements that are made, what's available today, what's coming later this year? Absolutely. So the Dell Technologies cloud platform that's based on VxRail and VMware cloud foundation is available now as an integrated solution. The VMware cloud and Dell EMC, the fully managed offer is available in the second half of this year. It's in beta right now. And as you saw, we have really good feedback from our customers. And then I think the Azure VMware solutions offer will be available soon as well. All right, well, Varun and Manib, congratulations on the progress. We look forward to talking to the customers as they roll this out. And Rebecca and I will be back with lots more coverage here at Dell Technologies World 2019, wall-to-wall coverage, two sets, three days, 10th year of theCUBE at EMC and Dell World. I'm Stu Miniman and thanks so much for watching theCUBE.


Intel IT, we've been running a very large-scale grid computing environment. In fact, that's my background, where we run a lot of silicon design over a Linux grid across the globe. About four years ago, we made a decision to run an enterprise private cloud for traditional IT. We're pretty successful. We've had it running since 2010, but we made a call a couple years ago based on our large background with open source that moving forward, we're going to do green field environments focused on open source solutions. When we focused on private cloud initially, it was basically with a concept that since we have such a large scale inside of our environment, we felt that based off of cost, security and performance, it made a lot of sense for us to continue down this path of private cloud. However, as the world has changed and clouds become more mature, we've come to recognize that hybrid cloud is really the way to go. This is because we have 68 data centers, but I don't have data centers everywhere across the globe. I really see cloud as part of the supply chain. As we push forward with this hybrid offering, I want to be able to use these open APIs. If I need a data center capacity in South America, I can use one of my partners in the public cloud space. Preferably, they're using open APIs, so my developers can write once. That's really where we're going is pushing in the hybrid state and allowing our developers to write once and utilize public or private and where we help control based off cost, performance and location where they're getting their compute and storage capacity from. About two years ago, we basically looked at all the solutions in an environment that was happening and we made a choice and basically a bet on OpenStack. Ever since then, we've been pretty successful running this in a production mode since mid-2012 and we haven't looked back, so far working great. Fundamentally, the reason that we went after OpenStack is we're trying to turn our entire data center basically into software, so all the infrastructure needs to be exposed as APIs. With OpenStack, we've been running with Essex focusing on compute predominantly, but as we move forward into the next couple months, we'll be turning on object storage and block storage to basically have a completely robust data center infrastructure exposed as APIs. With cloud, it's a great opportunity to really create an ecosystem that allows soft developers to basically run in a federated fashion across the globe. I see cloud as part of my supply chain whether it's private or public and by turning on OpenAPIs, we're really able to basically have a game-changer where the software developers can write once to many types of clouds. So the reason that we really focus on the OpenAPIs is how do we drive to a federated environment that's interoperable, meaning that they can work across any cloud across the world, we're a global company, and then three, how do we do it in open fashion? So these three elements together are very important to us, which is why we're taking such a specific step into the OpenStack space. So eventually, we'd like to just stop saying hybrid cloud, there's no public, there's no private, it's just this very large federated interoperable open cloud. You can really almost see it as utility, finally, where you're really just getting electricity, but where you're getting is compute and storage globally across the world. Whether we're doing business in China, South America and the United States, we need to operate everywhere. So having this all federated so we can connect together with similar identities, similar security, interoperable where we can basically write once or control it through our infrastructure teams with one set of controls, or open, which is really how to get there by enabling the industry to move up the stack from the core of Linux to now have open APIs in the cloud space and really allows a level of innovation to start happening higher and higher up the stack and allows us to run it as a global industry.


We are the tribe that they cannot see. We live on an industrial reservation. We are the Halusa Nation. Before I begin, I would just like to acknowledge and honor all the work that we do here currently at LMIT FM is currently being done on unceded Algonquin territory that was never given up and never surrendered.  I'm Toolman, I'm one half of tribe and I grew up on Six Nations. Nice. I'm Bear Witness, the other half of tribe. My family's from Six Nations. I grew up in Toronto. I just wanted to ask what started this whole idea of Indigenous kind of electric music? Like where did it all begin? I mean I guess it started here in Ottawa back with the Electric Power 10 years ago now. You know, we came together with the simple idea of promoting ourselves as Indigenous DJs in the city and promoting a party to the community here. So you know, I went down to the Native Students Association, Friendship Centre, places like that to throw up posters. Out of that party, it was a success from the first night, sold out and there was a real reaction from the community coming that said that this was something that was needed, that people wanted, that we had created this place for Indigenous people to gather in Ottawa and that we had to keep doing it. Yeah, so they pretty much got all hyped up and ready and just wanted to keep going with that kind of thing? Yeah, and after like a year or so of doing that, we started, you know, we wanted to give something back because that party was being so successful. We wanted to give back to the community that was showing us so much support. So that's where the idea of remixing powwow music came out of was wanting to give back. Based upon that, what do you guys want to promote through the style of Indigenous music and around the world kind of thing? It's just basically like representing ourselves.  So, you know, giving the platform to represent ourselves the way we want to be seen and do the things that we, you know, like we want people to see us do these things. So knowing that you guys are always on tour and whatnot and, you know, you might be exhausted at some points, I bet.  What do you guys do? I like to set up a, I bring like a portable studio with me and we play video games on the road. You know, we hang out a lot too. Like, you know, we go eat places and we're very, very close and like we also have dancers with us, creation and lunacy, Angel Gladue. It's a, in our tour manager, Buddha, like we all, we all, we're all just like a family. So like we all just, you know, when we need our space, we need our space, but then, you know, we're all, we're all there together. So we're all there. It's like a big, it's a family feeling when we tour around for sure. Do you have any cultural tradition that you do for relaxing, kind of like, you know, kind of go back home, you know, go hunting or anything like that or is it just kind of always on the go? We're very much like I think being a part of Tribe and being surrounded by not just necessarily the music itself but the people that we bring around us, like that get attracted from when we play shows in Brooklyn or even in Norway, you know, it doesn't matter where it is, like we'll find indigenous people there and most times they'll give us medicines too or they'll give us like, they're the, them themselves are medicine themselves to see them. So it's pretty good. It's really dope to be able to have that kind of experience. I don't think any other band has that, what we have, but that's super important to us. Tell me more about what this Northern Touch remix is all about. It's been a kind of a staple, a staple, I guess. Like it's one of those things that, you know, I grew up listening to, we both did. It was a really huge thing. It was a cross-Canada remix featuring like, you know, MCs from BC to Toronto. So it was definitely like one of the biggest music videos that I've ever remember seeing on much music back in a day. It definitely got played a lot. It's been around for a long time too. So it's like, it was an honor, I guess, to be able to recreate that. And we were just like, oh, we're like one of two people to do it. So yeah, it was really, really cool. I also hear you're doing this new concept show that you're presenting all across Ontario. Can you give me a little bit more insight about what that's all about? Yeah, we kind of started this idea now, you know, moving forward with what a tribe called Red does and always, you know, pushing ourselves further to do bigger and more interesting things and, you know, challenge ourselves as artists. We've started this concept called the hallucination band, which is, you know, really just the next incarnation of where we're going with the ideas of a tribe called Red, taking it beyond just being a club and DJ set. In the case of the shows that we're doing across Ontario, right now we're bringing in other players. So we have Respectful Child on violin and Jeremy Dutcher on piano and vocals, as well as Creation, one of our dancers who's also jumping up and playing some beats. So it's really turning into this thing where it was four turntables kind of all playing together or six turntables all playing together or two turntables and MPC has now turned into more of a band concept and trying to create, you know, create something more than just a club vibe.  I don't know if there's any particular songs, but I know that on this tour that we're doing, there has been these moments that happened because we're all in sync together, so there'll be Respectful Child, Jeremy Dutcher and us and Creation and even, you know, Miss Chief Rocker there, Lunacy, we're all on stage together all at once, all in sync, all doing something.  Yeah, I guess on this tour, my favorite moment is some of the new songs we're playing, so we're premiering songs that nobody's heard yet, songs that are going to be for the next project, that's for me is the most exciting part. When can we expect that? Or can you give us something you can't tell us? That's okay. Yeah, we're working on it. We're working on it. We're working on a lot of things, you know, we spent this past year touring more than twice the amount we have two years before it while also making an album. So, you know, we've been, we've been keeping pretty busy. Cool. Well, thank you so much, guys. You're listening to 957 Element FM.


With the fourth pick in the 2021 NFL Draft, the Atlanta Falcons select Kyle Pitz. Fight ends Florida. So, the player from Florida that's atop so many people's draft board is the best prospect in this draft period.


What's going on everyone Sam here with late in sports cars we're in one box of 2022 Can any absolute baseball hobby for Dylan P? So good luck Dylan see we can get in here for you buddy Get out of here. See if you can see kaboom Be nice being I'd be in a kaboom. We've got Bartolo cologne 135 out of 149 big sexy heck yeah Tom I'd say Louise Robert Yeah, no problem Eric Got anthony bender 99 out of 199 for the uh marlins Because I thought they were backwards and they were backwards anyway Colin welker 49 out of 75 there you go for the Rockies nice one there Still not a hundred percent of you didn't put it around We've got luke jackson that is 17 out of 99 one color uh three color three color nasty patches on that Went to the wrong way. I know I get you because you get into a groove And then you're like That classic classic groove roomer went to the wrong way classic Oh, yeah Yeah, Ken Griffey jr. Nice. That's 107 out of 149 on the blue Duel's A booklet in here as well for our total column. There's a rookie class of jaren duren One 94 out of 149 got a Fernando top each jr. 70 out of 199 nice Is player warrant on the top And a booklet five out of 10 greg deakman. Wow Gold baseball stitching three color three color patch Nice hit for you there dylan. That's a great way to end the box That's sick congrats on that new card That'll do it for your break dylan. Thanks again on the order. We'll get it right out to you, buddy


Self-awareness is this ability to be aware of your thoughts but not be your thoughts. Imagine to live this day today to have thoughts and not be entangled or attached to them. Imagine being able to have thoughts and you're able to watch yourself thinking those thoughts but not be involved with those thoughts.


I've always wanted to be a teacher and I know this school is really good education school and then I applied to St. Claude State and I came here and I loved the campus and I loved how the education program ran so I just knew I wanted to come here and I have a lot of family up here too which is kind of fun so that was one thing that really drew me to here and the education program pretty much.


Preparing your data so the programs can read it is probably the most important task in data mining. Today I'll show you how to load your data in Orange. Orange can read several data formats, such as Excel, Tab and comma separated files. The data is normally a table where data instances are in rows and data attributes are in columns. But why just do the talking and no walking? Let's make our own data. I'll use Google Sheets to create a simple data set. Say we have a group of people and we would like to know whether we can predict the gender based on their physical characteristics. Okay, our people will have a name, so we know who's who. Then we also know their gender, height and weight, and we know how they look like. So let's put down also their eye and hair color. I have this data set for my friends, Jill, Jack, Mark, Ann and so on. Their names are all strings that is text. Gender won't be a string, but a categorical value, because our people will belong to one of the two groups, male or female. My friends naturally have different heights and weights, which are numerical values. Some of my friends are tall, others short, some slim and others a bit chubby. The color of their eyes and hair are again to categorical values, since the eyes can be either blue, brown or green. And the hair black, brown, blonde or red. Now we have our data. Still, other than providing the data, I have not explicitly specified attribute types, so let's hope orange will guess them correctly. Now we load our data in orange. Let's copy a shareable link and paste it into a file widget. Let us first view the data in a data table. Orange correctly assumed the first column with names contains our meta attributes, but it incorrectly made the hair color our class variable. Hmm, maybe I should have gender as the last column in the table. But let us fix this in orange. We can rearrange the data with select columns widget. We'll put hair color attribute into features and gender in target variable box. One quick check in a data table and we're good. You can also save the data to your computer with save widget. It's best to save the data in orange's native tab format, since it automatically appends header annotations for attributes. You might want to define your data locally. I will use the same data as before, only this time I copy them to Excel. I will add two extra rows under attribute names. Set variable type in the first one and variable kind in the second. For the attribute type, I will use C for continuous, that is numerical attributes, D for discrete or categorical attributes, and S for string values. For the attribute kind, I will write class under gender and meta under the attributes that provide some extra information. Now our data is all set for the analysis. Today we've learned how to prepare our data, manually annotate it and subsequently adjust which feature is considered a class attribute.


Well, do I have some great news for you? Everybody, this is Chris from the Rewired Soul where we talk about the problem, but focus on the solution and if you're new to my channel, my channel is all about mental health. So if you want to improve your mental and emotional well-being, make sure you subscribe and ring that notification bell. But my guess is if you're watching this video, you're one of my amazing, loyal subscribers.  And yeah, exciting announcement. I am writing a book, okay? I have already written two books, so they're usually linked down in the description. I think if you want to check them out. First book I wrote was like my story of overcoming addiction, depression, and anxiety. The second one is shorter and it's for anybody who's affected by a loved one's addiction. But anyways, anyways, before I jump into what this book about depression is about, I just want to put out a reminder, like please, please, please check out the description as well as in the pinned comment. Sign up for my email list. I am going to start sending out emails with just mental health tips, advice, just things that come to my head so I don't feel like I have to put everything in video, okay? So sign up for my email list.  So yeah, this book, idea, all right? So the title of this book is going to be The Isolator's Guide to Overcoming Depression, all right? So how did this come to mind? Well, I am somebody who, I meet people where they're at, okay? So isolation, as some of you know, is one of the worst things for your depression and your anxiety. I've made videos about this in the past. I discussed the brain science and the evolutionary psychology behind this, but like if I just come straight at you and say, hey, go out, go, go do stuff, like you're going to look at me and say nah, right? So I'm making a book to take what you're doing or what you won't do and try to give you help, because everybody can get help no matter what.  So I am somebody who loved isolating and everything and like I have tips and this book is going to be filled with like scientific evidence and studies and everything to explain why certain things that you do, even though you're isolating will help with your depression. I plan on doing a bunch, a bunch of these books and I've just been delaying on it. And I know a lot of you enjoy the sound of my voice. I was actually just talking to my buddy Q-Star about how like it's weird that people like our voices, like I think my voice sounds weird and nasally. But anyways, what I'm getting at is I might, might do an audio book. I'll see how it goes. I am a writer by trade. I've been procrastinating on writing way too long so I don't want to over promise anything, but I will try to do an audio version of this book as well. But anyways, the next thing is I'm going to need your help. Okay, so first I want to give a shout out to my girl Jeanette. All right, she is an editor and she's a subscriber to the channel. And she like, I asked you, I'm like, yo, I have these book ideas and I don't know where to get started. Like every time I think about writing, I'm just like, uh, I don't know how to organize my thoughts, right? And this amazing woman took time out of her day and we sat down and we had a video call and she helped me just kind of organize some thoughts and just get started. And I love her for that. So if you are planning on writing or anything like that, I'm going to provide her links down below. Go follow her on Twitter. She's an amazing, amazing woman. But yeah, so we're talking about this and I want to get started by, you know, getting feedback from all of you. Like this book is for you. Like I already have my own ideas and things that I want to touch on, but I want to make sure that I'm doing this for you and there's going to be useful tips for you. Chances are if you're struggling with something, a lot of other people are struggling with something as well. Okay, so I'm going to ask you three questions. I'm going to post this all over social media as well as here, okay? And I'm going to pin these questions down in the comment because I need you to help me write this book. And everybody whose suggestions I use will be credited in the book. I will have an entire page or two pages depending on how many people contribute and all of you will be credited in this book. Pretty sweet, right? So question number one, what are your fears? Like anybody who isolates, there's fears, right? Like fear of, you know, being judged by people. Fear of, you know, certain interactions. Fear of being harmed, whether emotionally or physically or whatever, like what are the fears that are surrounding this, okay? And then the second question is very similar to the first, but there's a method to my madness. The second question is why do you isolate, okay? I'm guessing a lot of this ties into fears, but I would like to hear like personal experiences maybe, okay? And, you know, when I write this book, if I am credited in you, like, you know, I'll keep you anonymous or whatever it is that you're comfortable with, but like, I just like to tie in personal experiences because sometimes I can tie that in with something that happened in a previous relationship in your childhood with your parents or a family member or even at school or whatever. So why do you think it is that you isolate, okay? Or what kind of thoughts are going through your head? For example, some people don't like hanging out with friends because they think their friends don't really like them or, you know, nobody likes them or nobody cares about them or whatever it is. So question number one is what are your fears? Question number two, why do you isolate? Question number three, most important question. What are your hobbies? What are your interests? What do you like to do, okay?  I don't care if you like watching YouTube. I don't care if you like being on Twitter. I don't care if you like to draw or paint or watch TV or Netflix. I don't care what your hobbies or interests are. Just let me know, okay? Because what I'm gonna do is I'm gonna take things that you already like doing and explain with neuroscience how this helps with depression, okay? So those are the three questions. I'm gonna pin them down in the comment section below. And just a real quick Patreon plug. I know a ton of you are supporting me on Patreon. So something I've had up on Patreon, which I haven't really been able to give benefits for yet, is at the $20 tier, whoever is in that tier will get free copies of all my e-books. So I plan on selling these books for like four or five bucks on like Kindle and Audible if I end up doing audiobooks. But if you sign up for the Patreon, every book I write, you'll get a free copy digitally, all right? And I plan on doing a lot of these. I will be making more videos like this to get your feedback. Like I have books I want to write about, like, anxiety and meditation for beginners, addiction, you know, all sorts of stuff. I have a billion ideas. Jeanette helped me kind of organize them. It should give me a cool app to use. But anyway, so if you're interested, go sign up over on Patreon and you will get a free digital copy of every book I write today and for the rest of my life as long as I got that going, all right? But anyways, that's all I got for you with this video. Again, please sign up for the mailing list and I will leave the questions down in the comments below. All right, give me your feedback. I will be posting this stuff all over social media as well. So, yeah, I'm excited to get started. I plan on starting this as soon as Tristan and I move into our new apartment this week, get settled in, and I'm gonna get cracking on this thing. And like, I hustle and I write fast. So this project might come pretty quick and I'll release it. So anyways, that's all I got for you. Huge thank you to everybody supporting the channel over on Patreon. Make sure that you don't leave me hanging because I need your help to write this book, all right? I love each and every one of you and I got some new videos coming up very soon, all right? I'll see you next time.