I would vote for docker as well. The last time I had to inherit a system that ran on virtual machines, it was quite a pain to figure out how the software was installed, what was where in the file system, and where all the configuration was coming from. Replicating that setup took months of preparation.

By contrast, with Docker, all your setup is documented. The commands that were used to install our software into the virtual machines and were long gone are present right there in the Docker file. And building the code? An even bigger win for Docker. In the VM project, the build environment for the C++ portion of our codebase was configured by about a dozen environment variables, none of which were documented. If it were built in Docker, all the necessary environment variables would have been right there in the build environment. Not to mention the build commands themselves would be there too, whereas with VMs, we would often have developers build locally and then copy it into the VM, which was terrible for reproducibility and onboarding new developers.

That said, this all comes down to execution - a well-managed VM system can easily be much better than a poorly managed Docker system. But in general, I feel that Docker tends to be easier to work with than a VM. While Docker is far from flawless, there are a lot more things that can make life harder with VMs, at least from my experience.

Do you know how vim has distributions like lunarvim, lazvim, nvchad, etc.? Simply installing something like lazyvim can quickly and easily convert vim from a text editor to a full blown IDE.

I think Gnome needs something like this. A curated set of plugins that are easy to install and maintain compatibility with different versions of Gnome - something that would deal with the API churn in Gnome while maintaining a stable, usable desktop environment.

I don’t know if this is feasible, because I haven’t used Gnome since 2.x, but I think it would really help make it an actual full blown DE.

I doubt that you’re interested in arguing in good faith, but if by some miracle you do care about having an informed opinion before opening your mouth, how would you respond to things like this?

This essentially killed my (EU-based) startup in the project management and collaborate space. Before MSFT bundled Teams with O365 we were rapidly growing and closing enterprise customers in the automotive, energy and education industries with high retention rates. Right around the time the Teams bundling started our retention dropped, churn went through the roof, growth slowed down, we failed to raise our next round because of it and had to drastically downsize the company, causing even more churn (about 80% net churn in 2 years). This move by the EU is good, but too little too late - 99% of the companies that were hurt by this have already shut down, and the ones still running will take years to recover…

Interesting! Sorry, I don’t know why I thought you were using swipe keyboards, it must have been stuck in my memory from reading other comments. I definitely agree that pressing the buttons was a little annoying, but manufacturers could probably make softer buttons if they were willing to put the money into developing them.

Anyway, I really miss the phone I had from about 2008-2010. It had two sliders that moved in orthogonal directions. One of the slide directions revealed a standard 12-button phone pad, while the other had a 4-row keyboard. And yet, I’m pretty sure it was under 1.5cm, so not too large. It was definitely easier to keep in my pocket than current phones!

If it weren’t for reading Lemmy/RSS feeds and a camera, I’d probably be going back to dumb phones for my next one…

I just use the lazy plugin manager (not to be confused with lazyvim) to set up a few plugins for my environment. I followed this guide and just chose only the plugins and configuration that I like. I’ve used vim for over 15 years now but have only used plugins for the past 2-ish years, so I don’t like it when distributions mess up existing keybindings and other default behaviors. Lazy makes it very easy to set up your own environment and I was able to learn how to do it in a relatively short time with some guides and tutorials.

It’s not for the faint of heart, but for me, I think the personal customizability is worth it, as well as not having plugins installed that I don’t want/need. A lot of the time, they’re more modern, but they would also require unlearning my existing habits and learning new ones, which I would rather not do, so I prefer doing it this way.

But I will say that it can be helpful to look at existing distributions to see how they implemented configurations when I run into trouble with my own configurations. Sometimes I’ll steal their keybindings and maybe adjust them to my own preferences. It’s also a great way to explore new functionality and configuration options as well.

But what’s the error rate? I could type at 200 words per minute (even on a phone!!) if I didn’t care about how many typos I was making. And swiping keyboards get confused incredibly easily. The error rates are especially bad when you’re writing words that only use a single row of keys - on QWERTY keyboards for example, try writing something like “type”, and you could get that, or you might get something else, like wipe/write/ripe. Other groups could include things like tip/top, pit/pot, wit/wire and the selected word will be wrong almost as frequently as it’s right. And autocorrect systems can’t really correct for things like when you mean to press enter and hit the backspace key instead. Plus, their suggestions are generally just very stupid. So while buttons take longer to press on physical keyboards, the reduced error rate makes typing speed about the same in my experience.

Plus, with physical buttons, you get tactile feedback, so you can tell when your fingers are slightly off and adjust them, whereas on a flat surface, you have no idea whether you pressed the correct button or not. You have to stare straight at the screen to make sure every press is correct, which is exhausting and bad for your eyesight. I feel a lot more eyestrain from simply typing on phones, whereas with physical buttons, I didn’t even have to look at the screen, and I could look at something else around me while typing. And don’t get me started on how many calls I’ve missed because I accidentally hit the hang-up button, or couldn’t find the accept call button - not a problem when you have physical buttons!

Regarding screen real estate, all you need is a slide-out keyboard. They work great!

There are a few downsides to physical keyboards, but in my experience, they’re far superior to non-keyboard devices. But what can you do - in the 21st century, practicality never matters, it’s just all about aesthetics and nothing else…

Just in case this comment didn’t make it explicitly clear, you can just invoke the python binary inside your venv directly and it will automatically locate all the libraries that are installed in your virtual environment.

To show how this works, you can look at the sys.path variable to see which paths python will search for modules when you run import statements. Try running python3 -c 'import sys; print(sys.path)' using your system python, and you will only see system python library paths. Then, try running it again after replacing python3 with the full path to the python3 binary in your venv, and you will see an additional entry in the output with the lib directory in your venv, which shows that python will also look there for modules when an import statement is executed.

The intent is to allow companies time to implement the change. But if you’ll pardon my cynicism, in practice, what ends up happening is companies just use it as a tactic to delay the implementation and continue recording the revenue.

At the very least they should forfeit the revenue that they earn during the period for this. I’m not sure exactly how the fines work and whether they take this into account, but I doubt Apple is seriously going to use the 12-month period to actually come clean and change their ways. I think they’ll just use it as more time to come up with some new bullshit form of non-compliance.

Excellent news:

At the heart of Monday’s findings are three elements of Apple’s practices, including fees charged to app developers for every purchase made within seven days of linking out to the commercial app.

source

This is, in my opinion, the most egregious non-compliant practice from Apple. They have no reason whatsoever to entitle themselves to purchases made outside their repository just because the software runs on their hardware. It’s also the most asinine set of rules that they established to pretend that they were complying with the DMA.

It’s a bit disappointing that it will take so long before the fines can be enforced, but I really hope that they get the maximum penalty over this because it’s really the most shockingly brazen breach of the DMA’s terms. In fact, I hope that they get imposed the maximum penalty multiple times - the same article I linked mentions that there are two other DMA investigations being launched into Apple, though I don’t know what grounds those other investigations are looking into.

And I really hope Apple gets the message loud and clear: they’re gonna start making less money. And this is a good thing. They don’t deserve it, and they were never entitled to it in the first place. This is what happens when you invent new revenue streams that are criminally worthless.