I spun up a test server of Pleroma recently. Following just a few people, 0 people following me AFAIK, I did join a few relays so my federated timeline is populated. It is currently showing 360MB RSS and the CPU load maxes out at ~50% of a single vCPU.
Note also that recently a fork called Akkoma[1] sprung up. If one is looking to self-host, it might be worth looking into this vs Pleroma (I don't have a horse in this race, was just doing some research on different ActivityPub servers).
Not the parent poster, but there seems to be some misunderstanding. The GitHub issue creator explained that they're getting two different behaviors depending on C compile flags. That's already not "the same behavior as Go" AFAIK.
> What kind of behavior do you expect?
Defined behavior, I assume. If V uses C as an intermediate, and the generated C code invokes undefined behavior, then V can not guarantee "no UB" in that case at all. It is completely up to the C compiler what happens. Even if the compiled app behaves "properly, like Go" with the specific C compiler, with the specific flags, on that specific machine, does not mean this behavior is defined and consistent.
Are there plans for docs to be updated? The 0.3 release notes claim:
> Option and Result are now separate types: ?Foo and !Foo respectively. Old code will continue working for 1 year and will result in a warning/hint.
Yet, doc/docs.md still states:
> V combines Option and Result into one type, so you don't need to decide which one to use.
Is there an up-to-date doc, or how does one find out more about these types? I found parts of the RFC overhauling the error handling [0] pretty bizarre, so I'm interested to see how the implementation turned out.
That's absolutely fair, I don't think either the parent or the NixOS devs implied in any way that it should be the right fit for everyone or 100% of the Linux distro market share is the end goal.
For me, the benefits outweigh the quirks of the language. As my alternatives to manage multiple machines consist of: wonky Bash scripts, similar tooling but bolted-on on top of the distro and with no built-in rollbacks (Ansible, Puppet, etc.), or trying to get everything right manually, Nix does not seem like the worst out of this bunch.
The Steam client works natively on Linux. It ships its own version of Wine, called Proton and many games work well. They are doing lots of work to get the remaining games working in preparation for the launch of Steam Deck.
I am a backend engineer who has spent the last 4 years building real-time online advertising systems in .NET. However, I am looking to change up both the domain I work in and the technologies I employ while at it.
At this point you're just arguing for removing all mechanical skill from competitive games.
Impede the gameplay however you want, in pure mechanical aspects a program will always have the benefit of perfect accuracy and near-zero reaction time (as opposed to the >200ms average of a human)
The indexing operator [] does bound checks, the method `get_unchecked()` does not. If you need the extra speed at the expense of safety, you can do it, but you have to consciously choose this trade-off. Unlike in C, in Rust safety is opt-out.
I've been running my own email since about 8 months ago. I have Google's MX (that I used before) on backup (with a lower priority). Will not help me with every sort of fuckup possible, but it will at least deliver the mail if my server is down.
Oh, the UX horror!