sjellis
Joined 10 years ago
Joined 10 years ago
It's a shell that is actually built for structured data, taking lessons learned from PowerShell and others.
The main sponsor of WINE is CodeWeavers, who have been paying folks that work on WINE for a very long time, and are involved in Proton development:
They sell a supported version of WINE for Linux, macOS and ChromeOS, as well as providing engineering services to clients like Valve.
dsq CLI - https://github.com/multiprocessio/dsq DataStation desktop app - https://datastation.multiprocess.io/
Two alternative CLI tools that I looked at:
sq - https://sq.io/ octosql - https://github.com/cube2222/octosql
Honourable mentions to:
Miller - https://miller.readthedocs.io/en/latest/index.html Dasel - https://daseldocs.tomwright.me/
These don't use SQL.
VisiData is also amazing for data navigation, although it requires some effort to get the model:
The USP of Hatch is that it uses the latest generation of Python standards and tech under the covers, so you have a unified tool that's less quirky than previous ones. Poetry and pipenv predate some of the improvements in Python packaging, so had to develop some things in their own way.
There's a discussion here:
Hatch aims to do what Poetry does, but is strictly compliant with Python standards.
https://aws.amazon.com/sdk-for-rust/
There are people at Microsoft working on a Rust SDK for Azure, but it's explicitly a volunteer effort with no support guarantees at the moment:
https://github.com/Azure/azure-sdk-for-rust
These days I probably would not look at any language that did not have SDKs for AWS and Azure, for similar reasons.
It supports various types of file stores for syncing between devices. I've used OneDrive and WebDAV. The project has also recently launched a cloud service for people who want to sync between devices but don't want to set up a network file store.
TLDR: Microsoft wanted .NET developers to only use tech from Microsoft, used various tactics to achieve that, and people got the message. If you wanted to use modern tech or develop innovative stuff, .NET was not a comfortable place to be.
Microsoft have tried to move past that, but never really have. .NET has never had a healthy Open Source eco-system.
It does the stuff that you need without excess weight, the look and feel is flexible enough that you can make it look like other systems if you prefer, and the small development team consistently put out new releases to fix and refine it without any drama.
AWS use it for their Linux cloud-based desktop service, probably for these reasons.
Ubuntu MATE is a great showcase for what can be done with MATE. It's arguably more user-friendly than the main Ubuntu, with the MATE desktop and quick-start features like a well-curated software selector.
Red Hat explicitly will not ship a component unless they can build it from source and update it, and have confidence that they can continue to do so for the life of the OS version.
That's what being a responsible "enterprise" operating system vendor means.
The bugs cited in the article are already fixed in the code, so I don't hold those against it.
I did have an issue that was my fault, encountered one genuine bug, and was disappointed to find that there's some work to be done before third-party tools can use it as a Docker replacement:
https://github.com/containers/podman/issues/11397
I agree that Podman is not yet a complete replacement for Docker on macOS, but the experiment was successful enough for me that I intend to try Podman instead of Docker on Linux servers.
This really should be the term for projects that are perpetually releasing 0.x versions.
Maintainers are free to release their software under whatever terms that they wish, but if you actively encourage people to use your software and do not want to maintain backwards compatibility, then IMO, you should be very honest about that.