The State of Django

Hi

Speaker 1: everybody, I'm so excited to be here. Everyone in person and online. It's the last talk of the conference. It's been a great year. Yeah. All right, so this is the State of Django twenty twenty two. Uh this is the US edition. We have uh sister conferences all over the all over the world, but this is our US version and we also have friends from all over the world uh here with us today. So um so the the the friends we have uh represent uh imminent voices in the Django community. Uh it also implies a level of familiarity and uh comfortability with the Django community, but I'm expecting to learn here today as I as we ask

Speaker 1: And I picked some questions that I want to know the answers to as well. And they were also uh given from feedback from people online. There was a forum that went around of I know I got some really good questions from people as well. So hopefully uh you'll feel uh feel some of the questions you have represented up here on stage All right, so I'm gonna go through and we can go from my right to to the left of the stage. Um And we can have everyone introduce themselves , the full name, their pronouns, and their relationship with the Django community, and your favorite icebreaker question. Yeah, so I'm gonna go first. Okay. Uh yeah. Oh, I said I wasn't gonna change anything and I changed that one. I'm sorry.

Speaker 1: That's the only thing I changed. So my name is Dawn Wages, she, her pronouns. I am the Python community manager for Microsoft, software engineer for a few years. And in my relationship with the Django community, I help organize these events sometimes with a really great crew. I organize Django Girls events and I am a product of Django Girls 2016 So it's been really exciting. Yeah. And I also want to give a special shout out to Philly Python Users Groups. Don't forget your your streets that made you. And I I love them to death. Yeah. Alright, so let's go left to right.

Speaker 2: I am um I'm Carlton, Carlton Gibson, I'm uh he he him pronouns. I'm um Jangofellow and uh Do Django chat with someone else over there. Um my favorite icebreaker?

Speaker 1: Icebreaker question. Oh, I didn't do that one either. Okay. My favorite icebreaker question is um what is your favorite mythical creature? And I like to answer, I am a fairy.

Speaker 2: So Oh that's good. That's good. I've been married so long, I'm not sure I have asked very good questions. They used to be quite cheesy. I w I couldn't couldn't couldn't say them now. Uh

Speaker 3: hello everyone, I'm Andrew Godwin. Uh I'm he, him or they them pronouns. Either one's fine. Um and yeah, I've been around Django for a while. Uh that's probably the best way to describe it. Um these days I'm a principal engineer at a company called Astronomer, which We actually work on Airflow rather than Django, but I still do a lot of Django stuff and Python stuff in general. So I I also come here just for the people, as I'm sure all of you have realized over the last uh we A few days. And my favorite Ice Maker question, I I don't have one of the this is it's it's mm, yeah. I know. What's your favorite hobby probably? Because I have like twenty-five of them. So that's a good match. Yeah.

Speaker 4: Hi everyone. Uh my name is Marj Freshek. I'm uh he him pronouns. I'm a member of the Django security operations team. I'm also a release manager of few Django versions now and a Django fellow since 2019. question.

Speaker 1: Yeah. This is the hardest question you're gonna get on stage all day though.

Speaker 4: I would probably not figure out anything clever now. He will be here on it.

Speaker 5: I'm Jeff Triplett. I'm uh vice chair for the Python Software Foundation. I'm also the president of DEFNA, which is part of the nonprofit that holds DjangoCon US, which I think I've been helping since 2014. I'm also a partner and an engineer at Revolution Systems in Lawrence, Kansas. I was kind of lucky to work at the newspaper that created Django a couple years after it was open source. Also, I help run Django News and Awesome Django with William Vincent. I also run Django Packages. I have no icebreakers whatsoever. So I'm sorry I failed you, Don, from the beginning.

Speaker 6: All right. Hi. My name is Rachel Calhoun. She, her pronouns. I am a software developer at a medical device company. My relationship with this community is uh I'm also a product of Django Girls. Um yeah. Out out of Out of uh Seoul, actually, that's where I got my start, and now I I'm in Grand Rapids, Michigan, where I organize local events for uh Django Girls and Py Ladies. I'm also uh trustee for the Django Girls Foundation. Um my iceberger question I'm it was hobbies, so that's it. Nothing there. That looks exciting.

Speaker 7: Hi, my name is Will Vincent. He him. Uh I have a couple books on Django, but most of my community involvement is I'm on the board. I've been the treasurer the last three years. Django chat podcast with Carlton, Django News Newsletter with Jeff, awesome Django repo with Jeff. Some other things. I like to ask what's your favorite ice cream flavor and why isn't it coffee?

Speaker 1: It's a good one. Cool. Awesome. So um we're gonna start uh jump into the questions now. Uh so Django has received over seventy-eight million downloads in 2021. Uh rise of 20% in 2020. Downloads in the past day, I checked this morning, was 365 ,394. Last week was two million uh seventy-eight thousand four hundred and thirty-eight. And uh in this last month was eight million seven hundred and ninety-nine thousand nine hundred downloads. This is all courtesy of PyPI stats. The PyPI um is the Python package index, which uh is a behemoth. We had a couple of talks that talked about

Speaker 1: That uh today. Um that uh is the index for uh Python packages. Um and of these uh we deposit them, a good number of them are beginners. And my question to the aud uh to the group on stage is what do we do to encourage uh and and and intend to the beginners in Django? Can

Speaker 6: I start? Um I would say contribute and support Django Girls. Uh how many people at this conference I've um talked to and I said I I you know work with or I volunteer with Jangle Girls. They're like, oh I always recommend everyone do the tutorial. Yeah, it's amazing. But we have to keep it that way. That means we need contributors. We need to work on what the tutorial. We have translations, 20 different language writing. languages right now. And we have to keep that up as the technology changes. Um especially as the first um experience with Django, I would say. Um my second point that I would like to kind of bring up is maybe like we need to work on making those, like removing the barriers to deploying your first um web app, right? And and make that experience even smoother. They don't necessarily need to learn Git, GitHub, and how to manually deploy.

Speaker 6: And so there was a talk about what simple um Uh Django simple deploy. Yeah, doing something like that with Django Girls would make it so much easier, not only for the attendees, but also the coaches. So that's kind of my take on it.

Speaker 1: We have time for someone else to take

Speaker 7: I mean I have a million thoughts, so anyway anyone else but me. Okay. Uh I think having some tutorials in the Django project like Hello World would help, having basic CRUD. Um I think the biggest thing is actually on the board we help sponsor the conferences, but getting people to come and meet the community. I think once you come here You're you're gonna invest more time and see what it's all about. And so finding ways that we can make it more accessible being online, opportunity grants, anything we can do around that, I think will help.

Speaker 5: Semi -hot take, I guess. Um I I when Rachel was mentioning about making Django beginner friendly and that deployment story is what comes to mind for me. I think Django is really good by default at settings working for beginners. But I think settings and production are the exact opposite of, you know, you you just cannot take a default Django start project and and deploy it into production. So it would be, you know, I've got ideas for that too, but that's an area I think that's not that hard that we can fix. But I think it's something that needs to be emphasized.

Speaker 1: Any more thoughts on that? Okay, cool. Cool. All right. So at the risk of editalizing um uh what actually is a beginner, I just I wanted to add an underlying point that Django is such an opinionated framework as well. Um and so I think that it makes a beginner out of a lot of us who may uh owe it to ourselves to give ourselves a little bit of street cred as well. And so in that in that context I think there are beginner and intermediate type access that we can do without um alienating the audience. So like for example, can you can you go into detail a little bit more about Django Girls for the audience that may not know and what is Django Girls?

Speaker 6: All right, well Jingle Girls is a community that um tries to inspire women to get into tech We have a tutorial that takes you from what is the internet to having a project, a Django project deploy. online and it walks the the attendees step by step. So we do workshops where we have coaches, volunteers from the community. Please volunteer if you can and to to guide them and to assist them them answer questions and um yeah does that cover it

