Like someone else said, if I have to dig through settings to do that then I might as well use Windows. It's better to use something that doesn't even have snap in the first place via another distro than play cat and mouse with Canonical.
I had my tmux customized to the point I forgot how to use it on a clean install which is a problem when I'm sshing into a server.
I wish it had better defaults but now I run it as is. After a while you get used to it. The only thing I always have to change is the mouse scroll and my brain cannot retain the exact command.
Volunteer to be the official image maintainer - I had emacs-nox and (screen) installed fleet wide for my own utility :)
I had a friend that even had his public keys added to the /root/.ssh/ but I didin't go that far -I didn't even put my own .emacs out - but I at least could use good tools to look at the tcpdump output or giant log files if needed. "Eight Megs and Constantly Swapping" is not that big of a deal anymore.
And if people want to just use some default open source image, just point out that in modern cloud environments, you don't want each node to customize itself, you want to pre-run that process one time per node type in your "directed graph of image delta pipelines" which takes the input image and publishes the cloud ready app-specific images (with your DNS configs, LDAP integration, whatever, plus emacs/neovim and screen/tmux :)
This will definitely work, but it's not really even necessary. Just have some pre-connect script, that checks if the host is already "configured", and if not, then one-shot some Ansible playbook (or bash even) that installs what's needed. Use /tmp if root is not available. Also works for Kubernetes, though there we have better options.
I think of this as the curse of Emacs. Infinitely configurable, thereafter entirely unique in the universe, which can be a double edged sword. See too (maybe it's the same thing) The Lisp Curse.[0]
Total opposite. I adapt to the defaults meaning I almost never customize anything. Tmux? Game controls? UI look? Default. I am almost never met with surprise unless I am sitting in front of someones OCD config.
I've hit this problem multiple times. The approach which finally eased this pain point for me was to take care to not overwrite any tmux defaults with my config, and only add non-conflicting configs (new shortcuts, styling changes, etc.) That way, if I need to use tmux on a new or unfamiliar machine, the core functionality is still present, and I just miss the candy that comes with customization.
For example, leave the existing prefix binding (ctrl-b), but also add something nicer for day-to-day use (ctrl-space or similar).
> I had my tmux customized to the point I forgot how to use it on a clean install which is a problem when I'm sshing into a server.
I had the same issue with gnu emacs… but at some point i lost my very custom configuration when the disk broke… i resorted to use a mostly-vanilla emacs :)
I can't speak for the parent, but I rarely login to the same remote server twice and don't want to need to set things up and clean them up anytime I do. This is why I try to keep my stuff as close to vanilla as possible. If anything goes wrong on a server and someone sees I have a whole bunch of dot files to customize my config, it becomes a red herring that I have to spend time explaining away.
No, wanting to keep things vanilla when you're dealing with lots of random servers is a valid concern. Just because you can solve this with shell scripting doesn't mean you should.
Sometimes I ssh into a server as a specific user (e.g. as the "app" user that is used to run a web app), sometimes only root is available (probably not best practice, but it's not like I can or want to fix it myself).
In any case it's not practical to carry your dotfiles everywhere you go. Changes are also a hassle to propagate
Linux was created by an European. And there are many European distros. Even Canonical is European.
But that's besides the point. The point is no company owns linux so you're not tied to big tech even if they are the biggest contributors to the kernel.
We may see Canonical or other commercial Linux vendors come forward with a government or enterprise-flavored solution for all this. But the important thing to keep in mind is that they're not selling Linux per-se. As the GPL prohibits this, these companies sell support for their Linux distro instead. That revenue goes into improving Linux and maintaining their distro (e.g. Ubuntu). But even with all that money changing hands, that they do not own Linux, the Linux kernel, or any other shred of GPL licensed stuff.
Selecting your own mute words for your timeline is the best part about Twitter. The algorithm changes have been pretty bad in the last few weeks though.
FYI the “mute by keyword” feature exists both on Bluesky and Mastodon and I use it extensively. I don’t use Threads but a quick search tells me it’s available there too.
Now you know, and you don’t need to use twitter anymore!
I don't know how this blocking works. A couple minutes ago I could access this link but now I can't. It's happening with another website too. It's like an intermittent blocking today.
> It's a plugin that I'm not using, don't care about using, and cannot see any conceivable use for.
> No-one wants this.
So, fun fact about earth: there are lots of people on it, and some of those people aren't you, and some of those people who aren't you actually have desires that are different from yours.
I think it makes the planet a pretty fun and interesting place, but it also does mean generalizing from "I don't want this" (totally fine! Awesome! Makes sense!) to "no one wants this" is usually not very productive.
IntelliCode has 60M downloads and is the 11th most downloaded extension for all of VS Code. Also consider that there's 6 official Python-related extensions above it that could all be rolled into one, and Copilot just above it which (to my knowledge) is installed by default in newer versions of VS Code.
Just because it doesn't affect you personally doesn't mean it affects no one. You aren't in fact the centre of the universe.
I'm guessing that's 60 million people that don't have a small child that can just type stuff that looks kind of like code but doesn't actually work like code.
I was about to comment to say that unless Valve is prepared to invest significant effort into an x86 -> ARM translation layer that's not going to happen but a quick search for "linux x86 to arm translation" led me to an XDA article[1] proving me wrong. The recently announced Steam Frame runs on ARM and can run x86 games directly using using something called FEX.
Now we just need to be as good as (or better than) Apple's Rosetta.
Apple Silicon actually has microarchitectural quirks implementing certain x86-isms in hardware for Rosetta 2 to use. I doubt any other ARM SoC would do such a thing, so I doubt third-party translation will ever get quite as efficient.
They are. You're mad that Valve isn't militantly enforcing Linux-native games, which is nonsense. The OG Steam Machine did that and was DOA.
Thousands of game studios are gone now, and supporting their software is important legacy work. You don't have to appreciate that, but I do. I do not give the faintest fuck about the opportunity cost you bemoan towards native UNIX games when I do this. That's your problem, not mine.
I have seen VR headsets trying to break any significant market share since 1994, they have never been anything other than a niche, with customers having too much money to throw around.
reply