Welcome to the last chapter, point set topology course part 1. So, this will be topological groups and topological vector spaces. Interaction of algebraic operation of addition scalar multiplication etcetera with the Euclidean topology on the one hand and the important example that we had Van Aak spaces right. They are very important ok. What are the Van Aak one Van Aak space we can emphasize namely the set of all bounded functions on a given set right. So, all these things together motivate the study of the so called topological groups on the one hand and topological vector space is on the other ok. So, this last chapter is devoted to a brief introduction to these two concepts. The first section is just a brief introduction to topological groups and the next section we will have take up topological vector spaces ok. It is no way claims that this is exhaustive or comprehensive. This is just a brief introduction ok. Let me start with recalling the definition of what is a group first so that I can use those notations comfortably. I assume that you know already groups because we have even studied group actions right. So, a little bit of group theory whatever groups, homomorphisms, subgroups etcetera I suppose you know, but let me recall them first for ready reference also. First of all you may treat a group as a you know order triple of a set G and a binary operation mu and a distinguished element E where G is a set mu is G cross G to G that is the meaning of binary operation which is associative. If you have a short notation we will use mu of G comma H as G composite H. So, G and H are elements of G. G circ H is also inside G you may relate a G composite H or G circ H. Axiom of identity there is one axiom which means another another condition here is that this distinguished element is called identity why because its action on other elements E composite G is G and on the right side of the G composite is also G for every G H ok. So, it is acting identically on other element that is why the third axiom is that for every G in G there exists a unique element G inverse ok. G to the minus 1 we written as G inverse such that what is the property G composite G inverse equal to G inverse composite G is the identity ok. The element E is called the identity element which I have been referring to for every G in G the element G inverse is called actually inverse of G. We will also use the short expression G is a group just like this X is at a logical space. So, we can suggest that G is a group instead of writing the triple G mu E etcetera each time often even the simple notation is composite instead of mu of G H we are writing G circ H, but most often when there are no other compositions you will just write as G H. If there are two three compositions then we have to distinguish we cannot write all of them as G H ok. Even there are two different groups ok one is a domain and a core domain we are using the same G H here and G prime H where I am there to mean that we have to take the corresponding multiplications from G and G prime respectively. So, such short you know short notations or abuse of notation which is there in the practice by stalwarts all the way go back to you know Euler and so on we cannot change that so we better follow those rules. In a group G if the composition happens to have this property namely G composite H could H composite G for all G and H then G is called an Abelian group or a commutative group ok this is similar to the case of integers, rational numbers, real numbers and so on. So, there the standard notation is plus G plus right G plus to G composite H, but that is not forced on us because there may be more than one composition both of them commutative ok. So, then you have to choose which one is plus plus and plus prime and so on. So, that is also not it is only customary you have to follow the customs here rather than rigid rules. Rigid rules will be followed you know logically in our mind that much we have to do by abuse this abuse of notations it just means that you are not going to get confused by this notation that is all I did ok. Let G be a group together with a topology on the underlying set G such that the product map namely x comma y going to x y inverse that I am going to denote by nu for a y that must be continuous ok. What is the continuity here G is a topological group it means it has topology ok. So, it is a multiplication is here then condition is that this multiplication is continuous means what here there is a topology here I have to take the product topology ok. The product topology from given topology on both G and G here that is what I have to take under that this must be continuous ok. We then call G is a topological group a subgroup edge of G together with the subspace topology will be called a topological subgroup provided what what you have to do the group operation is also the same because it is a subgroup ok. So, however when the context is clear we may simply mention this as a subgroup likewise homomorphisms from G to H between topological groups ok are always assumed to be continuous unless mentioned otherwise ok. Precomposing the continuous function nu from G cross G to G by y going to e comma y see y going to e comma y is a group home is a continuous function from G to G cross G right it is like a coordinate inclusion followed by x y going to x y inverse e becomes x. So, this x becomes e sorry. So, this becomes just y going to y inverse. So, that map I am denoting by eta y it is called the inversion map eta y is y inverse because y inverse uniquely defined ok. This map is called what inversion map it is called it becomes continuous by very by this observation that is no I am not making this as a hypothesis now this is a follow this is a consequence because this is a composite of these two functions likewise if you take x y going to see first composite nu and then take eta. So, x y going to x y inverse is your identity comma eta right. Therefore, these are continuous now composite with x y inverse that will become x y going to x y. So, nu of x comma y inverse is x y inverse y inverse right. So, that is equal to x y. So, this is actually the multiplication map nu which you started with that will be also continuous. So, in one single go by taking this definition namely x y going to x y inverse we have made taking inverse taking inverse of inverse of an element also taking x going to x y both of them are continuous ok. Once you have both of them continuous you can recover the continuity of nu g inverse continuous nu net limit x y going to x y inverse also. So, they are equivalent instead of one you may have two different conditions combined with that one it will give you the first condition. So, they are equivalent ok. So, 32 and 33 together imply continuity of mu all right. So, here are some examples now any group together with the discrete topology or in discrete topology is a typical group. See you have already a group. So, group operation you do not have to change. You put a topology we are very familiar with putting lots of different topologies. You put a topology discrete topology cross discrete topologies discrete the codominious discrete, but any function from a discrete topology to any other space is always always what continues. Similarly, indiscreet indiscreet to indiscreet any function into an indiscreet space is also continued. So, out of this discrete topology is not so, it is interesting we have already done one of them namely action of a discrete discrete group on a set and so on. But the latter is namely indiscreet topology is most interesting one we will never have an occasion to use that one ok. But what may one what may you know trigger some thought process here is that these two extremities are there right. They are both topological groups without change a group. So, you you may think that topological groups after all have no special properties at all. A topology for a topological group may not have no extra properties at all. If at all there are properties it must be because of the group theory you may see wait a minute that is not the case. So, we are going to prove something out of this maybe you you may think it is nothing ok. So, not all topologies on a topological group even if you change the group structure maybe will be topological groups. So, we will see such things. So, that being the abstract part let us come back to some reality namely genuine and useful examples. The real numbers, complex numbers these were the motivating examples for them for us for this abstract definition right along with standard addition and standard you know if you take non-zero complex number there is multiplication also they are all topological groups right. The complex numbers of unit length they form a closed subgroup of the respective multiplication topological groups complex or real numbers ok. If take unit length of real number they are just minus 1 plus 1 that is some group. Similarly, the circle ok unit circle is a subgroup of the non-zero complex numbers under manipulation ok. So, these are the easy examples any finite dimension vector space over k is also a topological group. I am only looking at the addition the scalar multiplication is there we will study them little later. Similarly, our example namely I told you about Panak spaces the set of all bounded functions on x taking values in either r or c ok that was a Banak algebra right. So, there the addition will be automatically continuous with respect to the topology induced by the norm the norm is supremum norm ok. One of the most interesting case of all these topological groups occur inside the matrix matrices of you know n cross and matrices addition there already makes it a topological group ok. Even the multiplication just like the in the case of complex number central number of course you have to throw away the 0 the 0 matrix right. Not only 0 matrix you have to throw away this time you have to throw a lot more namely all matrices of determinant not equal to 0 determinant equal to 0 you have to throw away. So, in other words you have to take only invertible n cross n matrices invertibility with respect to multiplication. So, that will form a group and the group laws are continuous. How do you take inverse of a of an invertible matrix n cross n matrix? So, each entry will be a polynomial namely the ijth j ith cofactor divided by the determinant. So, it is polynomial divided by polynomial, but the denominator is non-zero therefore, they are continuous ok. So, glnk forms a what a group and the group laws are continuous with respect to what? With respect to the euclidean topology there glnk is an open subset of all k k you know n cross n I have written which I have told you earlier namely you write it as you know n cross n vector you think of that as n cross n vector. So, that way you get a euclidean topology on that ok. Similarly, you can look at o n which is defined as all those matrices real matrices ok. So, set A A transpose is identity. If you take complex matrices and then take A A star namely conjugate transpose right A A star that is equal to identity that will be called the unitary group. So, verification that their groups is easier it is linear algebra matrix theory. The only missing thing was why the group multiplications are continuous. You can separately verify that A comma B going to AB is continuous by looking at the matrix entries of this product they are all polynomials. Then you have to look at whenever this is invertible then how to write the inverse. So, for writing the inverse you have the Kramer's rule which says take the adjoint matrix which is again each entry is a polynomial in the original one. Then each entry you have to divide by the determinant of the given polynomial given matrix. So, that is also another polynomial right.  They have various subgroups I have denoted only two of them here o n and s u n here. Then you can take groups with determinant one also here. They will also form another subgroup smaller subgroup and so on. So, these are groups and many, many other groups are you know central to a lot of mathematics and there are theories here a small aspect of this you can call them as matrix groups which will lead to what are called as later on a deep theory very beautiful theory lead groups which we will not be able to do. So, let us stop here and take up these discussions next time. Thank you.