Speaker 1: was good that was good and i kind of threw that one in there so all right so there are a lot of different ways to make an impact in Django for example the Django Software Foundation Board of Directors which is uh the nominations are open now. Uh it would the board of directors guides the director of marketing and governance and outreach. provides funding, resources, and guidance for global Django events and works closely with corporations and individual members. So uh the nominate yourself, you can nominate yourself for 2023. It's open right now. Um the elections are no uh you can nominate yourself by November 4th, 2022. And if you have questions for about applying, you can email foundation at Django

Speaker 1: Project. com. So I just want to put that little plug in and a call to action for people who may be interested in making more of an impact in Django. So I didn't mention this at the outset. I'm the treasurer and director for the PSF. I'm on the Wagtail Core team. More ways and more flavors and interstate Intersecting and um eccentric circ circles on what our community uh can do and the ways that you can make impact And let's say I am a member of the community. I am, but all of you are now members of this community as well. And you have a great idea not to be a confrontational potential You have a great idea. Um and you want to know how to make it work and how to impact the community with this idea, whether it's code or community

Speaker 1: or otherwise, security and safety. I ask the audience or the panelists on stage, what is the process to go through that? How do you recommend someone approaching giving a really good idea for Django?

Speaker 3: I guess I'll st I'll start here a little bit. Do you want me to go first, Carlton? No? He' he he he'll get there. So I mean my perspective, right, like I think there's always two flavours of contradiction. contribution. There's there's the big like I want to do this big change to Django. Um with those, my encouragement is come to us with the idea first and talk about it on the mailing list or even maybe the forum these days of like Let's talk it through. Like Jenga 's been around for at this point, scarily over 15 years. Um, many of the ideas have come through before. The fact we didn't do them then doesn't mean they're bad. It just means there's historical context to bring up and talk about as well. If it's a smaller idea, you can go much quicker. And obviously the two fellows here on the side of me probably have a better idea of how to get small patches.

Speaker 3: and stuff in um but generally like those need less less discussion if it's a bug fix almost no discussion really um but those can happen on track um but i'm sure one of these two can elaborate a bit further maybe Maurice, you go. Yeah.

Speaker 4: So yeah, if if it is a big idea, then probably the best way is to start a new treat on Django developers mailing list or on the Django forum. Because As Andrew said before, there are some ideas that were discussed in the past, and sometimes it's better to start a new treat and uh ask. what what uh to do if and if we want to if we want to have uh this injo and not waste time uh to implement it before uh the discussion starts uh to reduce the level of frustration if it is reduced at the end. Uh if it is something related with community, I would uh

Speaker 4: say that sending an email or using a contact form to the uh DSF board is probably the best way to start

Speaker 1: Anymore.

Speaker 2: features because each new feature brings with it a maintenance concern. So I just say to be aware of that. And it's not to put you off. And if your first, you know, you you can't say here's my idea and if the first response is a bit like Don't be put off. Like advocate for your idea and explain why and you know really you know bring out the the the underlying yin that this is what this is gonna serve and maybe maybe your idea go you wins over converts. Or maybe someone else pipes in with, ah, we could we could satisfy this with that. But try not it can be off-putting because of that negativity bias, but that negativity bias exists because Django's downloaded how many times a day? And we can't break it. We really can't break it. So that's why the negative by negativity bias exists, is all I'd say to it.

Speaker 4: Yeah we we need to keep it maintainable and also friendly for beginners. So There is an issue with keeping a right balance between all batteries that are included in Django and keeping it friendly for for uh beginners for and also for uh newcomers. So adding more options is not really uh user friendly all the time if uh if uh users need to make decisions that uh we can make for them. And in most of the cases we made in the past.

Speaker 3: Something I've done over my years contributed to Django. I've started as a third party package, right? Like channels was third party before we moved some of the stuff into Django Core. Migrations was a third-party package called South before it was in Django Core. calls. So like if you do have a big complex thing, don't be surprised if one of our responses is, well have you tried writing this as a third party package? Because A, they're not not tied to our nice slow release cycle for stability. And you can iterate much faster. And then B, it's a good way to prove the idea. And so often the advice can be like, well, yes, we like the idea. It sounds good. Let's try it externally first and then see if we should merge it into Django later on.

