I would like someone to explain what are the perks of having ngx-translate over building your own translation service. The reason I'm asking this is, for now, I don't see the difficulty of building a translate pipe, which from the top of my head would consist of:
- A JSON file or an exported constant with my translations.
- A service that imports that file and has a method to translate a given string (if found in the object).
- A pipe that uses that service (for template usage).
Of course, using ngx-translate would save me some time, but considering the basic requirements of my app, I think it's a fair trade off.
Also, wouldn't my own minimal translate module reduce the size of my app a little bit?