Heroes basketball postseason section 8-3. Abel Midgey at Little Falls, first half, all Lumberjacks. Allison Beard finds Elaine, all the way to the bucket for the easy lane. They go up six, and later Kennedy Mills. The home run ball to Clarissa Whalen, who will put it up and in. Midgey's lead is up to nine, and finally, how about some Lindsay Hildenbrand from the wing? This'll rattle home. Lumberjacks go up by double figures. Impressive win for them. They get the upset on the road. 62-35. Alexandria is up next. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


There is substantial empirical evidence showing that cheap federal loans are actually a major cause of the rise in college tuition, which has outpaced the growing cost of even medical care and housing. This theory was famously argued in a 1987 New York Times op-ed by then-Secretary of Education William Bennett, who wrote that, increases in financial aid in recent years have enabled colleges and universities blithely to raise their tuition, confident that federal loan subsidies would help cushion the increase. When you give people more money to pay for something, prices tend to go up, and forgiving debt makes the problem worse.


Let's jump straight into it. Right, let's start integrating this. And no suggestions from GitHub. For the wavered denoising, the universal threshold is used here. 0.5 asterisk mp, sqrt, 2 asterisk mp.log, then egundascoredata. This is just one of many thresholding techniques you can use for denoising. You might want to adjust this or offer multiple options. That should be fine. The wavered used for decomposition, wavered transform, is directly obtained from the client request. You should ensure that this is a valid waver type supported by pywt, eg db1, db2, r, etc. This sounds legit, what else? While it's generating. The level parameter is also directly obtained from the client request. Again, you should ensure that this is a valid value. Too large a value might result in an error or undesired behavior. If you wish to use wavered coefficients for other analyses or visualizations, you can extend the code accordingly. The above example just applies denoising. Yeah, we also have the outputs. I'm sure it's the correct MID, yes. Right, so I want to do some error checking first. Absolutely. Validating the input is crucial. You can achieve this by checking if the provided wavered transform is in a list of wavered supported by pywt. If it's not, you can send an appropriate error response to the client. Let's pop this. Okay, we do get an error. This is not the type of error I was expecting. Do we get it? Even if I remove this? No. Okay, can we print out this list? Why copilot doesn't want to work? Is that doing something? All right. We can just do that, can you? Right, this is the list. Okay, we need to adjust this dropdown. Do they actually have names? Let's pop it back into GPT. The list you've provided appears to be the wavered name supported by pywt, and the log entry suggests that a request was made with an unsupported wavered transform value, uwt. Are any of them legit? No. Given this, it seems that the validation code is working correctly. So when provided with an unsupported wavered, uwt, the server responded with a 400 bad request. Yeah, that's fine. If you're looking to improve the error message for the client, you might want to include the list of valid wavers in your error response. Oh, but how do we take this HTML bit? And we update this. Wait a second. So those are actually the correct responses, isn't it? The wt, no. We want to update this with the valid wavelets. Let me create that. Run this. This is the valid wavelets. Shall you understand the context? Okay, updating the value, this value. It's not a valid value. Or is it okay? Okay, let's try this. It should be updated. It's not giving an error now. Okay, we might add more later. Should we do it now? Because we'll forget later, won't we? Okay, give me the DB3. Yeah, there's a good feeling of that. Okay, let's just add four. That should be enough. Okay, you know what to do, don't you? It's the same two. Yes. Right, it's enough.  Why aren't you doing it by yourself? Is this... Ah, there is no 1.2, so thank you for that. Yeah, there's 1.1, 1.3, 1.5. And 2.2. Okay, we'll leave it there for now. Oops, get this. We need another input for... Let me check. Let's make this one default HTML. Okay, how do we do this? Selfie. Yeah, Github, co-pilot. It's either I don't know how to use it or it's absolutely hopeless. Hey, one sec, what are we doing? I missed this one. Well, having a problem, can we make an option? Can't spell. Yeah, Github, co-pilot can learn from JGBT how to modify code. Yeah, just need to add the word selected there. So, now we have db1 as default. Obviously, this should change the signal. Okay, this stopped working. Okay, what's up? I think I had this error before. How to fix... Can you fix this? I saved this file as moment was the last change. So, this line is doing what? Yeah, what do I have to do? So, line 87 is not indicating any problem. Just restart the thing. It's working okay. When I hit wavelet in noise, I get this error only when selecting wavelet in noise is on. And this is the error. Can you give me more specific answer? Yeah, if wavelet in noise is over there, what's the problem? Yeah, it doesn't have an else function. Let's try co-pilot is doing something. Let's do some manual printing coefficients. Why? Okay, error handling is good. Okay, let's do some more error handling. Okay, so instead of... Oops, okay, right. Okay, now the app is having an error. Don't have else yet. Okay, so this is running. Okay, so this is running okay. Why is this not sending this... What am I doing wrong? What am I doing wrong? If wavelet in noise is just be reverse, multi-level discrete wavelet transform. Yeah, this doesn't make any sense. To fix a code. Sorry, no super long prompt. I'll probably get a timeout soon, but I'm just trying to understand what's going on. Okay, so we have this. Right, so this should come first. Yeah, I don't want any comments like that to... It's obvious that that's the continuation of the code. Where is if... Do we have if the trend? We do. Okay, now I'm really confused. Yeah, that's just checking for NANDs. So we should go e.g. data and the trend, if necessary, then removing check for NANDs. And then weather denoising rest of the code. Okay, let's try this. So we're starting the thing. It's refresh. This is working. Okay, that's working. And it's actually doing something. So it's removing some noise. This is actually only useful up to a very limited point. Okay, let's reduce the window size. Yeah, so you can see the noise reduction there. So yeah, check gpt4. It does know something about the e.g. It's a particularly noisy channel. This is the trending. This filter orders only. Yeah, we need to restructure the whole thing. We could actually just try this again. So on the larger screen, ideally everything will be set from left to right. On the smaller screen, on the tablet or phone. Yeah, it's obviously we'll have to go top to bottom. But otherwise it's actually working. It's actually doing something useful. So next thing we'll be patching it up a bit and publishing on the side. So it will go instead of this one here. We'll probably put it up top there. So it will eventually look at least as good as this one. If not, it should be much better. So hopefully you'll be able to test it yourself. Yes, this levels in html should be limited. Levels value should have a mean and max like that. It equal, well, would zero just be the same as having it off? Let's make it five and default about two. Yeah, there's not much difference between the different weather types. Now the other thing is when I change the frequency spectrum is updating as well. It's good. It's changing by the role. The question is this is working. Now with no errors. The effect of the wasting is not very clear. Let's see what it says. Maybe it knows way more than I do. Okay, that looks sounds very interesting. Can you give me the details? Should I have it as an input? Wow, you're so smart. Let's add a multiplier. We might continue this next time. But yes, we made quite a bit of progress. But you know, it actually works. I assume this number should be between zero and one. Yeah, the original thing was 0.5.


