azure-cli VS sciter

If you don't use AWS, you can usually find CLI tools for other major cloud infrastructure services, such as Azure CLI or gcloud CLI.

Yep. They also do not notice, that Fedora 37 is using Python 3.11 already, and can't merge the fix for azure-cli for 2 months to fix the compatibility issue: https://github.com/Azure/azure-cli/pull/24109

References: https://github.com/Azure/azure-cli/issues/20476

In the spirit of moto, it actually looks like quite a bit of the groundwork is available for someone to take a swing at an Azure version:

* the cli uses the python SDK: https://github.com/Azure/azure-cli/blob/azure-cli-2.38.0/src...

* which uses autorest: https://github.com/Azure/azure-sdk-for-python/tree/azure-mgm...

* of what appears to be an OpenAPI-ish spec: https://github.com/Azure/azure-rest-api-specs/tree/fda2db441...

Isn't Azure CLI written in Python?

Even though it seems like a pretty good little hack – this is not supported. The Portal would also bug out and refuse to display Environments correctly if the resource were created with “Other” workflow:

> wondering if css and svg could be used as abstraction over graphics and UI libraries

There's another project called Sciter that uses CSS to target native graphics libraries: https://sciter.com

> I wonder how hard it was to implement css. I've heard it can be pretty complex.

It was hard, but the biggest barrier is the obscurity of the knowledge.

Text layout is the hardest, because working with glyphs and iterating them in reverse for RTL is brain-breaking. And line wrapping gets really complicated. It's also the most obscure because nobody has written down everything you need to know in one place. After I finished block layout early on, I had to stop for a couple of years (only working a few hours a week though) and learn all of the ins, outs, dos, and don'ts around shaping and itemizing text. A lot of that I learned by reading Pango's [1] source code, and a lot I pieced together from Google searches.

But other than that, the W3C specifications cover almost everything. The CSS2 standard [2] is one of the most beautiful things I've ever read. It's internally consistent, concise, and obviously the result of years of deliberation, trial and error. (CSS3 is great, but CSS2 is the bedrock for everything).

[1] https://gitlab.gnome.org/GNOME/pango/

otherwise, if we have only retained mode as in browsers, we will need to modify the DOM heavily and create temporary elements for handles.

[1] https://sciter.com

I've still never used it but I've long been curious about Sciter:

https://sciter.com

These bullet points are exactly what I did in Sciter (https://sciter.com)

- Windowing

-- Tabs

-- Menus

-- Painting

-- Animation

-- Text

-The compositor

-Handling input

-- Pointer input

-- Keyboard input

- Accessibility

- Internationalization and localization

- Cross-platform APIs

- The web view

- Native look and feel

On top of that DOM and CSS implementations to achieve declarative UI. And JS as a languuage behind UI - declarative in some sense way of defining UI behavior.

I'm not sure if it can support all the libraries but yes it can be used to make desktop apps. Theres also Sciter.

https://sciter.com/