WEBVTT 00:00.000 --> 00:11.680 Hello everyone! We're getting started. I have to project because this room's full in that 00:11.680 --> 00:26.760 rocks. Anyway, ready? All right, welcome to the first ever Swift Devroom! Yay! And welcome to 00:26.760 --> 00:38.760 the Swift ecosystem! And I'm Paris. I'll be your MC for today. And we are so excited to have 00:38.760 --> 00:48.120 everybody in this room for the first time for this inaugural location for Swift. This room 00:48.120 --> 00:53.400 would not be possible today without the diverse set of volunteers that we had from the 00:53.400 --> 00:59.560 community who helped us with various backgrounds that they have select talks and plan for this 00:59.560 --> 01:15.160 amazing day of operations. Please give them a high five when you see them. We were so impressed by the number 01:15.240 --> 01:25.560 of talks that were submitted this year. So next year, let's get a full track. Before I get into the 01:25.560 --> 01:31.720 Swift ecosystem bits, quick recap of some housekeeping items for how this Devroom's going to work 01:31.720 --> 01:39.000 today. And obviously this is most applicable to the folks in person, not necessarily our live stream. 01:39.080 --> 01:46.520 Hey live stream! And as we go along our day today, I'll probably repeat this a couple of times. So 01:46.520 --> 01:55.800 first things first. We do have a code of conduct. If you need anything in that regard, please reach out 01:55.800 --> 02:03.880 to conductatphosdom.org or see someone with a phosom staff shirt. Please be kind and consider it to 02:03.880 --> 02:13.400 each other. That's all we ask. Second, meet the speaker in the hallway after their talk. 02:13.400 --> 02:19.160 If they have, if you have questions, please don't interrupt the speaker during their talk and try to 02:19.160 --> 02:26.040 reserve all comments and questions to the end. We need to transition speakers pretty quickly and we 02:26.040 --> 02:30.600 also need to ensure that the live stream has a good experience too. So we are going to try to 02:31.240 --> 02:36.920 ask you to step into the hallway if you'd like to speak to a speaker afterwards. Obviously if we do 02:36.920 --> 02:42.760 have time and the speaker would like to take questions, we will do our best to try to get some live 02:42.760 --> 02:48.440 questions going. We also have some hats and shirts and front as well as some really great 02:48.440 --> 02:54.760 Belgian chocolate, so during speaker transitions, we'll do some clown acts up here, ask you all some 02:54.760 --> 03:00.440 questions and wind cool prizes. So that'll be really fun until later this evening. 03:03.880 --> 03:10.920 All right, now I'm in the show. All right, so today I'm thrilled to share some incredible 03:10.920 --> 03:17.320 achievements from the Swift community in my style of a live listicle who doesn't love a listicle 03:18.520 --> 03:23.880 and we're going to showcase some of our multi-platform efforts to make Swift a great choice for a 03:23.960 --> 03:28.280 general purpose programming language. All of the content that you're going to hear today 03:29.240 --> 03:35.240 is a testament to this and the amazing work that the community has driven and all of the work that 03:35.240 --> 03:41.240 the speakers themselves have put into it. I wish I had time to honestly delve into all the things 03:41.240 --> 03:46.520 that have happened within the last year with Swift but I don't. So instead I'm going to pick my top 03:46.520 --> 03:54.760 six so let's begin by reviewing those and also the open doors that we have for you to join this 03:54.760 --> 04:04.200 little this amazing thriving ecosystem. So guess what? There's a new home for Swift. Last summer 04:04.200 --> 04:09.640 the community celebrated Swift's introduction to the world 10 years ago and brought together 04:09.640 --> 04:14.840 repositories for many different sources like the Apple GitHub org as well as the Swift 04:14.840 --> 04:20.440 server GitHub org. There's more work to do this year around governance and operations so 04:20.440 --> 04:31.720 definitely watch this space. So next our second home Swift.org is getting a makeover 04:32.440 --> 04:36.760 as the community has progressed through engineering milestones needed for cross-platform 04:36.760 --> 04:43.320 to cross-platform support and developer experience. Contributors have added new pages and 04:43.320 --> 04:49.000 face lifts to existing ones to reflect this work. The project wants to make it easier for 04:49.000 --> 04:54.840 everyone to use whatever they need for their stack and their experience. For the install page 04:54.840 --> 05:00.760 there's added support for five Linux distros and made the win and we've made the windows process 05:00.760 --> 05:07.320 clear. Each release has a Docker image, turbo and some other option like a static Linux SDK 05:07.880 --> 05:14.520 as shown in the WN example on this slide. Access to Swift will continue to be a focus area 05:14.520 --> 05:25.320 for the project go forward as well as tooling. For tooling at Swift.org slash tools it's a new 05:25.320 --> 05:31.560 page to capture many editors that you can use such as the VS code instructions and support 05:32.440 --> 05:37.800 e-max and NeoVim which definitely helps us curb the debate on which one's better. 05:38.840 --> 05:45.320 So why not both? The team is greatly improved support for source kit LSP as well. 05:46.120 --> 05:53.240 So if you're editor, can plug into the LSP. That's great. The development and the website 05:53.240 --> 05:58.920 improvements are a crucial step in creating a desired experience for general purpose language. 05:59.880 --> 06:05.400 Please feel free to file an issue or a PR or raise a PR against the Swiftline 06:05.400 --> 06:12.120 GitHub org for the website and make these pages even better and add things that are worth 06:12.120 --> 06:24.760 while for you and your stack. I'm breaking news today literally today. Apple's open sourcing 06:24.760 --> 06:41.800 the build system for Xcode and contributed it to the Swiftline GitHub organization. So take 06:41.800 --> 06:49.400 a cruise over to github.com slash Swiftline slash Swift dash build and check it out. 06:50.040 --> 06:57.080 This is a huge step forward for the Swift package manager story. By open sourcing this 06:57.080 --> 07:03.320 part of Xcode, the entire community can help the immediate improvements in the Swift package 07:03.320 --> 07:11.400 manager experience and set a new standard for the thriving ecosystem. A powerful full feature 07:11.400 --> 07:19.160 build system is crucial in any project platform success. And we're thrilled to see this as 07:19.160 --> 07:27.480 a sign of momentum behind this movement. Check out the blog on Swift.org for much more details 07:27.480 --> 07:33.800 than what I have time for today. And also please reach out if you have any feedback, issues, 07:33.800 --> 07:43.080 or questions. Who are the people? There are several work groups and steering groups in the 07:43.080 --> 07:48.440 projects and their contributors. Two groups that have greatly helped the cross-platform 07:48.440 --> 07:55.080 story or the Swift server work group as well as one of our newest groups. The platform steering 07:55.080 --> 08:02.040 group finally abbreviated as PSG. Their mission is to ensure that Swift has a great cross-platform 08:02.040 --> 08:09.240 story while proactively pushing for improvements and gaps of platform support and also supporting 08:09.240 --> 08:16.040 the ones that we already have. Right now, the PSG is busy crafting a set of vision documents 08:16.040 --> 08:23.880 that will outline platform support levels, ABI stability, debugging and more. They're also tackling 08:23.880 --> 08:30.360 some tricky technical issues like finding metadata on out platforms, figuring out the future of 08:30.360 --> 08:36.040 Swift's support and awesome, and making remote to bug support for the next Android reality. 08:39.400 --> 08:44.040 If you have a technical issue that might affect Swift's cross-platform support or any other 08:44.040 --> 08:49.640 suggestion, the PSG absolutely wants to hear from you. You can reach out to them at the Swift 08:49.640 --> 08:56.280 forums. We'll talk about that later and the handle that's on the screen. You'll also hear about 08:56.280 --> 09:01.320 the newly formed ecosystem steering group, so let's work together to make Swift better for everyone. 09:01.400 --> 09:07.800 So, in some of the samples, initiatives that I've just mentioned, above, I said get in touch, 09:07.800 --> 09:13.480 reach out, post on the forums, so how do you do that? How do you contribute, how do you participate 09:13.480 --> 09:25.720 in this great community? Sorry. The first step is typically the forums. That's forums.swift.org, 09:25.720 --> 09:32.840 how many people here on the forums? Nice. All right. If you're just trying out Swift and you 09:32.840 --> 09:38.280 want answers to your setup, building a service with Swift, contributing a feature, giving feedback 09:38.280 --> 09:44.680 about a language proposal, or the newly released Swift 6, or more, the combos are tier. 09:45.880 --> 09:50.040 With the initiatives I mentioned earlier, you'll find the categories and development community 09:50.120 --> 09:56.680 showcase evolution, and more. And then there's obviously the traditional method of raise a PR 09:56.680 --> 10:03.640 or an issue. And of course, help us grow this ecosystem by building clients, libraries, and more 10:03.640 --> 10:17.640 that need it, and or ask us to see what we can do as well. So Eric, you're up. Thank you.