What's up everybody? Jason here for jaspyscasebrakes.com. Last break of the night 2020 Panini Immaculate Football 2 box break. Picketing number three These are the last two boxes of the case and here we go guys looking to pull a big rookie quarterback patch auto here potentially hopefully and Christopher getting the Dolphins last-ball mojo And here's everybody else So good luck everybody You're in this break. All right, so here are the last two boxes and again. I marked them The last two boxes remaining All right you guys good luck Von Miller out of 60 Broncos going to Joshua You got a little jumbo 20-door set out of 49 You got right here for the bangles T Higgins nice little patches here five out of ten Cincinnati bangles going to Demetrius a little Super Bowl autographs of Cam Chancellor They go Seahawks with that one. Seattle Seahawks. That is Matt Joe Thysman 24 to 49 Washington football team.  I have no idea what rookie reserve brand logo is That'll be a blockchain So Rookie reserve brand logo card number 15 will be out of three This is a blockchain of course all digital, but still very nice there for the Minnesota Vikings went to Jeremy S Definitely wonder what that's gonna look like All right, last box guys good luck. Should he be it's white out of 60 We got Adam Thielen I Little quad patches and it's to a toggle by low at 12 out of 49 Very nice Mommy dog mommy dolphins that is a Christopher Las Palmo Joe We got Marlon Mack little jumbo patch and autograph five out of ten I feel like the Colts if I'm so great the whole case We got ourselves a rendez-barber Six out of 99 little player collections triple relic and auto The pack straight down the middle and the last one is a rookie patch autograph It is a quarterback and it is gonna go to the Packers 65 out of 75 J hard Jordan love and Packers is Ryan Harold There you go the future and there you go guys. I was a man of the football little two box break Right here some nice stuff. So appreciate it guys Jaspies case breaks calm