Speaker 1: That's great. I learned something. That's awesome. So we've had a few questions about production ready applications. It's prescient and top of mind. We've had a few uh talks uh this week um about production ready applications. But there's a lot that's involved with it. It's more than just coding and deploying and securing and shipping the code. It's also employing the people to maintain the code in enterprise applications as well. So just the entire gamut, so this is going to be a little bit of a more of an open question, so it doesn't have to be around code. What are some suggestions or forward-looking initiatives to support people who are doing production and enterprise applications with Django?

Speaker 1: And maybe we could start down on this end. You don't have to say. No, but you don't and anyone can pick whoever's interested and excited. I mean you're excited, Jeff. Yeah.

Speaker 3: Okay. I'll I'll lead in here. Um so it it's very interesting, right? Like I think, you know, as we sort of heard earlier and throughout the conference, Django doesn't really come out of the box ready for production, so it can be a bit tricky. And I think, you know, as a former SRE myself, there's a whole operational side of the industry that I 'm often underlooked. So I mean my view I think especially is I'm not gonna beat the documentation drum here again, but like we don't have amazing documentation for deploying stuff. But we we deleted some of it over the years 'cause we were like, oh, Django doesn't want to tell you how to deploy that's not our responsibility. Sometimes I question that. Sometimes like maybe we should have much better like here's how it works on these commercial providers. Yeah, that's with Heroku vanishing especially That's maybe more relevant now than ever.

Speaker 3: So

Speaker 7: on that thread, I mean we have the Django deployment checklist, which I would wager. Many people don't know about, let alone use, and yet it provides a checklist for your deployment. So we could highlight that more. There could be something around a start project dash dash production type of command. Um those would all help. But I mean, yeah, the docs. I mean I'm excited for this new wave of hosting companies, platform sponsoring and and the others. I think do lower the bar for many types of deployments. So we we perhaps could cover deployment in the docs a little bit more and have a story, whereas before it was so dependent on they were quite more different in what they were doing. But it comes back to like the size of Django itself.

Speaker 7: How much can Django do? I mean I've my own journey is my first time I came to this conference in 2018, I was like, why doesn't Django do this, this, this, this, and this? And then I met all the people and understood, well, this is why. And it's basically the people in this room who do Django. And their response is, you know, negative bias is like if you feel strongly, like you do it. You know, you create the PR, you you can do these things. And so maintaining that level of being friendly to beginners, but also understanding why things are the the way they are, hopefully this panel brings out, because everyone means to be encouraging, but you know, we're all keeping things afloat here, especially the folks on that end.

Speaker 2: So I'd just say for companies that um are trying to deploy Django, trying to build a bigger scale application with Django, if there are things that are missing, we want to hear about that. So our priority is make it easy to use for a beginner. But if you're deploying it at scale and you're saying, look, I need some I need At scale, if you're the enterprise, you can customize. We're we're gonna we but what are the hooks that are missing? Tell us. Show us why. Say you do you know what when we hit this scale this happens. Um we need this. Oh that's a really interesting conversation. Cool.

Speaker 3: Yeah, I think just to finish that one off, like I have over the time you know, I started off at an agency writing small websites and then these days I write big single company. applications. So like it there's such a v wide variety of ways you deploy, but yeah I think I absolutely agree with you Carlson. There are things in Django that you know I've put a few of them in over the years, but like We should absolutely listen to everyone who's doing this and draw that feedback, I think, for a lot of like, well, everyone says they actually want this thing, so we should just put it in.

Speaker 7: Fill up the Django Developer Survey if you haven't. And if you have feedback on what we should ask next year, tell us and we will ask it.

Speaker 1: Awesome. And to uh we had some great points, but we didn't have any conversations about the the employment part as well. And I'd love to underscore and kind of sort of circle back around to that. What is it like uh employing and searching for jobs as a beginner? And then as is a special sh um kind of an employment jour uh journey as an intermediate developer and with very specific knowledge in one way of deploying or one way of production or um w one type of feature and how does that how does that work and how can we help the community um evolve?

