k32

4 ms·

1.
by k32 6y ago
This matches my experience. I played it for 50 hours on PC (and I am a very lazy gamer, typically I get tired of everything in one hour), and didn't encounter any breaking bugs. Overall, it's a very enjoyable story-driven game, al
2.
by k32 6y ago
> Use Signal to transfer messages and files https://blog.erlang.moe/2020-12-01-acme-messenger.html
3.
by k32 6y ago
Sluggish UI, dark patterns, OS rebooting when it feels like it, OS waking up during the night for some shenanigans, surveillance, nagging, ads... I don't know how people can have so little self-respect to use windows. Feels like living
4.
by k32 6y ago
> If that was your problem, you should've said so instead of spinning it up into an entirely different security problem that plainly did not exist. It was merely an answer to your remark about "this fork wasn't meant for e
5.
by k32 6y ago
> This is precisely why it's important that Twitter calls out when things are stated as fact without evidence. Twitter is a platform for stating things as fact without evidence. 120 (or whatever it is now) character limit is not sui
6.
by k32 6y ago
Twitter: https://joinmastodon.org/ https://pleroma.social/
7.
by k32 6y ago
> Erlang's gnarly build system It's actually fine, thanks for a remark.
8.
by k32 6y ago
> requiring you to specify the URL of the required packages and its hash beforehand. ...a different hash. You see, I naively think that a checksums should not be overwritten when they doesn't match.
9.
by k32 6y ago
> First of all, the fork obviously isn't there for general consumption. I didn't know that when I installed a package called "rebar3" and spend some time trying to understand what's wrong with my build. Oh, my ba
10.
by k32 6y ago
> Except that your anecdote is completely misleading given that the patched version was intended for creating Nix packages. You could've just used the unmodified version instead. The package was called rebar3, not rebar3-nix or some
11.
by k32 6y ago
Thanks for a constructive comment.
12.
by k32 6y ago
> Any widely used distros do this. I've yet to encounter another distro that deliberately breaks 3rd party software the way Nix did it to rebar3 (before it was reverted). > Plus, the statement that you have to patch all packages
13.
by k32 6y ago
> I don't find myself patching stuff all the time, and would hate to go back to half-assed leaky-abstraction kludges like Ansible. Speaking of half-assed kludges, NixOS itself is a held together by duct tape of scripts patching she
14.
by k32 6y ago
> Oh ffs really? Yes, really. This PR partially reverted this behavior (or rather made it less intrusive): https://github.com/NixOS/nixpkgs/pull/54115/files , but from there you can easily track &quot
15.
by k32 6y ago
Nix is a nice research project, but after playing with it for ~6 months and contributing to nix-packages, I came to conclusion that (in my case) it's not suitable for production nor development, and now I manage my personal machines wi
16.
Beam VM Telemetry Collector(github.com)
4 points by k32 6y ago|0 comments