are we live yep yes all right so maybe I'll give you words here first of all we're the last stop before the party so hopefully you can hang up and stick with us the the talk was actually was was supposed to be driven by Barack who is for because of a family agency couldn't be here so after picked up after our product manager picked up the challenge and learn a new presentation in less than a day so we'll try to do our best to actually substitute Barack and and cover his talk we're kind of an intimate forum here so I wanted to ask a question first before we kick that off how many people here are actually consumer of open stock raise their hand majority of them how many are developing products for open stock all right and there is a reason why I asked that because I think the challenges that we're gonna talk in this talk I think is very relevant to those who are developing products on open stock which tends to you know test and put open stock in a point in which it actually stresses it much more obviously you need to deliver a product that works in various scenarios and not for a particular organization or user and and you'll hear a lot about our experience our experience meaning gigs faces and cloudify specifically what is the journey that a product company that wants to develop a product into open stock how do we actually do that what was the choice of infrastructure that we've gone through over the years and we're talking about three four years now of a journey what worked what didn't work and then we'll try to also kind of get to the bottom line of that by all means a lot of that experience is our experience because of the way we run the product and the way we need to develop it it doesn't necessarily mean that you know all the lessons and all the experience that we've gonna present here and talk about is the same experience that you would have gone through there is no intent here to also bash any product here or do any comparison that says this product is better than other products really talking about from a really really personal experience and try to share our experience and and give you the lessons that we've learned over the course of years nothing more than that I would like it to be an interactive session so if you have questions and if you especially those are also coming from a product company that wants to challenge some of the lessons please do that the the whole idea is that it will be interactive and if we could make it in interactive especially again in this type of form that will be I think more entertaining for the rest of the people here so with that I wanted to give the mic to Arthur thank you right so first of all this is the Nati Shalom our CTO of Gigaspaces at the company behind Cloudify and I'm the product manager for Cloudify by Gigaspaces so we're going to do a quick introduction on what we do with Cloudify just to set the ground and set the stage on on on the types of interactions we are doing with OpenStack and our experience with that and we're gonna like quickly cover like private versus a public cloud discussion on in which types of cloud should you use when you're developing your own product and the clouds that we've been experienced with and where we ended up and what's our path forward so and just to set the ground Cloudify is a cloud orchestration platform you know just to get the jits of what Cloudify does it takes an application topology in a blueprint format and then basically works with the various APIs to realize that application blueprint obviously that's super simplified explanation of that but essentially Cloudify works a lot with the OpenStack APIs to bring up the amps to bring up networks connect to connect to everything that's that's involved in that and basically stresses OpenStack APIs a lot. So Gigaspaces started working with OpenStack at the SX release and basically ever since OpenStack has been the main path for developing Cloudify. So yeah that's the quick intro and as I mentioned the one thing we've realized is that Cloudify breaks OpenStack quite often and quite a lot and as I'm not to mention the main point of this discussion is not you know bash one one OpenStack distro or the other vendor rather to to basically take take us through the path that we've been going through with Gigaspaces and and and basically share our experiences and where we ended up and where we would like to go forward I would hope to go forward and nothing mentioned earlier that's that's I picked up this talk kind of in the last minute and the main reason I try to avoid this tag because I'm ex redhatter as part of the product team for for OpenStack so I don't feel too comfortable doing this talk specifically but interestingly enough and actually the slides were done by Barack they're kind of like interestingly put so I should be fine. All right so we started off by using by going to the to the approach of working with a private on-premise cloud basically bring it up OpenStack internally in our own IT environment and actually that was not not not really a blocker to work in public clouds you know we work with public public clouds a lot. Cloudify works with AWS with Azure and then almost every public cloud out there but we focus mostly on the private cloud due to some security reasons first of all and in the public cloud and when we worked on the public clouds basically we experienced some some some breaks and into the environment and some weird things that were going on that once we've started investigating we've realized we had some DDoS attacks some breakings into our own environment and you know working behind the firewall definitely definitely has its benefits even that you know the workloads that we run there are not you know real production workloads rather are in the infrastructure but still it would you know it's much much nicer to have an environment that you full control and second reason we focused on on private cloud initially was that fixed cost so whenever we work in a public cloud we're charged basically by the hour and the way cloudify works is it orchestrates you know different types of topologies different types of applications and basically brings up a lot of a lot of VMs it needs them like for a minute or couple of minutes and then tears them down so the price model of charging based on the hour per VM or per resource that you work so that you consume from the cloud basically blows up the costs of the overall of the of the overall R&D budget that we were hoping to achieve so going to the private cloud in the in the environment that we're trying to work actually worked a bit better for us a thirdly bandwidth so when we when you basically debug issues and you have huge huge log files and huge core dumps from the environment you pretty much would like to have a pretty good bandwidth to pull data to investigate data and you want to have a better access to those machines when working with large large quantity of data that you need to understand what's going on there and obviously multi-tendency and have better better control of which operations are allowed which operations are not allowed etc so public clouds tend to be more strict about that where in private clouds you're basically can configure whatever is works better for you so the first thing we did was go to DevStack obviously you know that's the first go to a go to a solution for developers and it's very easy to set up and then you know basically showcases what cloud what what OpenStack can do but it's not production great so once you set up DevStack usually it's a specific environment very different from customers actually are doing and you know when you work on a product that works with APIs it's it's really important to work with the same architecture as the customers are doing so working with with DevStack actually was quite limiting for us and like we realized pretty quickly that that it's nice to play around with it's nice to figure out how to work with OpenStack but to really build solutions it's it's quite challenging so the next step was to go to the do-it-yourself approach and install OpenStack so how many of you actually installed OpenStack themselves right pretty good set of hands in here how many of you actually read the documentation the installation guide for that how many enjoying the length of that guide so sorry you thought you should belong and how many pages do you think that guy is it's so so we download actually PDF and like went over all the installation guy and it's 164 pages long back in the day at least it was so you have to like read 160 something pages just to get started so I cannot believe it at this point I'm still showing this like super complex diagram of OpenStack architecture and still relevant and but but yeah so you know started with Grizzly and the architecture is super complex we had to go over all the services reconfigure them do it everything manually and it did work after a lot a lot a lot of effort and then it broke pretty quickly so we didn't actually like investigate on why realized we needed some more expertise in the house and so we did a sexto course by by Thorian has which was really good so that actually gave some background on the how OpenStack works all the internal services what's needed to be done in order to for for set up an environment that actually runs for more than two minutes and we installed the basically OpenStack in-house using some puppet puppet puppet scripts to bring that up and everything just started fine and then networking just stopped working randomly I think that was around the fall some release so VMs once VM started continued working but sometimes you know we had many like weird issues when the VM would bring up would come up without networking other issues when when we had networking but no DHCP other times DHCP was available but suddenly the VMs lost connectivity so we had lots of like weird weird scenarios where networking just was really not working well so at that point we realized we probably needed to work with one of the distros so Ubuntu was was really no brainer at the time it was one of the main paths on the OpenStack main documentation and pretty well documented bit easier to use the packaging at least from the commutation it seemed and then they do it yourself approach and the experience there that back in the day and this is you know 2014 couple of years back from now but we couldn't get it working with Juju so tried installing it tried getting up in the air but put a lot of efforts to bring that environment up and essentially couldn't get working and gave up after a couple of weeks so that was a bit disappointing and sort of saying next we've tried Mirantis's fuel to bring up OpenStack and that was also back at the day and that also did not work quite quite well so we did a lot of you know work and effort and actually actually ask questions around that but again back in the day it was really challenging and then we couldn't bring it up and to note that the first installation worked fluently when it was basically running in few minutes or few hours actually to get started with and the first few days was actually very good but once we broke it it was almost impossible to recover from that point and that's I think where it stopped working again I think that a lot of that had to do with the networking piece with Neutron specifically because in our test what we do is we create networks and destroy them and create and destroy them and that wasn't a stable part of the API OpenStack API and I think that was kind of the reasons why it got to that crash mode. Yeah and like one point one thing which is super important to stress back at the day it was really really challenging to debug to debug Neutron so you install Neutron you install the agents you bring up everything that you should be bringing up you look at the logs and it's really not clear on what's going on why the network is fail why do you don't have networking you know essentially everything works all the services are up in the air but it's really back at least it was much harder to debug than it is today I believe or hope to believe. I think it's also I think indicative on the state of OpenStack at the time I think there was a lot of lack of maturity and how OpenStack has been developed and what you would see in that journey is also kind of indication of the maturity that happens to OpenStack itself in the sense that you know I believe that you know the fact that we were running into that meaning that no one was actually testing a use case of creating and destroying things all the time to get it to the point of stability and that created a lot of timing issues and a lot of things that the distro couldn't solve because obviously it's a core issues within the OpenStack itself and that manifested in the distro itself and the distro tried to make the experience simple but at the end of the day if you hit a problem in the core OpenStack the distro didn't really solve that. Yeah and actually this kind of brings me back you know back to my redhead days where I used to work a lot with the OpenSort with the upstream community developers and you know working with the various Neutron teams developing Neutron itself and all the subcomponents and you know the kind of issues that you know I've been working around back in the day were like really trivial sort of like you would have expected it to be in but simply was not in so services would go down without any login or debugging messages so you know one thing to important to stress that you know back at the day OpenStack was much less stable and it's not specifically probably not specifically around this issue rather a general OpenStack upstream issue that you know simply Neutron was not stable and mature enough. So redhead days and this is back to the back to the Cloudify gigaspaces effort so the R&D team brought up RDO redhead's distro and the redhead's community distro using PackStack so that was rather simple to bring up you know simple simple CLI wrapper around the puppet modules to configure and bring up rather the same setup of OpenStack a couple weeks to install after all the investigation research understanding which configuration files needed to be like how the confile should be set up in order to bring up a multi-node environment with dedicated Neutron node and essentially glory days that was the title that Barack put here definitely this specific setup was up and running for quite a long time actually several months and you know because of the maturity we got we got we felt around this environment and this deployment and we felt we felt really secure really really really confident about about this deployment and started bringing workloads into it so you know initially we started that we tried to bring up some some CI workloads then we relied on that CI environment actually to build Cloudify itself and we started moving some some not real production but some IT workloads we needed into OpenStack and you know started feeling really confident about the environment and used this environment for the day-to-day R&D operations so if a developer needed a VM to do some research to do some some development some component needed on-demand resources and we used this OpenStack environment for these kinds of things and there's a big but there on the slide so you can assume what happens next so yeah so Cloudify obviously started breaking after several months of working rather smoothly Cloudify again started breaking OpenStack with various again networking issues so there was no DHCP suddenly suddenly at certain load neutral server would fail no connectivity to the ends and you know this is a screenshot of cases we've opened with Red Hat asking you know various things on how things work or how should be reconfigured most cases we got fixes for other cases we needed to do some reconfiguration different kinds of issues that we didn't actually have solution for so it was quite quite challenging after that period of time one of the challenges in developing OpenStack is that it's open it's developing an OpenStack sorry in an open source community that is not necessarily running a cloud unlike Amazon for example or other clouds and and that's challenging because a lot of the issues that we're discussing here right now for example making it stable over time that's not something that as a developer you could run and test easily you actually have to run it in a production type of environment for a long time to actually experience a lot of those problems and and get them manifested and in the open source community and the way OpenStack is being developed it actually comes back to the developers after the fact and in a way that it's almost hard to reproduce and not suddenly even get to the community it gets to read it and somehow indirectly it gets to the community which kind of shows one of the problem of the process itself the process of developing something like a cloud infrastructure in an open source type of environment which is good for certain things but it's more challenging when it becomes to something like a cloud in itself I think that's kind of the the interesting output from that. Yeah and actually like one another very interesting comment that this brings to mind is you have to have OpenStack expertise because if you rely on external expertise it's very challenging to keep this environment up and running and the real challenge here when you are an R&D organization working on your own product obviously your R&D or in your like most of your expertise are around your specific product so it's really like you know challenging to put some resources that would really understand OpenStack and then bring these types of expertise into your own R&D environment in order for you know to keep maintaining the environment but also bringing these expertise into the product itself so expertise are definitely key aspect when considering going into OpenStack and using OpenStack and developing against OpenStack in general. Right so skip a couple months forward after this environment started becoming unstable and the aftermath again we had too many errors and too much effort into fixing the errors in that environment and again essentially we gave up on this specific environment yet again and started looking for a different approach that would probably better fit our expertise with OpenStack. So then we went back to Mirantis and tried Mirantis Express so Mirantis Express is a hosted private cloud and it seemed like a very good option because it actually did not require too much resources from our hand to maintain and bring to bring up maintain install configure and then fix this environment. Maybe not too many people knows what is Mirantis Express. Yeah so Mirantis Express is a hosted private cloud solution basically providing you the infrastructure needed to set up and everything is needed to set up OpenStack and that is a hosted environment so that's not on-premise but that's not but also does not have like the downsides of a public cloud so essentially you get a set of servers and they set up OpenStack on top of that and help you maintaining that environment. So our experience with that was pretty good it was a quite a quick installation so we were up and running in quite a few hours in that environment and started moving workloads into that environment and you know gave our R&D members permissions and access to that environment they started working running workloads there and everything seems rather fine for quite a long period but again you have their current theme of a but on the end of the slide. Cloudify started breaking this environment as well and also we had quite a lot of issues we open with Mirantis some of them are specific some of them are very you know the issues that existed upstream in OpenStack itself some of them are configuration things that we needed to accomplish in order to get things going. So Cloudify definitely breaks OpenStack again is a nice and nice logo there and I think that again it's we're hitting a lot of those issues of that are result of creating and destroying creating of destroying environments and in that specific case we brought that environment to a point in which it was unrecoverable and so the only way to go around that it was to wipe up the entire thing and to create a new accounts and whatever which kind of brought us to a point in which we realized that that's not the right path. So next was public cloud back to public cloud again we reached a conclusion you know where you have an OpenStack of your own you're probably gonna get gonna get less attention to it from the experts because you forgot to mention that we're probably the only user of the HP OpenStack. Oh yeah. So we're the one. Up until the end the soaring end of moving all the resources from there into into our own environment. Yeah so back to public cloud so we started moving we started testing data data center so data center is a OpenStack based public cloud offering they're based out of the UK so you know distance wise it was quite okay and bandwidth what was was quite well to our offices in Israel and we started doing a lot of tests against it started working giving more and more access to to our developers to that environment and their environment was running a quite well quite stable environment you know compared to compared to what we've experienced beforehand and so something to be said about experts so definitely you know that was quite a different experience from everything else that you experienced so far until the fully public cloud offering so you know letting the handle the experts handle it and when you have like guys that are solely focused on maintaining and keeping a specific environment up and running as a production environment definitely made a huge difference you know compared to things we've experienced beforehand where we actually had to maintain the environment or we were relying on a small team that are probably were focused on several environments so quite a difference there and there's a still but on the on the presentation there and claudify did not break this environment entirely but we did have some weird experiences mostly around keystone and the and the load we were putting on keystone apparently keystone was not expecting to to handle such loads as claudify created so and there were some configuration changes they did and the day center did in in in their public offering to better support keystone and some may kiss some a quarter changes needed to be done at for for claudify to work well with with data centered so so definitely claudify breaks open stack a lot and I think you know this also brings some value back to open stack itself where you know these issues that we've encountered you know hopefully and hopefully are you know getting fixed and definitely you know as we go along with time where we're seeing that some of the issues that we've been encountering actually we're encountering them much less and less which you know kind of tells us that these kinds of things are getting fixed and these kinds of issues you know whether they're coming directly from community or from a vendor are getting attention and are getting fixed so open stack definitely you know gets more and more stable as time progresses and it's actually the data centered solution you know works quite well how many people here are familiar with platform 9 okay only few so I'll say a few words about what's the concept behind platform 9 platform 9 basically have a very interesting concept that we like a lot which is that the management gear if you like of open stack is hosted but the actual resources are on your premises or on your own if you'd like a cloud it could be also a public cloud and you install an agent and that's it so it provides a very simple way to run open stack and it takes a lot of the bear but still keeps the benefit of having relatively high control as opposed to a public cloud for example and I think that's we're actually the first beta or one of the first beta to actually try platform 9 so a lot of experience was part of that and unfortunately really unfortunately we couldn't really get past the point of setting up platform 9 under our environment after we investigated that I think it was to do with the with the data center that we had and the devices that we had the type of devices that we had and I think when we'll get to the lessons one thing that I think needs to be clear is that it's very hard to get open stack to run on all kind of environments and all permutation and all configurations it's probably not gonna work and so when you're picking on a platform you better know what is the recommended environment what is the recommended hardware gears that you have to have to actually make it run that is tested that you know that will run and in this specific configuration it didn't work we don't necessarily know why it didn't work we just know that it didn't work then we kind of passed to the next level yeah so talking specifically to platform 9 you know initially it seems like best of both worlds so you have all the servers in your data center next to you and the manager the controllers are basically managed as a service by platform 9 which is you know perfect right they managed they maintained the whole environment itself and the workloads themselves are really close on prem and actually like we do have some level of knowledge on what went wrong there so and the point where we started playing around with with platform 9 was where where they entered as what they introduced neutron as a beta feature and we really needed neutron and some specific features from neutron and very specific villain configurations needed to be supported from our hand by neutron so so that was a really a blocker for us to test neutron test the platform 9 and you know we definitely do hope to to try that again and hope that it would work in the next iteration because it does seem like promising the best of everything we need as an R&D but also but also like providing the stability without paying the costs sort of say of maintaining a production open stack environment so we're gonna talk a bit about rock space yeah so the next the next level was to go private hosted as you can see we almost tried every option on earth of using open stack so private hosted give you the benefit of someone else you basically outsourcing the responsibility of managing open stack to someone else and all the issues that we experienced we're hoping that someone else will experience or at least will be able to complain to him and he will fix it and and that's kind of the path in which we're pursuing right now that seems to be the most promising until the next open stack summit and and and again again I think that from at least a skillset perspective we expected to run better now it's also hosted in a local operator so the latency issue is not going to end the security issue and then we had we're accessing it through VPC kind of connections so we have secured access to that environment and we have full control over the infrastructure itself so it's supposedly going to be much more stable from our experience so far it looks very promising and still very promising yeah so definitely hope that this would work out next so yeah so so I think that if I kind of try to touch on that and there is other kind of guys here that are doing products on top of open stacks I want to hear your lessons and what are the type of environment that you've ended up working with if you ended up working with is that first of all I think that we can see that there is a lot of options to run open stack there is we started with Dev stack you could run open stack with distro without distro in a specific infrastructure without a specific infrastructure in a semi-hosted like in the case of platform 9 there is option to run it as a service but still private service like in the case of open stack express and there's also the option to run it on a private hosted environment so first and I think that's kind of an indicative of also a problem that you know there was no clear blueprints that says this is how you run open stack and this is how it's going to work I think that only now in the past I think last time it was so there is this type of blueprint that says okay it's probably not going to work if you're going to run open stack and expect it to run on all options and everyone going to bring its own gears and it's going to work and so the vendors itself and the distro themselves are getting to the point in which they don't just give you a distro they're telling you how to run it and which type of infrastructure including appliances themselves so I think first lesson is that don't try to run open stack yourself second if you're picking up and that's your business and for definitely for a product company even though we need an intimate knowledge of open stack that's not where we want to waste our time and we do we need to do other things as well the second part is that between a distro and a private hosted it's really a questions of where you feel more comfortable the if you need the benefit of a distro is obviously is that the installation is simpler but you still need to manage it and a private hosted you're also seeing that hosting environment the problem with hosted version is that it's if you need to run multiple versions of open stack it's harder to deal with that because then it's all outsourced to someone else and if you want a release cycle and you're saying that I need to now run a new version of open stack that's not going to be that possible so you probably still need to have some sort of flexibility somewhere else there is another option that wasn't mentioned here that we're actually using right now when we announced for example an NFV lab this week which is ravello which had really allowed us to create that type of POC environment on demand so whenever we we need to get to a customer engagement one of the problem that we had is that we needed to create a private environment for a specific case for specific POCs and running it whether it's in public or a distro or hosted is not going to be possible definitely if you want to share it with another user so we ended up using that so the result that we have today is that we are actually running some workload definitely the scalability on a public cloud data centered and we're going to continue to do that we have basically the hosted private cloud that we are running in open stack in the rack space and that's for the continuous if you'd like development that's for the most fixed workload type of testing and we're also using if you'd like some portion of open stack as I mentioned on the ravello environment to actually run a POC environment that we're using so we're using multiple options or from from the list and there is no one open stack that we're using that covers all of our use cases right now and that's where we ended up and I think that's kind of the the point maybe to open the mic to people here in the room who is developing a product on open stack I think there were a few don't be shy now there was at least 50 percent of the room so yeah exactly yes okay so you're from emc okay so obviously you're running on your own gears what's that okay ourselves if those guys will touch who else is developing products on open stack so what kind of products you work on guys yes there's someone there's someone brave yeah I'm from Nokia and we're developing a very similar product or at least we have been developing it for some years and we speak up a little bit yeah we encountered whatever we encountered very same issues as you did so for example the floating IP not reaching the the VM and fortunately we do not have to run it in production it's it's for the bad guys and and for our CI systems it was enough that we created several development crowds and whenever it broke we just scraped it and changed the CI to use another one yep that's the best option yeah destroy and create it from scratch excellent thanks who else yes so I work with we work with 40 net we're a next-gen firewall provider and hardware and I'm just wondering you ran into a lot of problems with Neutron and the networking piece it seems like there was a consistent theme through all that yep you know a lot of our customers are wanting us to to go virtual with these high-speed platform UTM next-gen features but what's your opinion on is that really there yet is that a need for that or did you guys find turning your networking services over to hardware ultimately this was a better fit so the question is should the recommendation would be to go with the virtualized network or hardware well a lot of your you just mentioned Neutron kept yelling on you so what did you guys do did you ultimately just end up going to hardware for all your networking or did you guys figure a way around that so I think it depends on what kind of product are trying to develop you know in our example cloudify needs to orchestrate networking as well so Neutron is very important to us and very important to us to have full control over how Neutron works so this is why we didn't look into the approach of you know having a physical specific setup of networking that would be you know very very very hardwired but if your business is around you know focusing on on cinder volumes for example or on VM specifically not you know and not bound into the solution to networking probably like going to the hardware approach would be would be the better the better choice there but I think that to your question a lot of our customers the enterprise customers specifically and also the carriers I know do choose their own if you like hardware network gear that is not the default one that comes with OpenStack and that's that's for the reason that I think a lot of the people in the room here are pretty familiar with that Neutron at least in its current in coronation is not stable yes I work for Rackspace so are you guys using RPC like the our private cloud stuff yes it is the private cloud stuff but it's the private hosted so it's we're not using it directly we're using it right right we're doing the ops types yes exactly using it indirectly so on the back end for us it is by default going to be just plain Neutron with Linux bridge and if that's working for you and then at least right now yeah so you probably did yeah we recognize that OBS kind of breaks and Linux bridge though is pretty stable and doesn't like to reset on anything like the level three stuff getting restarted was an issue yeah that's yeah I think that's a fairly that's a very good comment you know every every choice has its own you know advantages and setbacks so you know obviously it has less control so you have less things less less less types of configurations you can support but definitely that's more stable so that's the trade-off but yeah and and I think it continuously runs over time that's in itself will continue to be an issue especially when you develop new features and new services so that means that basically the maturity cycle is going to be longer as we've experienced with OpenStack so I think that's remain the major problem I think at OpenStack is that it does get stable and we are getting into production and I think now with the fifth release we're in in 50 years we're actually getting to the point in which we could see a lot of production workload but the cycle is very very long and there is a lot of iterations and it takes a long time until things get matured I think that remains a problem that the community have to figure out and in my view the only way to do that is either standardize on a specific kind of gears that says this is how it's going to run and be very specific about it second so that you could even test it and know that what you're testing is what the customers are going to use and not pitch it as a general purpose thing that you know install it and it would work hopefully and the second part is that it needs to run over time and the feedback loop needs to be much shorter which means that there needs to be some sort of environment like obviously in the case of Amazon that those tests would even run for a long time and over time and manifest much faster into the development cycles of OpenStack itself and I think the fact that there is starting to be a new wave of public cloud of OpenStack I think is a good thing because in a way those are the guys that probably you know the rack space and data centered of the world would send those feedbacks and will contribute back or at least fix those type of long running issues that otherwise you wouldn't even see them so that's kind of the positive side of that anyone else wants to share his experience or his comment any additional questions maybe all right so we are not going to hold you anymore from the OpenStack official party unless we want to do it here all right thank you guys thank you guys thank you


