fluentui

https://github.com/microsoft/fluentui see also https://fluent2.microsoft.design/

Microsoft Fluent UI reminds me Ant Design and Ant Vision ecosystem https://ant.design/ https://antv.vision/en Fluent UI React Roadmap https://github.com/microsoft/fluentui/wiki/Fluent-UI-React-Roadmap Hooks, Charts, etc everything https://github.com/microsoft/fluentui/tree/master/packages/ Seems Microsoft is trying to unify dev experience around React https://github.com/microsoft/fluentui/wiki/FAQ---Fabric-and-Stardust-to-Fluent-UI "Our end goal is to unify these things. One styling solution, one theming solution, one set of utilities, one set of component authoring patterns, one set of components, one documentation site." Is it mature? Worth to invest time and follow in coming years?

Thanks for the recommendation. I've used VMware's Clarity professionally (https://clarity.design/) and it's pretty bad (design and code wise). There's also IBM's Carbon (https://carbondesignsystem.com/); I love its design but it's incomplete in some areas. Microsoft has Fluent UI (https://github.com/microsoft/fluentui) which I have never used.

There's Microsoft's Fluent UI: https://github.com/microsoft/fluentui

Blazor, while a good effort, is still an experiment. Microsoft Office etc. are React apps, and has one of the most maintained React libraries: https://github.com/OfficeDev/office-ui-fabric-react/ I will believe the Blazor effort if they start rewriting Fabric UI components with Blazor.

Office Fabric React has some good React + TypeScript code that has good testing which is very necessary with the level of commit activity into a shared component library. https://github.com/OfficeDev/office-ui-fabric-react

Hey, I work on Yammer, and I'm one of the contributors to this project. YamUI is a cross-team effort between our Design and Frontend teams to create drop-in components for Yammer.com that have strictly-enforced style and behavior. As @gregod said, it is based on Office's awesome Fabric project: https://github.com/OfficeDev/office-ui-fabric-react/ The project is just us working in the open. We're not trying to push this as a new component framework for others to use, and we probably don't have the bandwidth to support external consumers, but we're happy if people can learn from it.

You might also want to look at the very comprehensive office 365 react components from MS which is build on. https://github.com/OfficeDev/office-ui-fabric-react Meant for developing Sharepoint/Office Apps but released under MIT License (Only the custom Microsoft Fonts are restricted but easily replaced)

As a professional web developer who uses TypeScript (disclaimer: MS employee, not on the TypeScript team), I don't find that it impacts in-browser debugging. TypeScript has the ability to generate map files, but we don't use it because issues with our tooling. I don't miss it though, because the generated JavaScript is pretty close to the TypeScript (we target ES5, if you can target ES6 the mangling is even less). Once you learn the common patterns (methods get mapped onto the prototype, fat arrow functions get compiled to regular functions with a _this variable) it's pretty straightforward to debug in the browser. The dev inner loop is maybe a little slower with the compile step for us, but it is possible to use TypeScript's automatic compilation with webpack and Node and all the latest hotness and get automatic build/deploy/refresh (see

Office uses react already: https://github.com/OfficeDev/office-ui-fabric-react