Speaker 6: I mean I guess I can speak Sure. A little bit to that from personal experience. uh or mid-level or senior, um everyone is like, well, what level are you or what do you know? And and it depends entirely on your past. And it's not like very clear categories to scale, right? So um I I don't really like that question. If you want to have a bigger question or a conversation about like what that means, I think that's more important and like what they've done instead of just like a checklist um because sometimes it's like yeah I I'm familiar with that or I've done that or similar but it's not necessarily like this specific thing. I also can I talk about hiring practices and how Yeah. Because that I that kind of ties into it. Yeah.

Speaker 6: Um and one thing that can help, you know, recruit more people at your company, for example, is taking out um gendered language in your job posts. Um uh including pay ranges in your job post. That's a big one. And I know that it's not always easy because there's, you know, um HR and you don't you maybe you don't control all that, but I'm I'm speaking to all the posts in the jobs channel on Slack. Um anyway, um but stuff like that and also like hiring outside um like professionals that actually know what they're doing because oftentimes you're interviewing people you maybe that's not that's not your expertise. Um and they can also help with you know diversity inclusion but also understanding why having a diverse team is important. It's not just like we are we have a diverse team, right? That it adds value to your team and your product.

Speaker 6: Oh, also Claire from Django Girls, she wanted to mention she wanted me to say that if you want help writing those. um job descriptions or if you need assistance, she is a resource and she wants the community to reach out to her and she's willing to help. Yeah.

Speaker 1: Can we get that

Speaker 6: Claire at DjangoGirls. org.

Speaker 1: Cool.

Speaker 6: C-L-A-I-R-E. Also hello at jingle girls. org. She's she's hello too.

Speaker 1: Awesome. Dropping resources. And my little I mean I've I've gone through this recent experience as well. Um and I I would consider myself more mid-level Django engineer. And I noticed that there's a lot of maybe like take-home projects. or um certain things like that. And it's it's I don't think Django um or the entire engineering industry really has the right way on hiring. I mean you're asking people to do work at home for free And it also gets kind of in a weird gray or even a scummy area when you're trying to ask them to do things to fix your problems on their own time to prove if they can do it. And I've seen that happen before a couple of times. Um and it's just I I I want to highlight ideas about having real

Speaker 1: world uh problems, but then also like we we run on trust, um and you can't uh decision model out the way a risk of getting to know a person and figuring out whether or not they're gonna um fit in that in that use case. So really adding a people first approach to the hiring practice. This sounds a little hokey, but I think it's the only only way to go to do it the right way, you know. Um so we can keep moving on. We did a a good amount of time on that one, which was great. But I wanted to talk about what's it what it's like or how can we uh create an uh Create an atmosphere where people who are not white or cis or hetero or uh identify as a man or of a particular age or of a

Speaker 1: particular background or of a particular country or is neurotypical how do we create an environment where they feel comfortable at Django um and in Django community and then how do we help them stay? And how do we get them back year after year? And it's not just necessarily necessarily about this in in-person event, but matching the contributors of Django to the audience that is also using Django. um in in getting them involved in the community in that way. If we have any thoughts from the panelists.

Speaker 7: So one quick one is the board. We have, I think, pretty good representation right now, but we really want the board to be as global and representative as we can. So even if you're earlier in your career, like you can still be on the board. You don't have to be uh you know committing to Django itself. So the board the board is one way to do it, but it's an important one.

Speaker 5: So um having been around Python for a while, um when I first got into Python, I didn't think it was the most inclusive. Um audience are very diverse, and I felt like eventually Django came on came around. And somehow the Django community in some ways has helped pull Python forward. Now, this is my very biased take on it, but from my seat, what I've seen over the years, that's kind of the progression that's happened. Now though, Django, the Django community has done so many things right that they're, you know, and in being on the Python Software Foundation board, one of the first things that always comes up is what is Django doing? What is the Django cons doing? And now we're getting to a period of time where I think Python, C Python, the steering committee, I feel like in some ways they have solved some problems that we have yet to solve. And I think we need to look at what they're doing.

