Microsoft Fast Design
11–20 of 216 posts
Re: Microsoft Fast Design
#12Re: Microsoft Fast Design
#13Re: Microsoft Fast Design
#14Re: Microsoft Fast Design
#15Allow me to ask the obvious question: How does Fast compare against React, Angular, VueJS, etc.?
https://www.fast.design/docs/fast-element/observables-and-st...
> The arrow function bindings and directives used in templates allow the fast-element templating engine to intelligently react by only updating the parts of the DOM that actually change, with no need for a virtual DOM, VDOM diffing, or DOM reconciliation algorithms. This approach enables top-tier initial render time, industry-leading incremental DOM updates, and ultra-low memory allocation.
> When a binding is used within a template, the underlying engine uses a technique to capture which properties are accessed in that expression. With the list of properties captured, it then subscribes to changes in their values. Any time a value changes, a task is scheduled on the DOM update queue. When the queue is processed, all updates run as a batch, updating precisely the aspects of the DOM that have changed.
That's neat.
Re: Microsoft Fast Design
#16Took a quick look: It has limited components. It isn't fast on my mobile device. Some components appear to be broken. Why would I ever use this?
Re: Microsoft Fast Design
#17Re: Microsoft Fast Design
#18Looks very flexible but the presentation and default design is horrible.
Re: Microsoft Fast Design
#19There are plenty of these libraries. Can someone tackle the hot mess css is? Give me one way of doing things. Css breaks do much shit for me to the point where I don’t want to code
Re: Microsoft Fast Design
#20According to the instructions:
> The exports of this package can generally be thought of as un-styled base components that implement semantic and accessible markup and behavior.
> it exports parts and pieces intended to be composed into Web Components, allowing you to implement your own design language by simply applying CSS styles and behaviors without having to write all the JavaScript that's involved in building production-quality component implementations.
Which means... if I want to make my own components, I can just take this package and don't worry about making broken components. Since the core HTML/JS is properly taken care (by MS, hopefully) I can less worry about re-implementing keyboard access, or things like accessibility which is hard to do properly. This is IMO huge, and should be more universal.