1,168 karma · joined July 31, 2016
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.
https://hn.algolia.com/?query=Flatpak%20%E2%80%93%20A%20Secu...
The tone and varied assortment of alleged issues makes me feel like he started by deciding that Flatpak was bad, and then found whatever he could to support his view.
"It investigates and explains, in a critical and clear-eyed way, examples of people working toward solutions. It focuses not just on what may be working, but how and why it appears to be working, or alternatively, why it may be stumbling. Using the best available evidence, it delves deep into the how-to’s of problem solving, often structuring stories as puzzles or mysteries that investigate questions like: What models are having success reducing the dropout rate in public schools? How do they actually work? What are they doing differently than others that’s resulting in a better outcome?"
https://medium.com/@soljourno/what-is-solutions-journalism-c...
The instant value is providing channels for developers to ship apps to their users without either side having to mandate the OS that the other uses. Right now, even well-funded projects like Visual Studio Code have to pick and choose which Linux distributions and versions that they package for.
They don't provide packages to the main repositories for Linux distributions, partly because the release cycles are so wildly different. I don't want Debian stable to ship a completely new base system every few weeks, but the release cycle of my Web browser is a new version every six weeks.
In the ideal Flatpak world, I can run Solus or whatever distribution I choose, and the app developers that I rely on can not care about distribution market share, and just target Flatpak runtimes.
The challenge is going to be to ensure that Flatpak repositories and the Canonical App Store (the server end of snap) enforce good enough legal and security checks once vendors have started using them.
> unless there's some particular piece of software you need which isn't supported.
Lots of people need to run very specific pieces of software for their work, or their pastimes. If you want to switch to Linux, you have to look at all of the software that you use, and replace the products that don't have Linux versions. If you can't, then you can't switch.
If you want some assurance, CERN are deploying restic:
Yes, this is why I made Open Source and open formats an absolute requirement when I started looking at journaling software. The content is irreplaceable.
After trying several things, I found that Joplin does everything that I need for journaling and note-taking. I made a point of donating to the project the equivalent of what I would have paid for a commercial offering.
It's an Open Source note-taking app that stores Markdown and Web clips in SQLite databases, and can sync between instances using a variety of options, including generic WebDAV services. It has desktop and mobile versions, so the information is available to me everywhere. I still keep my emails on IMAP and my Website in Git, but I will draft any long text content in Joplin, and then just copy the text into the final location.
By definition, version control is for collaboration, so using a less well-known version control system impedes the regular work of your project.
There's also the issue that version control is integrated into lots of other software. Everything now supports Git and Subversion, but support for other VCSes is rarer.
This is kind of unfortunate, because it makes innovation hard. Projects like pijul exist to try to move the state of the art forward, but it's difficult to see how they will gain adoption.
The lead developer goes out of his way to support less-popular systems, such as *BSDs and Mercurial, so if you work with more niche technologies, you may find Sourcehut a good home for your projects.
Feel free to tell us how your professional ethics as a lawyer enabled you to make change at Microsoft before you were general counsel and president, Brad. Or after you got the top jobs.