aequitas (u/aequitas)

aequitas commented on Ban me at the IP level if you don't like me boston.conman.org/2025/08... · Posted by u/classichasclass

brianwawok · 5 days ago

I doubt that’s on purpose. The bad guys that don’t follow robots don’t bother downloading it.

Never assume malice what can be attributed to incompetence.

aequitas · 4 days ago

Bad guys might download the robots.txt to find out the stuff they don't want them to crawl.

aequitas commented on Helix Editor 25.07 helix-editor.com/news/rel... · Posted by u/matrixhelix

munificent · a month ago

> I have muscle memory of Vim.

I respect the preferences of others but I think that most people overfit for muscle memory. I've switched OSes/editors/IDEs many times in my career. Every time, the first day or two I feel like "This is the worst fucking thing ever, I can't even type God damn it I want to set the computer on fire and become a farmer."

But... that passes. After a couple of days, I have new muscle memory and it's fine. It would be a shame to let a few days of discomfort control which software I use when software varies in its other capabilities so much more widely than just keybindings.

aequitas · a month ago

But there is only so much room for muscle memory or context to switch between. I tried Helix for a while, got used to it and I really liked it, especially the noun verb order being different from vim. Seeing what you have selected before performing the action. But for me the problem is that vim is everywhere I go or will eventually end up. All my servers have vim. Every server I need to randomly debug has vim or vi. So my muscle memory for vim keeps getting refreshed as well. And switching between the two constantly is just a pain. I could take along Helix to all these servers. But that is not practical nor do I need all the features Helix uses. Or I would miss specific feature which I then also have to bring along.

Now I’ve settled with Zed as desktop editor/IDE and still use vim on remotes. The context switch between a desktop app en cli is big enough that it’s never a problem. I don’t even use the vim bindings in Zed.

aequitas commented on Can your terminal do emojis? How big? dgl.cx/2025/06/can-your-t... · Posted by u/dgl

oneeyedpigeon · 2 months ago

Great. A feature that makes Apple's default Terminal better than iTerm or WezTerm. Just what I didn't need!

aequitas · 2 months ago

But iTerm2 supports imgcat which lets you just dump full images into the terminal output.

aequitas commented on How I use my terminal jyn.dev/how-i-use-my-term... · Posted by u/todsacerdoti

huimang · 2 months ago

Hi Jyn.

"i don't use Nix partly because all my friends who use Nix have even weirder bugs than they already had and partly because i don't like the philosophy of not being able to install things at runtime."

The first part is mostly true. Nix installs things in a readonly store (/nix/store) so regular dynamically linked binaries don't work. Packaging takes a different approach and when things break, it can be difficult to work around. That said, I've run NixOS for over a year now and I find the benefits are far preferable to these downsides. It's not often I run into bugs, let alone show-stopping ones. What is annoying is how many tools are distributed without the source, so I have to run patchelf on them or use something like nix-ld.

As for the latter part, I think that using Nix will change that mentality. (Note that you can do `nix-env -iA $pkg` but it's not recommended). See, I don't even install things like rust at a global level anymore. I can always do `nix-shell -p $pkg` for an ephemeral shell if I need that, or I encode that dependency directly in the project's flake.nix. If I end up using that program a lot I will make the effort to add it to my NixOS config.

aequitas · 2 months ago

I use Nix exactly because it doesn't allow installing things at runtime. This keeps me from hitting surprises where the runtime environment changes from under me. Containers can partially solve this problem as well but have their own usability issues.

Nowadays I start every project with `nix flake init --template templates#utils-generic`. And put everything in that related to the project. I even had some projects where I had to put 'ssh' as a pinned package as it was used in some scripting and the default macOS and Linux versions accepted different flags.

I also do love that I can do something like `nix run nixpkgs#nmap` on any machine I'm on to instantly run a program with worrying where to get it from. I also use this feature in some of our projects so you can click a link in the admin web interface which is a 'command url' for iTerm2[0] like: `nix run gitlab.com/example/example/v1.0 -- test http://example.com` which will prompt to run that specific version of the command in your terminal, without have to checkout the source repo. In this case it is to rerun specific task locally for debugging purposes.

[0] https://iterm2.com/documentation-command-selection.html

aequitas commented on uv: An extremely fast Python package and project manager, written in Rust github.com/astral-sh/uv... · Posted by u/chirau

espdev · 2 months ago

> Just a few months back I said I would never use uv. I was already used to venv and pip. No need for another tool I thought

Really? :)

requirements.txt is just hell and torture. If you've ever used modern project/dependency management tools like uv, Poetry, PDM, you'll never go back to pip+requirements.txt. It's crazy and a mess.

uv is super fast and a great tool, but still has roughnesses and bugs.

aequitas · 2 months ago

Pip-tools+requirements.txt helped me survive the past few years. I also never thought I needed uv, but after all the talk about it I gave it a spin and never want back. It’s just so blazing fast en convenient.

aequitas commented on The Zed Debugger Is Here zed.dev/blog/debugger... · Posted by u/SupremumLimit

mort96 · 2 months ago

I was interested in Zed, but lost all interest when they started integrating "AI". I'm tired of "AI" everywhere.

I'll just stick with Neovim until something better comes around. Which probably won't happen until after the "AI" bubble bursts.

aequitas · 2 months ago

I find it very easy to avoid the AI feature in every day Zed usage. Sometimes they do come in handy though. But nog often.

aequitas commented on The Zed Debugger Is Here zed.dev/blog/debugger... · Posted by u/SupremumLimit

laserbeam · 2 months ago

I'm very happy to see work on the debugger. This is the main feature preventing me from switching full time to zed.

Unfortunately, "here" is not accurate. Not having a watch window, a stack trace view, and no mention of data breakpoints in the announcement still keeps the "beta" tag. I know those features will arrive eventually, but what is described is definitely not sufficient for 97% of my debugging sessions.

I would also have liked to see more in the announcement of multiple simultaneous debug sessions, and on how multithreaded debugging is planned. There are really cool things that can be done with multithreaded debugging further down the line that I'd be interesting in hearing about (like how RemedyBG has a DAW-like UI for freezing certain threads, or hitting one button to "solo" a thread and freeze all others).

aequitas · 2 months ago

I have to try out the debugger yet. However I share your sentiment but for the Git feature. The basics are there but it is just not complete yet to fully replace my current git workflow. Hope they keep focus on that as well.

aequitas commented on Apple has announced its final version of macOS for Intel tedium.co/2025/06/09/appl... · Posted by u/mdp2021

ksec · 3 months ago

At home, I am still on my Early 2015 MacBook Pro running latest macOS with OpenCore patcher. As long as you don't use Safari because Cloudflare think you are a bot it is mostly fine.

The problem with all MacBook after my generation is their keyboard sucks. They have some variant and tiny improvement every year but it still sucks. The 1.5mm key travel is about the minimum I could take. Both butterfly and new scissors, despite giving them time I never quite come to terms with it.

But I guess this is one more year of macOS and perhaps two more for Safari + security. 2028 will be the final deadline.

aequitas · 3 months ago

I have a mid 2015 Macbook Pro 15", also with OpenCore. Running just fine. No issues with Safari and Cloudflake. Only thing is the battery was mostly dead. I replaced it with a iFixit diy battery kit, but that one died completely after just 2 years (out of warranty of course). Probably the controller board, as the cells were nowhere near empty. Now I have the choice to replace it with a cheap battery from unknown source or yet another iFixit one which costs almost the price of this laptop second hand. But I have lost trust in this iFixit product as others seem to have the same problem. Just sucks to have perfectly fine hardware locked behind another expensive battery repair.

aequitas commented on Apple announces Foundation Models and Containerization frameworks, etc apple.com/newsroom/2025/0... · Posted by u/thm

WhyNotHugo · 3 months ago

The ground keeps shrinking for Docker Inc.

They sold Docker Desktop for Mac, but that might start being less relevant and licenses start to drop.

On Linux there’s just the cli, which they can’t afford to close since people will just move away.

Docker Hub likely can’t compete with the registries built into every other cloud provider.

aequitas · 3 months ago

There is already a paid alternative, Orbstack, for macOS which puts Docker for Mac to shame in terms of usability, features and performance. And then there are open alternatives like Colima.

aequitas commented on Yes-rs: A fast, memory-safe rewrite of the classic Unix yes command github.com/jedisct1/yes-r... · Posted by u/ericdiao

3eb7988a1663 · 3 months ago

That reddit thread has some amazing benchmarks.

The GNU-yes

  $ yes | pv > /dev/null
  ... [10.2GiB/s] ...

The way I (not a C programmer) would have written it

  void main() {
      while(write(1, "y\n", 2)); // 1 is stdout
  }

  $ gcc yes.c -o yes
  $ ./yes | pv > /dev/null
  ... [6.21 MiB/s] ...

aequitas · 3 months ago

  yes &

A few times is still my favorite way to push a cpu to max temperature for testing. Used it a lot to detect faulty Core 2 Duo MacBook back in the day. They would short circuit some CPU sensor due to thermal expansion or melting of the wire insulation. Yes was an easy way to get the CPU’s hot enough.