Speaker 5: Now one example is we have, and I'm in the way code and the way like technical decisions are decided, it's still technical decisions. But CPython has had a steering council for a while, and the people who are on it, some of them haven't written C code ever, and some of them haven't written C code in 10 years Now, I don't know that Django is doing anything wrong, but I don't think like we're really leveraging our community when it comes to what is the future of Django, what is the future of Python, like CPython's able to do. So Carlton, I feel like you have a

Speaker 2: Yeah, I agree absolutely with you, Jeff. I think one thing we don't do is like so the technical board is all white men. And We've got this requirement in the governance of Django that to be a candidate for the technical board you have to have a kind of recent involvement in the development of Django. Now we've kind of interpreted that as quite a strict in inter um thing in the last few elections. It's like, you know, only white men who've been on the active on the mailing list have stood. But perhaps we could loosen that restriction or get rid of it entirely. I mean we have to that's a conversation. we have to have so that any member of the community can be can be a candidate for the technical board and then absolutely guarantee they get elected because the the Django community is a diverse body and

Speaker 2: We just don't sort of show it when you look at Django, it's all white men. But it's not. Like, ah.

Speaker 1: Yeah. Well

Speaker 3: as a member of the technical board, I do think the name steering committee is better as well. Like names have power, right? Like The name technical board implies it's like people meeting in a darkened room making like amazing decisions. But we don't do we barely talk about stuff, right? It's not really that like Like in my opinion, like yes, we should have a group that I think lays out the vision for Django. And I think steering is a much better word to use for that. And I also think expanding the remit of that to be much more about outreach and direction and how Django as a community and project grows rather than merely just as a code base. I think that's kind of important to me as well. Are we doing hard takes

Speaker 1: We are.

Speaker 4: Yeah, so my hot take is that we need uh that we need a mentorship program. We need a mentorship program for new uh Django core developers. So that that that is fine is something that uh I'm personally missing and I think that we 'll find volunteers to to be mentors.

Speaker 1: Cool.

Speaker 7: Now I would like to see a Django grants program, which we could do, for example, it's a technical board spec'd out 10 projects that are doable. If people need funding, the board can help with the funding. If they need mentorship, we can coordinate that. But to keep pushing Django forward, because there's any number of things that need the right person with two or three months with some mentorship and it'll get done. And it's just just a bit too much on a volunteer basis to expect of anyone. And again, if if funding is the issue, we can expand the pool of people who can do it as need be. Cool.

Speaker 6: I just wanna second that like a huge I've tried to say that like historically excluded groups of people are just that excluded and they often don't feel comfortable like stepping up or making that first connection. So if there's a mentorship program, somebody Or that they you know you can read, hey, why don't you try this or hey you'd be great at this, you know, um and just kind of bring them along and include them like actively. Um I think that would also help along with the mentorship. program.

Speaker 1: Yeah, Jjango Project has in in several years participated in the Google Summer of Code. That was just very, very exciting to have that happen. And I I've seen firsthand it on um in not in Django Project project, but in a in a sister project, um summer project. Um and I love programs like that. So I I just absolutely underscore. Sure. Yeah.

Speaker 5: Um so we're looking to have two fellows on stage, I think for the first time in Django Khan US history. They can't do it all. So a lot of the things we're theorizing, it isn't their jobs to do that. So I'm glad that they're happy to help you do some of this stuff, but we really do need more people too willing to help and and make Django pull pull it forward.

Speaker 1: All right, it's time for a game. We're gonna switch it up for those who might be getting a little bored. So we're handing to each of these, uh each of the panelists a whiteboard. Um and we're gonna go rapid fire through um a few technologies, like a half a dozen. And I didn't want to make it um too much of a uh technology conversation, but really to underscore the point of we are paying attention to what's coming up, we know what's happening, and we all have kind of opinions. So let's also give you a wipe. You get an eraser and a pen. Alright, let's do this I should have had an assistant up here. There you go. Pass him down. Yeah. Oh start on this end. There you go. Cool. Oh my gosh. Okay, this is gonna be fun.

