Well, then the answer is obvious, no? You can, but there can be some compatibility issues. And changing your operating system is not a criminal offense. As far as Google internal policies, you would have to ask them.
Uh, you don’t have to work at Google on order to do that. Most Chromebooks can be unlocked to work with Linux with a little bit of work. And you wouldn’t be at risk of going to jail for that. Worst that could happen is you void your warranty. But it’s not a “real crime” or anything like that.
Anyway… I figured out a workaround in my script. By focusing one of the windows on the current workspace before I open a new tab it seems to make it the preferred window. It’s not foolproof, sometimes it still selects one of the other windows, but it’s close enough.
Here’s the script in case anybody needs it, should work with any editor that has some sort of -tab and -window options if you grep for the correct window name:
NixOS and to a lesser extent nix package manager is great for this. Write a config for your entire setup, which will take a long time, but then you can carry that config with you through any and all future machines, and have every one of them setup just the way you like from the beginning
I would highly suggest using NixOS for something like this, however if you don’t want to/can’t the following should apply to pretty much any other distro
Most applications in Linux save their config in ~/. config/ or ~/.configname , if you copy these files and directories over to your new machine all your old settings should persist (this won’t copy applications themselves but will copy their settings for when you reinstall them)
(though be warned this is a messy way to do it if you just copy absolutely everything without thinking, some settings you probably don’t want copied over)
Is anyone actually running modern Linux on Itanium? I have never in my life even heard of anyone using those chips. I find it hard to imagine anyone still using them that isn’t running something legacy.
It’s still a supported architecture in Gentoo. I expect it will limp along there for as long as there is viable kernel source (current or LTS) and at least one interested maintainer. So if you have an Itanium machine lying around, you can install a current Linux on it. As long as you’re willing to follow a long set of instructions, anyway.
The last chip was manufactured 3.5 years ago and the last serious user was probably several years before that. Obviously no one’s running Itanium with modern hardware.
But just because the hardware isn’t modern, doesn’t mean the software can’t be modern. Tonnes of people run the most recent Linux kernels on 15 year-old laptops, so why not 10 year-old servers? Itanium is only for the hobbyists these days, but so what? Hobbyists have done a good job of ensuring modern Linux can run on 40 year-old 68k. Itanium can theoretically be done, too. It’s just a question of whether the hobbyist community has enough of the right people that can actually maintain it.
Hobbyists, especially hobbyists in itanium are an incredibly small market share. Their time is much better spent on what people, and most importantly businesses (who pay their bills) use.
It wouldn’t surprise me if there were still a few production Itanium systems in server rooms somewhere, running some obscure or bespoke proprietary software that can’t be migrated to anything else. There are other more arcane systems still being limped along in businesses around the world, for some frighteningly critical applications in some case.
Itanium support being dropped probably has a handful of admins panicking, but in the eyes of the kernel developers it’s a case of “put up or shut up”.
running some obscure or bespoke proprietary software that can’t be migrated to anything else
this is the primary issue – everyone looks at corporations when talking technical debt, but so many medium and small businesses are limping along on so called “enterprise” solutions they were sold a couple decades back and are now completely locked into proprietary formats for which support ended last decade
I’m a mech E in the medical field. We’re consistently understaffed. If I validate an Excel worksheet in Excel '08 or a Python program in 3.5 with a specific version of NumPy, we’re probably sticking with those versions for a while. Every time I bring up re-validating with the latest version, keeping one old system running the old software requires fewer resources than me or a colleague re-validating.
My whole department is stuck on one version of Python because that was the most recent version when I had an emergency project and developed a data analysis algorithm. We validated it, then as new members were added to my team, they needed a copy, so we had to keep using it. I’ll probably re-validate it to the next Python release. It’s not only unit tests, or we could automate validation. Unit tests are a tiny part of validating software for making medical decisions. And software that directly runs a medical device (like firmware on an insulin pump) is an order of magnitude more rigorous than what I do.
Side note: there are people who somehow root their insulin pumps and run algorithms on them. There’s a group that can get a PID control loop on an insulin pump that has a more simple control scheme on it (because that’s how the FDA approved it). The company has been trying to get approval to use PID control in the US for years.
The AS/400 platform is still alive and actively maintained by IBM so I’m told, although I think it goes under the Power Systems and IBM i brands now. I know several business still using them, with development teams still coding with RPG etc. Apparently there is also reasonable ecosystem of middleware to interface with more modern systems, and some sort of *nix compatibility layer to run more modern software on the platform.
I’ve never touched one myself, but they are keeping a few greybeards I know in steady work.
We currently support Turing (RTX 20XX and GTX 16XX) and later GPUs. We plan to eventually support hardware as far back as Kepler (GeForce 600 and 700 series) but those are currently poorly tested at best and missing a few essential features.
They might have changed the OP to fix it in the past hour, but for me the “screenshot” is coming from the social image for the link on the post itself. Clicking through the link gets to the actual article.
If you open Emacs in daemon+client mode (run emacs --daemon once, then emacsclient to open the window), buffers that you open in one client will be available on all other clients, even concurrently. Judging from a quick test (on hyprland), it also seems to open the file in the client located on the focused screen, but does not automatically open a new client if there is one already running on any screen.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.