This research examined the impact of interconnected transportation systems on the resilience of public transit in Hong Kong. It found that interconnected systems can reduce topological vulnerabilities, increase attack tolerance, and enhance post-disruption interoperability. Additionally, it showed how integrating vulnerable systems can further strengthen resilience. Finally, this paper demonstrated the potential to integrate different modes of transportation for greater robustness. Overall, this research suggests that interconnected transportation systems are a viable option for enhancing resilience in cities. This article was authored by Zixian Xu and Shorat S Chopra.


In this video we'll discuss if Mural is the right tool for your customer journey mapping project. Let the show begin. Hi, I'm Mark and welcome to the Server Design Show. In this video we'll talk about if Mural is a suitable tool for day-to-day use around customer journey mapping projects. If you haven't seen the first video where we created the basic structure of a customer journey map using Mural, check it out over here. At the end of the video I'll talk about some of the pros and cons that I found when using Mural for customer journey mapping but first let's dive in and I'll share my screen and show you some of the more advanced features that are I think essential for any tool that you'll want to use on a day-to-day basis to actually run customer journey mapping projects. So we're back in the map that we've created in the first video, the model of all maps, the basic structure of a customer journey map. If you have this you can expand it basically to anything you want and the first feature that I think is essential for any serious journey mapping tool that you want to use on a day-to-day basis is the ability to collaborate and share and luckily Mural has a very big pink button which says share and allows you to invite teammates and also people outside of your organization to see this map, edit it, collaborate on it and it even gives you the option if we click here on manage to define if somebody is able to export it, duplicate it, invite people so you can change a lot of settings around sharing. Sharing is really what is really well integrated in Mural so that's we can give all the points to Mural for the ability to share and collaborate on maps. So the next thing we'd want from a good journey mapping tool is the ability to change states in a map to indicate where things are changing because our journey map isn't a static image, it's not an artifact and end result, it's not a deliverable, it's like my friend Daniel Euroman says it's a change plan so we need to be able to indicate where things happen. Mural offers a few options to do that, we could for instance use border, the ability to change the borders like we could indicate that the dotted border indicates stages that we're working on or that they are in progress so we can use maybe background color that we want that this we need to remove this or this is work in progress or we could do something like add an icon which is over here maybe work let's see what it finds would work, hammer or I don't know yeah let's use a hammer for work in progress so there are a few ways that you could indicate states of cards which is really really important. Now the next thing that is really important for a good journey mapping tool is the ability to see version history revisions and the reason why you want to have revision history is when you're collaborating not if but when you're collaborating with other teammates you want to see what people have done how the map has evolved have people edit additional research insights that they promised they should do and did they actually log into to view the map so again this is really well baked in into mural they have this icon over here which shows activity and you see everything that has been done with the map and that it has been done by me so that's another win from mural this version history is really important especially when you're collaborating and it works now the final feature that I want to have in a journey mapping tool is the ability to export and again mural has a big button that says export we can we have a few options pdf png zip files let's do png and okay this might take a few minutes but it allows you to export your area of the map and this allows you to print it out put it on the wall then maybe two weeks later do another snapshot and put it on the wall and then see visually see what has changed in your map so this is really good so now let's dive into some of their pros and cons of mural that I found and the first thing the general a general remark is that mural is not a data dedicated journey mapping tool it's I consider it to be more of a online whiteboard you can do anything with it it's a blank canvas that allows you to um draw and add things that you need that's why they also offer a huge library of templates sort of canvases and mural is super flexible it can basically do what you need it to do it's a whiteboard at the same time this is sort of a disadvantage for you as a customer journey mapping pro because you don't you have to make the structure you need it doesn't guide you in any way there is a blueprint surface blueprint template but still you need to come up with what you need of course you can take this model of all map structure and use that as a styling point but for some people I can imagine that they would like to have a little bit more guidance and um yeah that's just not part of mural mural super flexible which is great but also might be a challenge there are two things uh a mural that make it hard for me to see it as a tool to use on a day-to-day basis uh focus on journey mapping and the two features are let's dive into my screen again um the first feature is imagine that we would want to add another card in between buy tickets and park the car so what we would have to do is we would have to select this card move it over to somewhere here then maybe add move this card over here and then move this card here and then you know you get the you have to do a lot of manual moving and resize this one it's possible uh but what if we decided to remove this one we need to sort of manually put everything back again this isn't a question if it will happen your map it isn't a static image it's a it's it's alive so it will change it will evolve and you need to be able to really quickly adapt and make changes it's possible on mural but it will take time and the more complex your map gets the more shoving and shuffling you'll have to do that's that's that yeah that's not really nice the other thing that makes it hard to use mural for more advanced journey mapping is that you don't really have the ability to add meta data in your lanes in your cards like i said we have the option to add comments this is already a thing but we can't add images in here we can't define what kind of comment this is and again this isn't a question if you want to add additional details to a card this is like you need to add additional details to your card and mural doesn't really offer that option at least it's the option it offers is really basic there are two things that i like about mural and that is the ability to collaborate and share they make it super easy to do that the version history is great super useful and the other thing that's a nice to have it's like the icon library and it's the image library that we talked about these could be useful depending on your needs but these two things are i think a plus and a win for mural so when would i recommend to use mural for your journey mapping projects well if you already have a license on mural and you're already using it you're familiar with the interface it allows you to pretty quickly digitize the results of a workshop that's that's where mural is pretty good for i wouldn't i don't i wouldn't see myself using this on a day-to-day basis after a project after a workshop because it mural makes it quite challenging it's quite challenging in mural that's a better way to phrase it to update the map and keep it alive so to make a snapshot to digitize your results of a workshop that's probably a pretty good use of mural if you're already using it if you want to use it on a day-to-day basis you really have to be dedicated and willing to manually shuffle things around but as with all these journey mapping tools my advice is just try them out give them a go and see if they fit your needs mural offers a 30 day free trial and i think the single user license is $12 a month so that's not huge you can easily jump in and just play around with it and see if it if it works for you i'll include the links to mural down below in the show notes if you have any questions about mural that i didn't cover in these two videos make sure to leave a comment and let's continue the conversation over there if you want to learn more about customer journey mapping and how to create maps that actually create an impact check out this playlist over here which is full of videos that are going to help you to do that thanks for watching and see you in the next video