Speaker 1: I want pumped. I want pumped y'all. Okay. Let's get into it. This is a game show or something, right? Cool. Alright. So this could end up like excluding some people from uh your Pictionary game, or maybe it'll be fine. It could also end up being like gymnastics or something. Alright, so how does everyone feel about async? Async and Django, asyncing being included, how do you feel of it? You could put a face or a poop emoji, I don't know. Sure, d this is yeah, we're gonna do and we're gonna go through. All right, ready, set, turn, everywhere turn. All right. Question mark. Okay. Check mark, smiley face, these look good. These look it depends, yes. Okay. I want the question mark.

Speaker 1: Can you describe your question mark quickly? Well,

Speaker 2: I still have to

Speaker 1: remote it

Speaker 2: 's still an unknown is the the why for the question box.

Speaker 1: Okay, yeah. Okay. All right. How do we all feel or give you a chance to erase? I'll give you a chance to raise. How do we all feel about type annotations in Django? You're puzzling. Okay, I was supposed Okay , when you're ready, like hold it, hold it the wrong way. Yeah, you can flip it. How are you doing? Okay, so we go. Any uh is that a half check mark? Oh, yes, please. It depends, Chug. Okay, let's see Yes please? Do we feel strongly about the yes please?

Speaker 5: I d I do. I think it's um I mean I feel like there's a ship that's sailing and type annotations is something that projects do I see it installed a lot with clients too, where they're using third-party uh type annotations, and maybe there's a technical reason we should not include them at this point, but I don't know what it is. So

Speaker 1: Cool. All right. All right. So next one, I'll give you a chance to erase. Uh third party logging observity observability and monitoring. So this would be any way that it could be included in Django or making it more susceptible or accepted and or provide resources or endpoints for it. How do we feel about it? Thoughts. I love these pensive faces. All right. When you're ready, turn. Okay. How? Okay. Question marks. Lots If it works, I like. Need convincing. Woo. Okay. What is the blob? Can you tell me a little bit more about why the why the blob?

Speaker 4: I didn't really know what to Yeah.

Speaker 1: That's okay. It's a nice blob. It's a nice blob. Okay, um we're gonna go through a few because we've been talking for a while, really great stuff, but let's um skip to We had a great talk about Python in the browser, Python and WebAssembly, Wasm, Pyodide. How do you feel about that and its incorporation with Django? Uh shout out to Absurd Django. That was a really great talk. Okay, turn. Yeah it is isomorphic Django maybe is that a crown? I like it. It's the future exciting excited maybe okay alright.

Speaker 1: Okay, okay, okay, I like it. Okay. It sounds like we're all from similar pages. Um let's go with uh HTMX. We're all friendly on this stage. Okay. Turn the boards. Turn the boards. Yes, yes. Okay. Nice, nice. I like it And Marius, you have a um a pattern of these faces. I like the faces. Okay, um let's talk about serverless Django. How do we feel about serverless Django? I don't know's are acceptable, but I like funny responses. I'm hoping for a poop emoji.

Speaker 1: Well, not for this one. I'm just in general. I want to interpret a poop emoji. emoji. Alright, are we turning it? It's hard. Question mark. Alright. What is serverless anyway? Fair. Fair. Okay. It's hard. Question mark. Alright, okay. And anybody of that particular one wanna describe a little more on why they got the Yeah?

Speaker 2: What's the use case?

Speaker 1: Yeah. Okay. I like that. But it's more of the theme of let's explain it, let's uh before we support it. I get it. Okay, cool. Um are we doing on time? I think Group printing okay. Okay. Um cool. All right, well we are past time, but we've had a lot of fun Alright, time flies when we're having fun. It's been really, really great. I'm so glad you guys did this for me. Y'all are such good sports. Thanks y'all.