I'm getting very annoyed by things that don't mention they only work on Mac until you go to install them.
1,391 karma · joined March 16, 2018
I'm getting very annoyed by things that don't mention they only work on Mac until you go to install them.
[1] https://blocksandfiles.com/2023/04/13/seagate-22tb-disk-capa...
Adding it to Atuin will take a bit of work to keep it from being too brittle, so it hasn't yet been done.
Feel free to open a feature request before I do.
I haven't used this for anything complex, so it may need a little bit of tweaking.
[0] - https://jackson.dev/post/a-portable-nix-shell-shebang/
In fish for example, it's as easy as the following (using zoxide query)
complete -c z -f -k -a "(zoxide query -l)"But X requires Sliding Sync on the server, which is still a separate service to run alongside the homeserver and doesn't have a stable API. I am increasingly disappointed with how centralized Matrix is becoming, since AFAIK there isn't really an alternate client close to the same level of quality as Element.
I probably would've made all of the same decisions myself though, so I don't blame them I'm just a bit disappointed in how it's shaking out.
I long for the day that I can just pay XX cents to read a single article with minimal fuss, but at this point I don't see that happening.
I use an obnoxiously custom Linux setup for my personal devices, but I still try to push anyone who will listen to try a Chromebook.
The 2038 problem comes about because of overflow in a 32bit signed int, so the top byte (smallest clock hand in this case) effectively only has 7 bits instead of 8, when it goes above 0x7F is when the int is interpreted as negative.
The easiest 'fix', if it's even necessary, would be to make the smallest hand go all the way around in 128 ticks instead of 256. But really this micro blog post could just use an explanation of that to aid the visualization.
The largest performance difference is probably that real threads must have a larger startup cost, as they will need their own copies of some resources (like stack space) that green threads can share. There's not really a way around that without changing how you define a platform thread.
I pay for a year at a time for ease of use since they wouldn't save payment info when using port forwarding. And now since I last bought a years worth in May they turned off port forwarding and now make me drop the next 8 months of prepaid time if I'd want to use this feature (that I've been waiting for for years).
I'm still not sure if I like the login situation for Tailscale (allowing only 3rd party auth) but I understand why they do it.
EDIT: Turns out I can't use it yet since you have to buy Mullvad through Tailscale. I bought a year of Mullvad in May (they can't save payment info for port forwarding) and in the 4 months since they've removed port forwarding[2] and won't let me use my remaining credit for this integration.
[1] https://jackson.dev/post/replacing-tailscale-with-nixos/
Consumers will likely keep these devices for many years and want to just upgrade the whole thing at once, and the fact that both the display and computer are on the cheaper side makes this feasible to make the usability tradeoff worth it. A pro use case would want to be able to upgrade the very expensive display and the very expensive computer at different rates. The upgrade cycles don't really line up.
[1]: https://www.pcworld.com/article/823939/vertical-tabs-in-fire...
So you can still seed, it just won't be as usable.
The CS101 explanation of a Vector that copies values around whenever it exceeds its capacity is incorrect in many cases.
When I worked on perf at Windows, I vaguely recall someone telling me that the Windows impl doesn't do that for some reason. I'm curious if Raymond will cover why.
I occasionally use this for convenience, even though I pay for YT Premium.