A QA engineer walks into a bar and orders a beer.
They order 2 beers.
They order 0 beers.
They order -1 beers.
They order a lizard.
They order a NULLPTR.
They try to leave without paying.
Satisfied, they declare the bar ready for business.
The first customer comes in an orders a beer. They finish their drink, and then ask where the bathroom is.
The bar explodes.
Anything they acquire and leave alone seems to do well (like those projects you list) everything else is almost comically bad. Made worse by the absolutely atrocious support that they've outsourced to Tata Consultancy.
Minor nuance, the radio button itself seems to work. My guess is what's happening is they're only initializing the UI state when you first interact with it, which blows away the radio button state.
Normally radio buttons can't start fully uninitialized like that, so I assume that's the real bug.
I really enjoy using GitHub, TypeScript, and VS Code. These are some my most favorite tools.
But Azure DevOps and Microsoft Teams make me think that the Microsoft engineers working on these products absolutely don't care and they probably don't need to care, and the companies using these products also don't care.
Popularity and dominance are criteria for success. Their success, but not necessarily your success. If the product is by Microsoft you have to look more than twice if it's a good product or if it's close to self-sabotage when you use it.
There are already many opensource ui components / libraries like bootstrap, tailwind, chakra, material, semanticui, etc, What's fast offering that other don't?
>FAST provides an innovative theming system called Adaptive UI, which builds design system properties that designers use every day directly into every component.
Then the next block is an example where you can change neutral color, accent color, saturation, border radius, stroke width and density of all components in a frame on the fly.
47 comments
[ 3.5 ms ] story [ 126 ms ] threadhttps://en.m.wikipedia.org/wiki/Microsoft_Development_Center...
The first customer comes in an orders a beer. They finish their drink, and then ask where the bathroom is. The bar explodes.
> FAST web components are built on the core technologies of the web to work in any scenario.
This is Microsoft's response to bug reports.
… the checkbox label is completely broken (clicking it does nothing at all)…
First impressions are this is buggy and not well tested.
* StackOverflow ranked VSCode is as #1 popular IDE.
* And #2 is Visual Studio.
* GitHub maintains absolute dominance.
* Azure ended Q4 as the fastest growing cloud
* ChatGPT owns AI
Microsoft is clearly going nowhere /s
That radio button is broken.
Normally radio buttons can't start fully uninitialized like that, so I assume that's the real bug.
But Azure DevOps and Microsoft Teams make me think that the Microsoft engineers working on these products absolutely don't care and they probably don't need to care, and the companies using these products also don't care.
Popularity and dominance are criteria for success. Their success, but not necessarily your success. If the product is by Microsoft you have to look more than twice if it's a good product or if it's close to self-sabotage when you use it.
I wish I could make a clever break-fast pun here.
You and me both :/
That it's a design system?
When you go to the page:
- first line: "Adaptive..."
- second line: "The adaptive..."
- third line: "...adapt..."
Then the next block:
- "flexible and adaptable"
>FAST provides an innovative theming system called Adaptive UI, which builds design system properties that designers use every day directly into every component.
Then the next block is an example where you can change neutral color, accent color, saturation, border radius, stroke width and density of all components in a frame on the fly.
>like bootstrap, tailwind, chakra, material, semanticui,
In order to adapt all components you have to
- in bootstrap edit SCSS variables
- in tailwind edit tailwind.config.js and probably use CSS variables for the utility classes you use
- in chakra override global CSS styles in the style object
- in material v3 define your own baseline and dynamic color schemes
- in semantic UI override CSS in your theme.config.
But it seems only tailwind with CSS variables allows to change styles on-the-fly, i.e. more than just toggle between light and dark mode.
*edit:* formatting