 Okay, we'll get started. This is a nice small group, I appreciate it. If anybody feels brave enough to come down towards the front, I don't know if it'll be easier or harder to see the slides with the glare from the back or the front, but I know there's a lot of popularity in this slot. You've got the board meeting, the next JS and the technical debt talk, so thank you for choosing to come to this one. Before I get started, I wanna make sure that you are in fact in the right room. This is What Can We Learn from the Drupal Local Development Survey, which is a survey of all Drupal developers worldwide that I conducted earlier this year. I shared the results of the Drupal South Conference in Wellington, New Zealand in May. This will be a variation on that with a closer look at how things appear in Europe versus the rest of the world. So my name is Mike Richardson. I run a Drupal web hosting company in Australia that specializes in mission-critical websites. And I also help organize a couple of conferences. I'm the Treasurer for the Drupal South Steering Committee in Australia and New Zealand, where we put together the Drupal South event. The next one will be in March in Sydney. I'll have a slide at the end to try and pitch that to you. And the other one that's just being announced at the moment is Drupal Asia, which is a new event that's being run in Singapore from July 31st to August 2nd next year. I'll talk a little bit about that later on as well. So let's get on with it. I'm gonna go out on a limb and guess that everybody who made it into this room has heard of the survey before. Can I ask you to raise your hands if you'd completed it not this year, but in a previous year? One, two, okay, three, all right, thank you. Did you complete it this year? Okay, all right. For those of you who hadn't heard of it and hadn't completed it, I'm really glad that you're here. If you wanna have a chat later on, I'd love to know what drew you into this room versus the other great content that's going on and what you hoped to learn from the local Dev Survey that maybe we didn't cover today. We're starting to think about what we're going to do for next year's survey, the questions we wanna ask. So feedback is really, really valuable for us at the moment. So the Dev Survey was not my initiative. It was started in 2018 by Jeff Gealing and Chris Urban. They are both former Acquia team members, but are no longer involved with Drupal. But when I was first starting my company in 2018, the results of the survey was really, really helpful to me in terms of working out what Drupal developers are looking for, particularly from a hosting provider and from a local environment manager, which is a space that we operated in. So I reached out to Chris and Jeff to say, because the survey didn't happen in 2020 or 2021, sorry, in 2021 or 2022. So I reached out to them to say, will you do it again? Because I'd love to see some more up-to-date results. If not, would you mind if I carried the torch and they generously gave me the all clear to go ahead and start that survey from 2023? But the survey would not be possible without their earlier work. So we really are indebted to them for putting that together. Jeff, sorry, I'll just point out quickly. Chris is now working on a product at a company called Confluent that doesn't manage Kafka service. And Jeff is a very successful full-time YouTuber with over half a million subscribers. You have probably seen some of his work around Ansible on his YouTube channel. He talks a lot about Raspberry Pi's, Linux, home networking, really great channel. So I highly recommend checking it out. This year for the first time, we also translated the survey into three other languages. So we're really indebted to Marine Gandhi, Jimmy Can from Iron Star, and Chris Wu for providing translations into French, Japanese and traditional Chinese directly. And specifically for the French translation, this had a real impact on the number of results that we had. Out of something like 60 results from France, 34 or just over half of them came from the translation itself that we may not have picked up. So if you'd like to provide a translation in your own language for the 2024 survey to help us get that reach, then please let me know. It takes about four to six hours of your time to do a translation. And there's a bit of a workflow that we've got now that make it a bit easier. So let's get into some of the stats. Can I check? Are you guys here for the local dev survey results? Are you here for the local dev survey? Are you here for this talk, local dev survey? Okay, all right. All right, so looking at stats. Who responded? We had 829 responses from 96 different countries, from places as far away as Ethiopia, Costa Rica, Vietnam, Cuba and maybe not so far away, Albania, as well as a lot of the countries that you'd expect to see. We had a lot of responses from the US. We had quite a few responses from Australia and New Zealand, which was overrepresented, mostly because that's where I am and that's the first area I pushed the survey out to. I was really delighted when we made it to the first 100 responses because for me that was statistically significant. If we could get that many, there was conclusions we could draw from the data. I announced the survey in the evening, went to bed and thought, if I wake up with 10 responses in the morning, I'll be happy. I woke up with 300. So it was a really great response and it was by and large because of folks like Acquia, the Drupal Association, the developers of Lendo and Ddev, Pentheon Platform and more, sharing that survey with their own network and it ended up being consistent with previous years where we get about 1,000 results. So 829 from 96 countries is really, really great. Looking at Europe, 369 of those responses came from this region and for the purposes of this presentation, Europe includes Turkey and Switzerland and the UK, Norway and other EEA members. We can see that France won out in terms of overall responses and again half of those came through the translation. UK falling just slightly behind with Spain, Germany, Belgium and the Netherlands trailing off from there. Again, if we had a German translation or a Spanish translation, it would be really interesting to see just how more well represented those regions would be. So if you'd like to provide a translation, I would love to have the help. We also asked respondents including yourself how many Drupal developers are in your current company and this was to gauge the size of the teams that people were working in and as you can see from these stats, there are still quite a number of Drupal developers, about 17% who are on their own and there's also quite a large number of Drupal developers, about 20% who are part of a team of more than just Drupal devs, more than 25 Drupal devs in that team. And I actually made a little bit of a mistake here because in the 2020 and earlier surveys, there was a block for 25 to 50 and more than 50 and I from my very naive perspective went, well, no one's gonna be in a company with more than 50 Drupal devs surely. And so I took it out and just left it at 25 plus in order to shrink the survey slightly and that I think was a mistake. So next year, we will bring that back. So a very, very widespread but when you think about some of the QA results that we'll look at later, just remember that more than 20% of Drupal devs are on their own or just with one other person which impacts those sort of statistics. Probably everyone's favorite area of the results was the local environment manager, Lando versus DDev versus Lamp versus Homebrew, et cetera, et cetera. We had a lot of really interesting responses there. Most people are using more than one tool and if you look globally, you can kind of see a bit of a map here that attempts to demonstrate and I know that these colors must be really hard for you to see so I'll step through it really briefly. In the US, Germany, Italy, Austria, Spain and Finland, DDev is the leading solution. DDev was incredibly popular in the US and that surprised me a little bit because as you can probably see in the bottom right hand corner, Australia and New Zealand, Lando is overwhelmingly popular and I don't know of very many people who use DDev within Australia. I don't know the reason for that but most people back home will use Lando. In Australia and New Zealand, 50% of Drupal devs just use Lando whereas in Europe that value drops to about 28% and solutions especially in places like France and Poland, solutions like custom Docker become more popular for whatever reason and again, DDev looks more popular overall because it's got strong representation in the US about a quarter of all survey responses came from the US and custom Docker looks more popular in Europe. So if we look at that comparison between Europe and the rest of the world, you can see that DDev is about the same. Lando is less popular in Europe than everywhere else but custom Docker solutions and Lamp, Wampstacks and Homebrew, sorry, a custom Docker solutions are more popular in Europe but otherwise it's pretty similar stats but I thought that was interesting. We also had a look at if people were thinking of switching from their local environment manager. Now because a lot of people were using more than one, most people were using more than one, it was a little bit hard in the survey results to say people with DDev are more likely to switch or people with Homebrew are more likely to switch but overall regardless of the tool or tools that people were using, the overwhelming majority are sticking it out, they're staying with it, whether or not it's Lamp and there was some free form sections on this question where people were quite adamant to point out I don't want to use Docker or I don't want to have to manage this and so on so there was a lot of strong opinions about what people's local environment manager is. We also had a look at what tools were more popular based on team size and I think there's an opportunity with stats like this for people in smaller teams to get a bit of insight into what larger teams are doing and using. So again with this glare, it might be a bit hard to see but effectively do-it-yourself, Lamp, Wamp and so on solutions are more popular with smaller teams, Lando is more popular with smaller teams, DDev and custom Docker solutions and Doxel tend to be more popular with larger teams. At very large teams the difference seems to break down but certainly if you're in a team of three to 10 it would seem that DDev wins out over Lando but that might also be because DDev is more popular in places like the US and Germany where there just happened to be larger teams. On the topic of Docker, we asked developers if they felt that it was important to understand how to use Docker. 70% of everyone who responded to the survey is using some form of containerized local environment. So the majority of people are using Docker but the question is do you need to know how to use Docker to use these tools because tools like Lando and DDev abstract a lot of that away from you. I know a lot of DDev users and a lot of Lando users who have no idea how Docker operates and when those solutions break they get stuck because they don't know how to troubleshoot those tools but otherwise they're completely happy and they're not interested in getting further into the details with Docker. So 59% of respondents said yes, it's important to know how to use Docker to be a Drupal Dev which again isn't surprising since 70% of them are using Docker in some format but I did want to see how that answer changed based on the user's experience with Docker. So again with the glare this is really hard to interpret but I'll walk you through it. On the right, sorry on the left hand side is the yes group. So this is the group that says you should know how to use Docker if you want to be a Drupal developer and on the right hand side is the group who says it doesn't matter. The bars in each group represent the skill level so most people know how to do basic tasks some people know how to do additional tasks and all the way on the right hand side in green is like running Docker in CICD environment. So the left hand group is slightly more skilled at everything than the right hand group. So there's an impression there that people who are more comfortable with Docker think it's more important but generally there's a lot of people who are comfortable with Docker that don't think you need to know it at all. And again, 70% of people are using Docker, 59% only don't think it's really that important. Operating systems and code editors. There's not a tremendous amount of insight in this but it's interesting to step through. It's mostly as you'd expect it would be 56% of users are on max. This is global, 29% are on Linux, 15% are on Windows. But if you look at those values for Europe, things change quite a bit. Mac drops market share by about 10% and the difference is almost entirely made up by Linux which is really interesting to see and it goes in line with my own expectations just from an economic perspective that there will be parts of Europe where shelling out for a high end Mac book just isn't going to be feasible, getting something more cost effective like a Linux laptop or a Windows laptop is more likely. So that's how things sort of look at a high level and if you drill down a little bit further into the individual operating systems for Windows and Linux especially, you can see that Debian based Linux is overwhelmingly more popular than any other Linux variety and Windows 10 still beats out Windows 11 even two years after Windows 11 was being used. Can I ask for a really quick show of hands? Who here is developing for Drupal on Windows? Yes, yes, yeah, yes. So the question is, how did we classify WSL or Windows subsystem for Linux users? And in the original survey, we didn't but in the notes that you could have for this question, they did. They absolutely were like, yes, I'm on Windows but I'm not developing in Windows, I'm developing in Linux on Windows. We didn't get to capture that in this year's result. We will capture it in next year, particularly not just for people who are doing development in WSL but also people who are doing development in a VM that's different. So for example, if they're on a Mac but they're in a Linux VM, we didn't really get to capture that in this year. We didn't bother to ask what specific version of Mac OS people were running simply because it didn't seem meaningful. Most people will update their Mac OS version and the difference between Mac OS versions isn't dramatic like it is for something like Windows 10 to Windows 11. We asked folks what IDE or editor they use. This is the global data. So we got a lot of feedback on this question because we only gave an option for one and a majority of people use more than one IDE, which is an oversight because I use more than one IDE. So next year, we will ask people what they're using but in this year's survey, we're asking people what their primary IDE is. And you can just see that PHPStorm edges out VS Code just a little bit. There isn't a lot of market share left for anybody else. There are some people who are still hanging on to Adam and Sublime and if you look at the Europe values, there are even some people hanging on to Notepad++ which is great, great for them. There's three VS Codium users worldwide. VS Codium is the completely open source version of VS Code. Those users, all three of them are in Europe. Don't know why, but interesting start. And they're not in the same country so I don't think they work on the same team. But what you see with the Europe stats is that PHPStorm gets a lot more market share. It goes about 10% market share over VS Code which I thought was really interesting. I would have thought going back to those economics of people in parts of Europe aren't gonna shell out for a Mac book. I wouldn't have expected that group to be shelling out more for a paid for closed source editor versus something like VS Code which is free. But those are the stats. Looking at this data over the years, again with the glare, blue 2019, top row, middle row, red 2020, the last time Jeff and Chris ran the survey, and yellow 2023, this year's survey, you can kind of see how the market share has shifted over time. So what's very interesting is PHPStorm and VS Code are gaining market share but not really from each other. They're gaining it from the Sublime and the Notepad and the Vim and everybody else. So those tools are falling in popularity. There's still one person on BB Edit and one person on NetBeans. But overwhelmingly, PHPStorm and VS Code have consolidated the market. And again, it's really interesting to see that the paid for tool for PHPStorm is still in use. I wanna do another quick raise of hands. Who here is on PHPStorm? Okay, who here is on VS Code? It's that. That's basically the way it worked out. Do you have a question? Sorry, what's that? Eclipse? Oh, sorry. Eclipse, not captured. It wouldn't have been enough, I think, yeah. Yeah. Okay, sorry about the microphone. Moving on, quality assurance. So we asked which quality assurance controls were in place, keeping most of the same answers that were in the 2020 and earlier surveys. So this is the percentage of respondents who use a particular QA control. So for example, 65% of respondents are using peer code reviews. If that seems low, just bear in mind that 17% of respondents don't have a peer to code review. And as we move down, 16% of people are still doing nothing. There were even some people in the results that are saying things like, I'm still making my changes live in production. And there's no local development environment. If you compare this data to the rest of the world, the results are pretty much the same. So sorry, this is Europe before was global. 63% versus 65, 60 versus 58. So it's roughly the same. There isn't a tremendous amount of, there's no gotcha moment here where it's like, ah, Europe's different to the rest of the world. From a QA perspective, Europe's pretty much the same. But that changes. We asked people about their future with Drupal. Specifically, whether or not they thought they'd still be using Drupal in 12 months. I know this is a Drupal con. You're probably all embedded within Drupal and planning to stick with it, I hope. But as a show of hands, is there anyone in the room who, I won't call on you, so don't freak out. Is there anyone in the room who doesn't think they'll be working with Drupal in 12 months? Akilah, keep your hand down. Now, all right, so you're all going to keep working with Drupal in 12 months, but you're not representative of the wider community. Globally and in Europe, about 2% say they won't be working with Drupal in a year's time, 13% say maybe, so 15% overall. Again, it's the Drupal Development Survey. You would expect it to have a pretty strong bend in that direction, and if people weren't expecting they'd be working with Drupal in 12 months, they probably wouldn't have answered the survey. But it will be really interesting to see how that data changes over time. What was next? My favorite topic, hosting and security. So, we asked respondents who they used to host their production websites, and we got a tremendous amount of answers. Most respondents, and I'm talking like 85, 90%, are using more than one hosting provider. So we collected a lot of data for this question, and globally there were 81 different hosting companies that were mentioned. About two-thirds of those only had a single respondent who was using them, and they tended to be local companies that were specific to a particular country. So for example, Crystal in the UK, Gundy here in France, Iron Star in Australia, there were a few of those, Sakura Cloud in Japan. But looking at this data, Red Top Line is the global market share, Blue Lower Line is the share in Europe. And you sort of see that AWS, pretty much the same. Acquia drops from 18% globally to 13% in Europe. Same thing with Pantheon. Both Acquia and Pantheon are less widely used in Europe, whereas Platform is pretty much the same. Tools like Azure, DigitalOcean, Linode and Google Cloud, more heavily used in Europe. We've also included what I believe are Europe-specific providers, Hetzner and OVH in those stats as well. The reason they probably look really similar is because for the global stats, the Europe data is included in that cohort. So that's sort of how the hosting provider usage looks. And the other really interesting insight in this is how usage of a hosting provider changes based on team size. So what you're looking at here on the left-hand side is individual developers and teams of increasing size over to the teams with more than 25 Drupal devs in the team. And what you'll see is larger teams are more likely to use a platform as a service provider like Acquia or Pantheon or Platform. I think there's an expectation that a larger team with more budget and more skills is going to host it themselves. But in reality, those teams are more likely to want to let somebody else host it. So if you've got a decent-sized or mission-critical website, this isn't a pitch, it's going to sound like a pitch, but it's not, if you've got a mission-critical website and you're self-hosting it, have a think about the fact that people with the larger sites don't want to do that. So I'm just going to let that gentleman take his photo. All right, cool. The slides are available, by the way, if anybody needs them afterwards. And the full dataset is available as well. If you want to have a look and crunch your own numbers, you can get access to the Google Sheet, too. So yeah, larger Drupal teams prefer Paz providers rather than doing it themselves. We asked respondents which security controls they were using to protect their sites, and this is one of those areas where Europe just did not reflect the global trend at all. And to be honest, not in a fantastic way. There were about 143 people or 17% of respondents who just didn't answer this question. This is part of a survey drop-off where this is one of the last questions on the survey, so everyone's getting a bit tired. But also, there were a lot of people who took the time to fill out the survey and just say, I don't know, it's the IT team, it's the client team, somebody else is responsible for this. But if you have a look, tools like having some form of two-factor authentication or SSO authentication for Drupal goes from 44% globally to less than a third within Europe. And to me, I'm concerned by that. If there was one thing I think you could do to protect your Drupal site, it's probably to patch it. But the second thing is two-factor authentication or SSO. So those are really poorly represented within Europe, and I hope in years to come that can change. I did a talk in Prague last year that was aimed at non-technical decision makers and trying to equip them with the questions they could take to their team to sort of say, what are we doing in this regard? And it was kind of pitched as a training session for people who are responsible for Drupal security but don't know anything about Drupal security. So if you wanna get a link to that, let me know afterwards. Next year, we will expand this question to ask about more advanced controls like workstation security. A lot of really big headline attacks that are happening at the moment are all through compromised workstations, last pass, OCTAR, CircleCI all got bitten through attacks like that. So that's that, and that's the bulk of the survey results which we got through much faster than I did in my rehearsal. So let me talk to you about Drupal South. So Sydney, beautiful part of the world. March, the best weather that you will get. The call for papers just opened for Sydney this morning. So if you wanna come down and have a chat to a bunch of Aussies and Kiwis about Drupal, please go and put that talk in. We also do Splash Awards which is a fantastic event that we've copied from Europe where we all get dressed up and we hand out an award for the best Drupal sites. Some winners in the room from last year's event. And there's a really great one day contribution workshop that's generally run by the very talented guys at previous next. So Drupal South.org forward slash Sydney. And in July, the just recently announced Drupal Asia in Singapore. This is a two part thing. Part of it is an event to get India, Japan, Philippines, Vietnam, Australia, New Zealand, Singapore, all into one conference where we can all share ideas and innovation and perspectives but also to establish a Drupal Asia steering committee that will be an elected body from the region that will be responsible for running these events in the future and building that community over time. So thank you. You all get out a few minutes early. Feel free to, on the left rate this, the conference on the right rate me and does anyone have any questions? Yes. Do you want to, sorry. Do you want to come up to the microphone? Thank you for your putting together this survey as well as for sharing the results with us. Going forward, do you have any plans to look at the results over years compared to what was done before going in the future to spot trends? Like I'd be interested to see like stupid little things like this VS code. How does that look versus like three years ago versus today? Yeah. The stat before that was comparing where was it? Yeah. So comparing say VS code down the bottom there versus 2020, 2019, I didn't have access to the raw data to the spreadsheets for that. So I'm going, I've plugged all of that in manually based on the previous YouTube videos, but definitely for 2024, 2025 and so on, there'll be a big component of tracking stuff over time. And also you've got to kind of, it's really hard to balance not asking too many questions, but not getting enough data. There were questions we asked like, are people doing any headless work? And I think the response was like 60% of people had built a headless site in the past year. And there's followup questions we want to ask from that now, which is how did you do it? What tool did you use? Would you do it again? Which I find is the most prevalent question when it comes to headlesses, you know, would you do it again? So we definitely want to ask questions like that and compare them year over year. Now we've got the full data set for next year and that's open and anyone can access it. We can do the same thing for next year and regional groups can do it as well. Like if someone in South America wants to run their own survey for their community, they can do that and they compare it globally like I just have done. Thanks. Anybody else? Cool. Class dismissed. Thank you. Thank you.