Re:Fluent 1.0: a localization system for natural-sounding tr...
by Andrex on Wednesday April 17, 2019 @09:37AM
(#19682400)
Why fluent-react and not (in addition to) fluent-web-components? :(
[ Parent
| on HN ]
Re:Fluent 1.0: a localization system for natural-sounding tr...
by Vinnl on Wednesday April 17, 2019 @09:48AM
(#19682494)
One advantage I can imagine is that you can prerender the React components, outputting e.g. plain HTML. With tools like e.g. React Static, that means you can somewhat ergonomically generate different static websites for different languages, avoiding the runtime costs of looking up the correct strings.
Re:Fluent 1.0: a localization system for natural-sounding tr...
by cbenz on Friday April 19, 2019 @05:37AM
(#19698158)
Using the Svelte JS library (https://svelte.technology) you can have both: server-side rendered components [1] and compile to web components (custom elements) [2]
Another advantage is that the components compile to vanilla JavaScript, so we don't rely on a runtime library to run the application.