![]() ![]() We used Gitter, which was fantastic for “I need help right now!” situations, but had a useless search system and no way of pinning extremely useful and relevant answers to common problems, so while I was banging on about either setting up a forum of some sort to let us assign moderators to flag and collect the hidden gems and FAQs, Angular 2+ shot ahead, as it was years before this discourse forum was created.Īs a result of this we missed the peak adoption period, despite having a significantly better framework, fantastic community, and significantly better core modules for real-world tasks such as validation and I8N. We also had a complete lack of centralised community support. ![]() He decided to make it completely unopinionated as far as the loaders were concerned, so we had a framework where the first thing a user was confronted with was a choice of six loaders, and most non-core modules (and some core ones) had a nightmare scenario where they supported some loaders but not others.Īngular took a simpler approach, choosing WebPack and standardising on TypeScript, meaning new adopters had a single documented process, so even a complete novice was able to get up and running quickly. Unfortunately Rob made what I felt was a fundamental mistake when he started Aurelia. ![]() While Aurelia 2 retains many familiar parts, developers love convention over configuration, intuitive templating, flexible binding system. We want to avoid a situation like Angular faced where they dumped an entirely new version of Angular and offered no easy migration path. The only comparable simplicity is Svelte, and Svelte is a library, not a fully-fledged framework like Aurelia.ĭevelopment is also slower because we want to ensure very few differences between Aurelia 1 and 2. I am biased, but I’ve found that Aurelia has had the most effortless onboarding and learning curve of any other framework. I know many projects had the same difficulties with Webpack 5. The only turbulence with Aurelia 1 was Webpack 5, a tooling situation, not exactly a framework one. Because Aurelia is just primarily HTML and Javascript, there are very few instances I can think of where Aurelia doesn’t work with emerging standards. I would love to know what people mean when they say “industry standards” because Aurelia is one of the most standards abiding frameworks around. I have apps that have been in production since 2016 that never die. We’ve improved our communication and have a tried and tested release process, which has resulted in the alpha being very stable.Īs for Aurelia 1, it’s a solid framework many are using in production. Work on Aurelia 2 has been done in the middle of the pandemic. Despite the perceived slowness, a lot of work has been done in 2021. Just like larger companies with larger development teams, everyone has been affected by the lockdowns, restrictions and changing landscape around the COVID-19 pandemic. I don’t speak on behalf of everyone else in the team, so my perspective will differ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |