“Speed trap” cameras are an entirely apt name. The solution to speeding isn’t cameras, or patrols, or administrative controls, it’s traffic calming, and that reduces capacity, so it’s not considered. The trap is driving on the road at speeds they seem to be designed for, with speed limits significantly lower.
Fuck cars, but fuck cops more. We don’t need to live in a panopticon. These cameras are a step in the wrong direction, and while I don’t think the person who cut them down is doing the right thing for the right reasons, they are doing the right thing.
Hey at least we got the CEO of a Saudi oil company heading up the climate talks. I’m sure that he’s perfectly willing to set aside his own personal interests and take one for the team and reduce his profits by leaving Saudi oil in the ground, and encouraging (or even requiring???) everyone else to do the same, right? Right?
Honest question, not being catty or anything. Why is this news, exactly? This is a nearly every winter occurrence to get below -50C in Yakutsk, the average winter day is -42C. (It also gets up into the 90s during the summer, Yakutsk is a wild place.)
This would be roughly equivalent to a news article saying Detroit is down to 10F today, i.e. colder than normal, sure, but not really beyond the pale for a December day.
Honestly asking because I’m just wondering if this is the start of the “there can’t be global warming because it’s cold somewhere” coverage for this winter season, or if this is intended to be a fun TIL article for the lucky 10000.
Put a shell script in your PATH named inkscape with the following content:
<span style="color:#323232;">#!/bin/sh
</span><span style="color:#323232;">
</span><span style="color:#323232;">flatpak run org.inkscape.Inkscape
</span>
Note that you can use a local folder in your home directory to house small executables and scripts like this, so you don’t have to touch your system config. I generally recommend using something like ~/.local/bin and add it to your PATH via your Shell’s RC file.
You may be surprised to learn that they didn’t all run out until 2013. UEFI had been around for 7 years by this time, and Microsoft was doing patent enforcement actions against Tom Tom during this time period.
Sure, they’re expired now, but not at the time. It was supposed to be an open standard at the time.
<span style="color:#323232;">flatpak run org.inkscape.Inkscape "$@"
</span>
To forward all of the arguments to the script. Note that this might be a bashism, so you might need to change your hash bang to /bin/bash as well. Double check though.
(An easy way to check if something is working as you assume is just prepend the line with echo.)
Just make sure you back up any important data before wiping your own hard drive. And yeah, Steam handles a lot of the weirdness of running windows only games pretty well automatically.
However it throws hundreds of people through the equally discriminatory criminal justice system, and allows car insurance companies to jack up rates. Functioning even more effectively as a tax on being different than regular cops do. It also creates a financial incentive for the government not to fix the underlying cause of the problem of speeding.
Wishing and hoping for people to be better than they are isn’t a solution. Just because traffic calming is more expensive, that’s not a reason to not do it. It is something that needs to be done if you want to break car dependency.
If “D” is physically on the same hard drive, then you’ll probably want to back it up before installing. Technically, you can manage to do it without screwing everything up, but I would not trust myself to. It’s always a good idea to have backups anyway.
Also, user files typically reside on C by default and it takes some effort to put them on a different drive. Things like Downloads, Documents, Pictures, etc. so it’s worth checking that before wiping as well.
Additionally, you’ll probably want to format your “D” drive to a Linux native filesystem (eventually, after you back it up, because formatting results in data loss). While Linux does support NTFS quite well, it’s not perfect, and your data would probably be safer on ext4 or f2fs (depending on if you have HDDs or SSDs) (or zfs or btrfs is you’re into COW filesystems).
In Linux, you have all of your files mounted to a single “drive” called /. Everything is below /, which is called the “root” of your filesystem.
Typically, user data is stored in “/home” and this resides in the same directory structure as the rest of your OS, but on most systems it’s on a different filesystem or even on a different drive entirely. This is because in Linux it is routine to put a “D” drive just in a folder. On my computer, I have several of these mount points defined, so the different types of data don’t get mixed around, and I don’t have to worry about downloading too much bullshit affecting my computer’s updates.
Another NixOS user (and minor package maintainer, if it matters) here. Essentially, NixOS is actually rather simple to write a configuration file for a particular program once you get the knack for the nix language and learn how to workaround the sandboxing. I would actually consider it substantially less involved as compared to (for instance) creating your own Debian package.
However, getting to this point will take a bit of effort, and this step is more or less obligatory to use software on NixOS, whereas it generally isn’t (but still is a good idea) on other distributions.
The single killer feature that convinced me to move to NixOS is the ability to very easily keep separate development environments separate. For instance, if you’re working on multiple dev projects that have different minimum requirements, and you want to ensure that (for instance) you don’t accidentally use features from after boost 1.61 for project A, because that’s the stated requirement, but you need features from boost 1.75 in project B.
In a normal distribution, in order to set up an environment that has the proper version for project A you’d need to set up a chroot, a virtual machine, a complicated set of environment variables in a bespoke script with custom installation paths that you need to set up manually and remember to source, or just install a newer version of boost and rely on continuous integration to catch it if you screw up.
In NixOS, you can set up different shells which all reference the exact correct version of the libraries required for every project, you can have them installed simultaneously and without conflicts, and there’s even a shell hooking program that will automatically load and unload this configuration when you change directories into and out of the project folder. It makes managing many different projects much easier. It’s like a better version of venv, but for everything.