 Helo! Mae'n fwy fwy ffawr o'r meddwl i chi'n gweithio. Mae'n ffawr o'r meddwl i chi'n gweithio, ac rydyn ni'n fwy ffawr i'n gweithio'r newon. Felly mae'n gweithio'n meddwl i Emba, fel y pionir i'r elfa. Felly mae'n gweithio'n meddwl i chi'n meddwl i'r meddwl i eimbrwysig. Mae'n gweithio'n meddwl i chi. Ngweithio'n cy shirtsiaf gan i ddau pa saysia. Felly mae'n Elderlyvar i eittr ar gyfr temporadaen. Mae ein mawr i, unrhyw iawn,edgellur rhawn, a'i chefof. Mae gennym yma, d neglectedd Alydogur Pegadrur Sarwffer. Mae'r uchydig yn fwy rhoi ychydig arigenous y Gwynb non o gwelio. Beth ydych chi'n sirfa am hyn o'r wylioid ymwylo fyddwn. Mae hyn yn rhywbeth bioligno yn psyllwyr, mae'n byw yn gwbelir am fynd i Llywodraeth, a ddiddordeb o ein bod ybwylliant yw ymwylo sy'n unig o sylwc. Mae y Llywodraeth yn sirfa'r awr yn ymwylo, y byddwn y 5 per cent yn y gafod. Mae'n hynny gweld i fynd i ddim yn 5 per cent. Yn perffennu, y felch ymweld yw'r risu tua sydd wedi ddod. Bydd y fawr o Devatwyr? Cesgwst-en, y dyfodol ychydig o'i ddim yn ffynuig ar gyfer y troi. Felly ddim ddod, rwy'n ddweud yma yng Nghymru. Nghymru yn y Llyfrgell, ac ym Llyfrgell yn y Pwyrnir. Yn ym Mhwysau, ym Llyfrgell yn y Pwyrnir, ond ym Llyfrgell yn y Llyfrgell, ym Llyfrgell yn ddod, ym Llyfrgell yn ym Llyfrgell, ym Llyfrgell yn ym Llyfrgell yn y Llyfrgell yn y pwyrnir, big part of a lot of development in the web community, how we have been a major driver for a lot of things. But first, before we go in, a lot has happened. A lot has changed since the last time I was here. I was on the stage I believe, in 2019, and just after that COVID strike, not too long down the way. And a lot of things changed. perhaps it is not too good. There is a few things that I should point out here. Of course, most folks are here already, but a core team is doing Covid because obviously we are all dealing with different challenges, and a lot of people have lost their jobs. It's been a tough time, we are still recovering as a community as well, but it is very nice to see new faces here as well. i gyd wedi bod nhw'n gwybod� Spikellai. Yn y gweithio'n gweithio, rhai oed yn gwneud Cymru y mawr i Glasolwyr o fenyw bod ni'n gweithio. Mae'n gweithio'r gweithio'n gweithio, rhai oherwydd rhaid i gael datblygaid yno, ac rydym yn y cyfrifiad, yn y gweithio. Ac rwy'n meddwl i'r dweud yn y cyfweld. Ond y ffarn ffaith, rwy'n meddwl i'r dweud, rwy'n meddwl i'r dweud, ond yn y cwrt-tym, y ffordd, rydych chi'n meddwl i'r cwrt-tym, yn y cyfweld, rwy'n meddwl i'r dweud yn y cwrt-tym, yn ymbrwysig, rwy'n meddwl i'r dweud. Yn y cwrt-tym, ym 18 o 19 o'r dweud, ymgwrdd, rwy'n meddwl i'r dweud, roedd, mae'n dweud ar y cyfweld, y rôl yng Nghymru. Yn y cyfweld, rwy'n meddwl i'r dweud, rydych chi'n meddwl i'r dweud, yw hwnnw i'r dweud, dyma yw hwnnw i ddiwedd. Rwy'n meddwl i'r dweud, rydych chi, dwi'n meddwl i'r dweud, ym mwg i'r dweud, yn y cyfweld. Rwy'n meddwl i'r dweud, Mae'r angen ac yn yw i'w adeithydd, gyda'n gynnwys, ond os gydwch i'w gyrdd. Felly,'r angen, y penderfyniadau yn ei wneud yn y cyffredinol rwy'n gynllun. At oedd, roi ddim yn ymddil leol, ac gennym Gydwyd. Jyngom ni'n vidio. Ond os yma'r angen y bydd yn y cyffredinol i'w gynhyrch fel gynhyrchedd, ac rwy'n cael ei ddod o'r gwisgoi, roi ddod o'r fath. Ac wrth gwrs mae'n meddwl. Fylltydd o'r disgloedd, rwy'n dechrau yn ymddangos. Rwy'n meddwl o'r githaidd, ond os rwy'n meddwl o'r githaidd, rwy'n meddwl o'n meddwl o'r githaidd. Meddwl o'r meddwl o'r meddwl o'r webseid o'r meddwl. Ac rwy'n meddwl o'r webseid. Ac rwy'n meddwl o'r webseid o'r meddwl o'r webseid. Rwy'n meddwl o'r meddwl o'r prywodau, ac yn eu moddio arweithio'r community. Rwy'n meddwl o'r meddwl o'r meddwl o'r githaidd, ond ydw i'r link ac yn cyflawn i fynd i'n meddwl o'r disgloedd. Rwy'n meddwl o'r meddwl, o'r cof mor hwn yn gwneud, ac mae'r cyllidaf am moko i wych? Probably a lot of people know him from EMPRESS, but Chris also runs the MBGS Dublin meet-up as well, he's been a mainstay in the learning community and he's also a good friend, so I wanted to give him a shout out, he's been around for quite a while and I think he deserves it as well. ac mae'r llwyddoedd yn y list, Jen! Jen yn hyn o'r energon yn ei waud, rydyn ni i ddim yn cyfnodd yn gweithio gydag y pethau yn y llwyddoedd. Jen yn y pethau ymddi, yn gweld i gydag y pethau yn gweithio. Felly mae'n gweithio'n cyfeirio'r ymddi, mae'n gweld i'n gweld i'n gweld i'n gweld i'n gweld i'n gweld i'n gweld i'n gweld i'n gweld i'n gweld i'n gweld i'n gweld. Ond mae'n gweithio, yna yn fwyloeth ymarfer ymddangos, As aneldo, so generally when we say pioneer, it's like we're referring to, you know, persons who basically make an in-road in something, in this case if we use a Vap for example, we probably would look at being the first to use a technology, as the case may be, or getting into some green field or ever green field. And Ember actually played that role in web development to a significant extent and we will go through some of these examples today. But first up, I'll leave you with this beautiful quote from Tom. It's actually one of my favourite quotes. We had to be willing to commit to the vision and be willing to be ridiculed. When Ember started off, it wasn't the fanciest idea to a lot of people. It also was one of those ideas where a lot of folks actually thought it was going to fail. To be honest, they still think we would fail, but here we are. Still not going anywhere. Let's take a short trip down memory lane. I just want us to have a quick look at this documentary. Just a short clip. There to be a bad idea. You go back and read the discussion threads on places like Hacker News in 2011 and everyone says things like JavaScript apps are broken. Please stop writing these. You guys have got it completely wrong. This is not what the web is supposed to be about. You guys are just abusing the system. You shouldn't be writing as much JavaScript. Please stop writing JavaScript. Honestly, we were iconoclasts. We had to be willing to commit to the vision and be willing to be ridiculed. People really thought that we were off in La La Land and that this was just a temporary fad and that we would be going back to writing web applications the way we had always written them before. Now, everyone is writing apps like that. Now everyone is writing web apps just like we do. I think an interesting one, which is always my favourite one I point out when I speak at conferences about Ember, is the Ember CLI was so loved. Loved so much that the first version of the Angular CLI was actually a fork of the Ember CLI. It's not the fact that they speak about it. It's not something we get credits for, but this was actually a fact. And that's how good the fundamentals that we built in were. So, longevity, how long have we been here? You can pick around on this. Who has any idea when the first version of Ember was released? V1.0. Okay. Yeah, that's close. So, I think the answer to why Ember has been around for so long is multifaceted in the sense that we built right from the beginning, but we've existed today because Ember belongs to this community, not to any one company. And that's a fundamental reason for longevity so far. How old is Ember? I'll go through it, but I actually found a very good clip about Ember GS and our age and longevity, so I actually wanted to share this with you as well quickly. It's been quite a ride. It's old, but it's not necessarily old in the way that is antiquated or anything. We just need to keep working on the right stuff. So, yeah, we're actually quite old. Probably older than you think, but yeah, it's been quite a ride and I'm glad we've actually gotten to this point today. So, this is more like a timeline of Ember releases. The very first version, my cathedral close, the very first version was in 2011, and it's been a significant progress all through. 5,000 was actually released as well, just not too long ago, a few months ago. But down this lane, obviously, this is not the only release of stuff we've had. As you know, we actually, a lot of effort goes into releasing Ember GS, so let's look at a much more representative timeline. On the green side, we have a lot of the releases for LTS, and up above, you have the timeline for major versions of actual releases. There's a lot that goes into releases. There's planning and actual development and a bit of release candidates. We go on stabilisation, we did deprecation warnings, release candidates ready, an official release, and after that, there's also a lot of things that will go on with documentation, community discussion, and then, of course, we talk about maintenance as well. So, making an Ember release, it's not the easiest of things, but this community has always bonded together and got things out, and that's good as the healthy community we have built of the type. And on that note, let's talk about community. When people think about Ember GS outside Ember, what they see first of all is, oh, it's a JavaScript framework. When we think about Ember, we think about the community that we have. So it's not just about the code, it's not just about the infrastructure behind the code, it's also about the people behind the code and that infrastructure. And Ember GS, we have people who are genuinely invested into the project and into the community, sometimes even on a very personal level. Of course, obviously invested on a technical level, but also quite personal level. I think Marco had a good explanation for this, which I think applied to me as well, so I will quickly share a clip from Marco for this one. How do we actually stand out as a community? What's our superpower? We have hired people who said, I want to join your company so I can work with Ember. Many people are strongly invested in the project and in the community on a personal level even, and that makes a big difference. So a fun fact here is, after Covid, when I was actually looking for my national role as well, the first criteria for me was it had to be a company that worked with Ember and was ready to invest in Ember as well. And I think that goes for a lot of members of this community as well. We're not just invested in the project and the fact that we actually use it. I do use a lot of other different projects as well, but the view and reaction depending on what I work on. But Ember is home. Ember will always be home. And let's look at a few things that Ember folks say. Again, full disclosure of the rent or where that I was actually going to put this. That's not the melody. Ember likes to build websites for everyone. Ember enables how to do that because Ember is that framework where beginners and experts can actually work together, collaboratively, regardless of the technical level. Jan says she tries to make THEC more welcoming. Ember is a welcoming community. And as you can see in Mel's closing slides, it was all about encouraging people to get involved in contribution. We are a community that doesn't do gatekeeping. We're focused on a healthy community. It's about the collective and not specific people. So it's a project that everyone can get involved in. Yehuda says sometimes that tells you if you're a beginner, this is for you. And I think that's quite important as well. A significant part of my career I spent also teaching beginners. I ran Codafric, which was a non-profit bootcamp for a while on the representative folks in tech. And the focus was actually teaching beginners. There were a lot of frameworks out there, but I chose Ember because you could actually start getting productive quite easily. The entry barrier was quite low. And I think that's what Yehuda was trying to emphasise here as well. It's a framework that anyone can use. And even as a beginner, you will feel confident to actually be able to get productive whilst using Ember. Leah isn't here, so I'll go ahead. I will not trade building open source software with this community. I think a lot of people here will probably share that same sentiment as well. Because of how tightly meet we are and how committed we are to the project, you find a situation where people who are actually invested in Ember, like Mark was saying, actually invested in Ember on even a personal level. So, here we have John, John Will Durham, he's the CTO at Forest, and when asked why Ember, I have a quote there. We needed something out of the box, something that was stable and reliable. I think this also summarises Ember to a very good point. I will play a short clip that explains his thought process and why they choose Ember. Audio out. We will get back to that audio eventually. As a community moving together, I will just summarise what John said in his audio clip since I couldn't play it out, but it basically spoke about selecting Ember as the web development tool when the company decided to move to web in 2015 for some specific reasons. It was stable, it was reliable, and you were quite sure that in 10 to 15 years from that time you wouldn't need to have a total rewrite of your app. You were quite confident that you could actually get developers to come on board and actually get productive as soon as possible. Above that, the last bit which you mentioned in the audio was the fact that although people say, oh Ember is a small community, it's not so huge and there's not a lot of people in it, it was one of the main attractions for Forest because it meant that they found a community where they knew their voice could be heard, where they knew there could be a part of the collective as opposed to one which they were just in the air pretty much. Now, when we say we move together, just to tie into what John said, when we look at longevity and we see how we've managed to do it, there's a lot of things that go into moving versions, but I think some of the under mentioned bits are the code mods and guides. A lot of work goes into guides educating us how to move our apps, but also the code mods. There's probably a few people who might not know what code mods are, but usually they come quite handy when you need to migrate an app. To a large extent, they help you to do all the heavy lifting and simplify it that way to a very large extent. This is actually quite useful and Ember does invest in this as a community because we see the importance of making sure that the apps that you write today can actually leave the test of time. So, in conclusion, you don't have to go to your manager and say, we need to stop feature development for two, three years. We need to do a rewrite of Ember. That's not how Ember.js works. That's not how it was built to work. And I think this is why it stands out. It's a beacon of stability, a beacon of reliability. As a community, we have been the drivers of that, making sure that Ember is what it is today. I know when we talk about Ember, we always look at Yehuda and Tom, and of course they have been at the forefront of it. But every member of this community has been a significant part of what Ember is today. We should feel good about ourselves, honestly, because it's not an easy fit. We should absolutely be proud of ourselves. And to address the question of, you know, every time I speak at a conference, we always have that same thing. Like, oh, how long is Ember going to stay? Is Ember going to die? I was really happy today, you know, Yehuda going to Polaris and Ed giving the long low down embroider. But Melanie had a very good summary for it about Ember, and I think this is the node I would finish on. All the good ideas will end up in Ember. It's just a matter of time. And that is true. All the good ideas always end up in Ember. It's only a matter of time. Thank you so much. Thank you to us.