4 ms·
Microsoft recently wrote a blog post saying they would be rallying around a single component library. [1] > What’s in a name? A lot it turns out. And we have a
by sholladay 6y ago
Microsoft recently wrote a blog post saying they would be rallying around a single component library. [1]
> What’s in a name? A lot it turns out. And we have a lot of them. Too many? We hear you and agree. That’s one of the key reasons we’re simplifying our story. To collectively rally around a single UI library for our web components—Fluent UI.
Yet, here we are, and they've released another component library. They really seem to love these things. It's not entirely clear what the difference is between them.
1: https://developer.microsoft.com/en-us/office/blogs/ui-fabric-is-evolving-into-fluent-ui/ https://developer.microsoft.com/en-us/office/blogs/ui-fabric...
- fassssst 6y agoFluent UI is the one the Office team is standardizing on. FAST is from the Edge team and used for their settings pages. That’s life at BigCo for ya.
- flowerlad 6y agoThe components part of Fast has moved to Fluent. See https://github.com/microsoft/fast/#fast-components-msft https://github.com/microsoft/fast/#fast-components-msft "This package has been moved to FluentUI and has been renamed to @fluentui/web-components"