12/23/2023 0 Comments Babeledit alternativeSo I did what anyone with a bit of common sense would have done, I told him that Angular i18n sucked, that it failed to deliver the promise of easy-to-use-yet-powerful that they wanted Angular to be. I was a bit speechless, I was there about to tell him that I had quit my job and wanted to work full time on my lib, and he was asking me to stop working on it. I wanted to ask him some advices on how to turn this into a profitable OSS project, but before I could tell him about my plans, he told me: “Ah Olivier, I wanted to talk to you, you’ve got to stop working on your library, Companies come to us and want to do i18n, but they only talk about your library, we want them to use our solution because it’s more efficient”. It was in December 2016, I had 2 months left at work before I was free, and I went to the conference NG-BE where Igor Minar from the core team was present. I knew that it was possible because ag-grid had done it and they were very successful. I decided to quit my job and see if I could make a living out my open source work. It solved a lot of use cases, and was simple enough to be usable in a few minutes. My library was so popular that I wanted to work on it full time because I could see that it was a necessity for the Angular community. The official i18n implementation was super complicated (and still is), it didn’t support json, code translation, changing the locale without reloading the app, and you needed multiple app bundles (one per locale). It was still a side project for me, but I was using it at work because we had finally started using Angular in production and needed to translate the app in multiple locales. I rewrote the whole library and made it possible to replace some parts (loader, parser, compiler, …). I decided to rename this library ngx-translate and to use npm scopes in order to deliver a modular experience. Some time later, the library ecosystem started to settle and Angular was stable, they decided to drop the name Angular 2/4/… in favor of just “Angular”. It was also a time where the framework was still in beta, and there were no real guidelines for publishing libraries for Angular, it was so hard to do it that not a lot of people were trying and I didn’t have any real competition on i18n for a long time. And I guess that the code was good enough and easy to start with. My library quickly became popular for various reasons (no real alternative, I had a good reputation from my work on ocLazyLoad, my appearances in Angular Air and my talks at conferences). I asked my good friend Pascal Precht if he was interested in porting angular-translate from AngularJS to Angular but he wasn’t and told me that I should do it. It had worked for me on AngularJS with my library ocLazyLoad that was a huge success (2600 stars) and whose core principles were finally integrated into the framework in v1.6.7.Īt the time I was looking for a way to translate my Angular apps and found out that there was nothing in Angular to do that (i18n wasn’t even existing in the framework). When I started this library 3 years ago, I wanted to learn Angular and I thought that working on an open source project would be the best way to do that. You can skip that part if you don’t care about how this library came to life Hello everyone, I’d like to discuss about the future of this library and get your opinion on my plans.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |