Might not look like it, but they're clipped in.
So you'd roll off the ledge, crack your head against the rock face and then bleed out, NOT fall to your death ๐.
Might not look like it, but they're clipped in.
So you'd roll off the ledge, crack your head against the rock face and then bleed out, NOT fall to your death ๐.
I know climbers who would absolutely do this and tell no one. Adrenaline can be its own reward.
Yeah there's no such thing as polticially neutral.
There's bipartisan, there's a political average, there's politically apathetic, there's political abstinence, but not "political and objectively neutral".
It has random side effects that break cli tools (tools that are not even installed with ASDF)
The more versions you add, the slower it gets. And it can get really slow (that issue was opened in 2018, and it is fixable).
It's got many "well it works on my machine" problems. And the author said that's a "wontfix" design choice. That's fine for the author, it's FOSS. But it means my workflow is going to randomly break and I just can't have that when it's my job.
Pkgx, Devbox and nix avoid all these things.
It definitely still is. I use nix on the daily and specialize in old versions seach; Just because it's very possible doesn't mean people don't find it to be a pain point.
With the right tools (which are not easily found in the docs or on Google) finding one old version is fine. Running one old version is flawless. But mixing that old version with newer versions of other packages causes problems because of the nix LD_LIBRARY_PATH issue.
Actually Lazamar's is kind of out of date. Here's the best sites for it:
And I made an interactive Cli tool that let's you search all four of those simultaneously!
Use this! nvs --install ruby@2
(I'd attach the gif but lemm.ee doesn't support images)
I had your exact complaint. And it only took me 3 years and hundreds of hours of learning nix to make that tool ๐
Btw, while it solves version search, fair warning you're going to immediately run into other usability problems. I use nix every day but I don't gaslight people into thinking it's usable.
Full disclosure, I use nix (not devbox) for all my stuff cause I care about hardcore reproduciblity.
I'd say 3 things
To establish a routine, I had to let go of everything else. Like, the checklist for the whole day was just the routine and it stayed that way for weeks. Sounds like you're in a good position to do this which is great to hear.
Shape the environment to enforce a routine.
Alarms are annoying. They can tell you something but not make you want to do it. We can do better. For example in the morning, using a sunlight alarm clock and a space heater will actually make you want to get out of bed. (Use a timer socket with the space heater to have it auto turn on)
Doing the exact opposite night also helps; use the thermostat clock to make it cold and have lights auto-turn off using timer sockets. It's difficult to keep working when it's really cold.
I find treating the weekend the same as weekdays is helpful. E.g. don't take a break on the weekend.
Recommended Books:
It's been a while since I last studied neurology. I couldn't find the paper I was hoping too, but I found a different one that honestly might be more what OP was looking for anyways.
Note: the gambling task is probably the most relevant in terms of distorted logic and decision making.
I was lucky for a while too, since you can also get lucky with dynamically linked libraries. Sometimes they find the new version of the .so (from other packages) and it works, but sometimes it finds a system .so and works until there is a system update. Which ruins the whole reproducability thing, although using the sandbox options of nix can help with this.
Nixpkgs is better about patching the RPATH now, but that's the thing; using old versions is like going back in time. We'd need to go back in the git history and also patch the super old version.
There are tools like nix-ld which can help, but they need to be setup and they've got edgecases too.