kevingranade

The climb to mid game is definitely the part of the game that works the best, I have some plans for a more extensive endgame, but it's going to be a while.

The stated use case for the perf improvement was "yes(1) may be used to generate repeating patterns of text for test inputs etc., so adjust to be more efficient."

Source: https://github.com/coreutils/coreutils/commit/35217221c211f3...

I've personally used it for generating repeating text and filling disks in system testing, so I appreciate it being faster at those tasks. I also sometimes use it as a signal generator for a hacky load generator, like so:

  yes | xargs -L 1 -P NUM_PROCESSES -I {} curl SOME_TARGET_URL > /dev/null

This doesn't benefit from being faster per se, but I appreciate it using less CPU since I want to give curl as much system resources as possible.

A detail you seem to be missing is that you are not limited to a shell script. The shell sets up the pipeline, but the members of the pipeline can be written in arbitrary languages and just have each stdout linked to the next processes stdin.

As a result you can process very large volumes of data and consume (not waste, consume) significant system resources to perform your processing.

On one hand, I would LOVE for all interview processes to be annonymized, as I think this is the only way for them to be truly gender/ethnicity/religion/age/etc neutral.

On the other hand, if submitting a photograph or video of the applicant violated EEOC Guidelines, in-house interviews, which are the vast majority of interviews, would also be in violation, so this is an untenable position relative to the status quo.

Setting aside their predictive power, questions related to logical reasoning are most definitely job-related in an interview process for a technical position that explicitly requires logical and deductive reasoning skills.

No one seems to have picked up on the strategic impact of the proposal, it neatly excludes many of the more sympathetic pro-patent entities from the picture, in particular the pharmaceutical industry and hardware manufacturers. They needn't bother to oppose it, because it has no effect on them, whereas they may oppose further barriers to granting patents on principle just in case it affects them.

Personally I'm not extremely in favor, as I'm anti-patent/copyright in general, but it makes sense for someone whose primary goal is software freedom.

Status.net/OStatus uses a similar PUSH model, basically it scales with number of followers, and yes, if you have thousands of followers the load will be significant. As a data point, I've been running a status.net instance since last December, during which time I've had 50-80* followers, have made an average of 12 posts/day, have followed 100-190* others, and my instance has transferred a grand total of 10,279MB * over that entire period.

followers and followeds gradually increased over the duration. I have this number handy since the connection is reverse-proxied via pagekite.net, which is metered. Over the last few months, I've had all static content offloaded to another server, which reduced the bandwith used, I'm not sure by how much.

PageKite (pagekite.net) is another solution for self-hosted from a household. plug