I can't serve for life when you see why you call people like Corbyn or the modern socialists. Socialists, because they seem to be the antithesis of what socialism is about, which is a concern about human flourishing. So for example, Jeremy Corbyn hates economic growth. He doesn't like it if he thinks we can't grow our economies at 6, 7, 7 years like China, or even 100 or unlimited economic growth. And if you look back to the original socialists like Marx, what they loved about capitalism is that it grew. It produced wonders greater than the pyramids. Marx was totally infused. Marx was much smarter than a socialist in the socialist era. Yes, precisely. So the socialists today hate all the best parts of capitalism, which is a mistake. But the thing is that capitalism itself, I mean you talk about using one's reason, which is a core Enlightenment idea I grant you. And then you learn from your experience. But the thing about capitalism is that it grows and then it falls. It goes into regular crises. And that experience has shown that capitalism doesn't work. And at present you could even say capitalism is in a rot, in a crisis. We're not growing enough. So what the challenge we face today, I think, as if you would say socialist, is to harness our reason and knowledge of history to come up with an alternative to capitalism which produces human flourishing consistently. And what I think you're doing is giving up on human reason because you are actually accepting a system which you know by experience goes into crisis. And you're saying we should just accept it and not look beyond it. So that's my accusation. No, that's good. And it's a relatively original question. So that's good. One of the reasons to just go back to some of the comments you're making, I'll try to take them all.  I'm not in the business of deciding who is a true socialist and who is not. And because he exemplifies certain socialist characteristics like the nationalization of industries, the idea of putting the state as a central planner over industry, which is a typical socialist policy. No, I understand why you don't think he's a socialist. And that's fine. And I'm willing to accept elements of that. Let me just say, and I have to say this, I don't believe Marx for one second believed in human flourishing and strove towards human flourishing. I don't think that was his agenda. I don't think he believed it. I think generally Marx was a hater, not a lover, and not somebody who really embraced human flourishing. If you read his letters with angles, with its scribe, which people they can eliminate and which people they're good. He was one of the most racist angles in particular, but Marx, of course, endorsed all this.  But I'll give you this. Marx projected a system that it caused optimistic about the future. And I think many of today's left are not about the future and they're not about economic growth, they're not about human flourishing. They are essentially nihilist. And I think that is a characteristic of modern leftist ideology is nihilism. It's a post-Nichie and kind of a real nihilistic approach to life. And you can't accuse Marx, at least in that sense, of being a nihilist. I think the results of his ideology are nihilistic. But he at least projected an idea of one day we all come together as the Poletarian and live happy, successful, wonderful, prosperous, rich lives. And nobody today on the modern left actually projects that. I don't agree with you about capitalism completely. I think the evidence is quite to the contrary of what you suggest. Capitalism does not fail. There is no evidence that capitalism has failed. And I will take you crisis after crisis after crisis and show you that capitalism has not failed. And today, the sluggish economy of the world is driven by one major factor and that is statism. The lack of innovation, the lack of progress, the lack of economic growth today is a complete result of the growth of the state, of the fact that the state today. That spending is consumption. It is wasteful. Instead of that money being invested, that money returning to the hands of a capitalist, they can invest it. They can invest it in production, in job growth, in innovation, in creation, in building. So it is the exact rejection of the last 100 years of capitalism that has brought about the Great Depression, that brought about the 2008 crisis, that has brought about the slow economic growth we are experiencing today. And in China, China is a great example because I know a lot of people on the left, or I don't know if you can tell yourself on the left, but a lot of people who want an alternative to capitalism look at China and say, look, they are growing at these astounding rates and they are run by the Communist Party. Well, you have to go look and you have to go to China and actually look at where the growth has happened. The growth and the success of China happens where the Chinese government doesn't pay any attention. When the Chinese government has said, go do whatever you want, we are not going to look over there, we are not going to worry about you. That is where the economic growth, in other words, in the areas where there is a lot of individual freedom, individual innovation, in other words, for capitalism to flourish, those are the areas that have generated astronomical growth. Growth has been held back by the state-owned enterprises and by the central planning of the Chinese government. Every area where the Chinese government has centrally planned has been a disaster. Every area central government of China has embraced has not worked. And I don't know how much you know of the transition from 79 under Deng Cha Peng to today of Chinese economy, but it is absolutely fascinating. There is a wonderful little book called How China Became Capitalist. Now, I don't like the title because I don't think China is capitalist, but it's certainly not socialist. It's got elements of both, like all countries, but where it grows are those elements of capitalism. But it's a book by a Nobel Prize-winning economics by the name of Rana Kos and a Chinese author whose name I can't remember. Rana Kos was 101 years old when he wrote the book, so it's pretty astounding for that fact. But it's a short book, it's wonderful, it's not the best written book in the world, but it's got fantastic information on how that transformation happened. And I'll just give you one story about how China became so successful at growing food. In the 1960s, communal farms generated mass starvation. People died in the tens of millions during the 1960s. That's just an historical fact. Mao Tse Tung knew this and basically did nothing partially because he believed that this was a weaning out process of the week and so on. But also partially because this was a system they believed in communal farms and this is what it generated. Anyway, throughout the post-1960s, farming in China, farmers in China struggled and starved. There was real hunger in those communal farms all over China. And there's one little community in China. I forget the name of the village, but there's a little village in central China. They got together one day and they said, look, this is not working, we're dying. So let's do this.  And whatever you produce on that is yours and you get to keep the surplus and I'll get to keep the surplus here. And they basically divided all the land of the village communally owned into private or pseudo-private lots that individuals now cultivated, maintained and got the surplus from. And guess what happened? Within a year, they were producing massive surpluses. Suddenly, there was plenty not only to feed the village, but they were exporting to other villages.  What have you done? This is great. This is miraculous. We want to do this. And the farmers tried to hide it, but ultimately it came out what they done. And the immediate response of the Communist was, well, kill these people.  They're embracing capitalism. And to dump Chopin's credit, now that Chopin was a really bad guy, but he did some good things here and there. To dump Chopin's credit, he basically said, no. This works. He was a complete pragmatist. He said this works. So leave it alone. Not only that. If it works in this village, let's see if it works in another three villages. And they tried the same system in other three villages. And guess what? When you get people private ownership, they produce and they create surpluses. So they worked over there and they said, okay, we'll convert all of China's farming or most of China's farming to this model and that's what they did. Even though to this day they don't own a private property. They have what I call pseudo private property. They pretend that they own the land. The government still hasn't given them full rights over the land. So capitalism works. And I'm happy to explain a 2008 crisis and I'm happy to explain a Great Depression. But the fact is that when markets are left alone, they flourish and succeed. Even today, if you look at where innovation happens, where does innovation happen today? What industry? Innovations. Of all the industries out there. Where do you see 8, 9, 10, 12% growth in an industry? Which industry? Technology. Yeah, technology. This industry. Right? This industry happens to be the least regulated, the least controlled, the least government influence of all industries. So it grows. And it's left alone. And yeah, is there a bubble? So there's a bubble, but the bubble is self-correcting and immediately it goes afterwards. Right? There's a bubble in 99 and partially funded by the Federal Reserve, a non-capitalist organization, a very statist entity. But after 2001, it grows again. And we don't get innovation. Well, things like airplanes. We basically fly the same airplanes today as we did 50 years ago. Same engines, the same basic body. You know, they make them bigger a little bit and they use fiber or whatever, carbon fiber and stuff like that to make them lighter. But it's the same basic design as it was 50 years ago. Why? Because it's so heavily regulated. And the one innovation we used to have in airplanes was what? What was the one airplane that broke them all? The Concorde. We grounded that. That's gone. Nobody. I mean, there's one company in our building, a supersonic jet. We'll see if they let it fly. And the same with automobile, the internal combustion automobile. And the same with every industry where the state regulates. Call what we have today. Capitalism is bizarre. The mountains of regulation. The mountains of state control. The fact that for years at Microsoft, a government official used to sit to sign off on any deal they make. Or that today, when JPMorgan opens the door at 9 a.m. in the morning, 200 government employees go to work at JPMorgan to make sure that they follow all the regulations and do all the rules and sign off on every one of the decisions. So many of industries today have been nationalized without saying they'd be nationalized. Basically, the banking sector in the world is run by governments. It's not run by private entrepreneurs. So, no, I think we know what the system is that produces human flourishing. We know what the system is that produces human wealth. And that is capitalism. And it doesn't need altering. We don't need a new system. We just need to embrace it fully and consistently, which we've never really done. We mentioned producers, aside from those people who give us intellectual products. What about the businessman? You've talked about capitalism. I'd like to know his role in this. Well, the businessman also is as recent a product as the intellectual. Before the birth of capitalism, there were no professional businessmen and there were no professional intellectuals. Both the mind and material production and trade were enslaved and ruled by the various combinations of Attila's and which doctor's, which means by a powerful government, by an absolutist type of government, whether it was the feudal absolutism or the absolute monarchies of Europe, of the past Renaissance period, in any case, the producers of material goods, the traders, and the producers of ideas, the teachers, philosophers, the early scientists, were men without official status, without a profession and the total mercy of the political rulers, which means that the mercy of rule by force. It is only since the industrial revolution, the birth of a pre-society, the society of capitalism, that there was a new class of men, which is the pre-producers of material goods, the businessmen, the industries. They, of course, are the producers, in a strict sense of the word, or should be, but they are the greatest victims of today's society. They're the ones who have been betrayed by modern intellectuals. And in this sense, both businessmen and intellectuals will commit suicide by destroying each other, and the fall belongs to the intellectuals. The businessman is the man who has to use his mind to deal with reality, study facts, to produce material goods. He is the man who serves as the transmission belt of the discoveries of science and carries the product of science to all levels of society. He is the one who takes the invention of an theoretical scientist or of an inventor, transforms them into useful products, and putting them into mass production makes them available to all levels of society. The businessman is the man who has achieved the enormous, historically miraculous rise in the standard of living of mankind during the 19th century. He is the one who has lived up to the role of a producer, to the role of a rational, creative man, but the intellectuals have never given him credit for it, have regarded him as if he were an Attila, and being afraid of freedoms themselves have been looking from the start of the Industrial Revolution for some form of an Attila to protect them, the intellectuals, against the free market of ideas. Well, you know, you've been talking about the bankruptcy of our modern intellectuals, and I know that in your most recent book, this is really a manifesto to a group that you call the new intellectuals. Would you mind telling me just who they are in your own words and how they differ from the old style intellectuals? Since the old style, the presently existing intellectuals, have declared their own bankruptcy by abandoning the intellect, what we need today, what are called the new intellectual, would be any man or woman who is willing to think, meaning any man or woman who knows that man's life must be guided by reason, by the intellect, not by feelings, wishes, wins or mystic revelations. Any man or woman who values his life and who does not want to give in to today's cult of despair, cynicism and impotence and does not...