Yes, it would actually be interesting to just have a bwt pass which does no compression, so we can then try lots of post compression options.
I've been thinking about adding support for this kind of stacking to DACT [0].
Readit Newsrkeene2 commented on Bzip3: A spiritual successor to BZip2 github.com/kspalaiologos/... · Posted by u/tosh
rkeene2 commented on Sixos: A nix OS without systemd [video] media.ccc.de/v/38c3-sixos... · Posted by u/transpute
So, systemd is like "doing Linux services the Microsoft way"
It's more like doing Linux services the UNIX(TM) way since it's more similar to other UNIX service managers like SMF from Solaris or SRC from AIX in the integration -- NT's service manager requires an active event loop which responds to messages.
As an aside, the reason I don't like systemd is because it's inferior to its UNIX counterparts -- especially SMF -- for system management.
rkeene2 commented on How many Alpine packages can you install at once? (2024) naff.dev/blog/all-the-pac... · Posted by u/todsacerdoti
Although that is true, it'll presumably be hard to use them all since some of them will trample each other's symlinks.
It doesn't really make that much sense, but I've always wanted a sort-of hybrid lazy Nix store. Rebuilding my NixOS machines take a long time since I like to have my preferred software configured and installed at the system level mostly, but there's some stuff that isn't so essential that it needs to block the upgrade. So I've thought about a hybrid solution where the packages would get built in the background and you could have some kind of magic FUSE system to block while the derivations are built or pulled from Hydra.
If you wanted to, you could combine this with the idea of installing every Nixpkgs package. It might even sort of make sense, as long as you ditch the "also work on them in the background" part... although it makes the surface area of your system absurd.
AppFS (my project) and CERN VMFS do this, if I understand you correctly.
rkeene2 commented on Show HN: Boulette - Protect you from yourself (even as root). github.com/pipelight/boul... · Posted by u/jean_dupont
What I really want is a way to get a read only root shell. I do a lot of work on a "traditional" multi-user unix host, where hundreds of scientists share a powerful computer. I often need to become root to look at files. I want to be able to do that without the ability to screw anything up.
I've used seccomp in the past to create a read-only root.
I created a seccomp DSL to make this kind of stuff easier [0] (an example of dropping network access is at [1])
[0] https://chiselapp.com/user/rkeene/repository/bash-drop-netwo...
[1] https://chiselapp.com/user/rkeene/repository/bash-drop-netwo...
rkeene2 commented on Ghost jobs – 7 in 10 hiring managers consider them morally acceptable stackoverflow.blog/2024/1... · Posted by u/zh3
Agree to disagree.
My experience is that it’s quite a bit more nuanced and complex than that.
The uncertainty works both ways. I don’t know at the moment I open a position when or if someone qualified will apply or be hired. I don’t even know with precision exactly when positions open up. How long is the grace period for taking down open job positions after one is filled? 3 days? 1? An hour? Just the mechanics of filling out HR paperwork means there’s lag between reality and the job posting. If I’m constantly opening/closing positions (as one would be at a team size of 500) there’s just as much chance of a position actually being open and not having a listing as the other way around if I’m attempting to always update the posting.
I do know that a chunk of applicants will be baristas, uber drivers, and construction works, another chunk will have keyword-optimized resumes that are incomprehensible, and many more will simply be too junior for a role because everyone is aiming high hoping to make to their next move. Employers are absolutely flooded with garbage.
Similarly, when trying to hire I spend most of my time on it between resume reviews, phone screenings, and actual interviews. It’s incredibly labor intensive to hire good engineers and/or technical managers. I’m working just as hard as the applicants.
I don’t use vague language. If it’s the case that I don’t have a position open at the moment of a phone screen, I tell an applicant when and how many positions I expect to have open.
And it’s not just the time spent on the process. It takes weeks to months to restart the process after it’s shut down. You have to update job descriptions, train your talent team on what to look for in resumes, train engineers on how to do technical interviews, and may sure they are “calibrated”. If they are out of practice they fumble the interviews and the company looks bad to applicants, and they tend over-estimate an interviewee’s performance because they don’t have a recent point of comparison to work with. This means I have to do 5-10 throw-away interviews to grease the wheels. If I fully stopped a pipeline and treated each position as a special snowflake, and everyone else in the world did the same, it’d just create even _more_ overhead for all parties involved.
I’m not saying it’s a good system. But humans are human and on balance any system is going to be gamed. There’s no way around that. For every one applicant who’s only applying to jobs they are interested in and qualified for there's 10 more just spamming every posting they come across. As a hiring manager I have to deal with that reality. The only way I know to reduce that overhead is to not add more by grinding the hiring pipeline to a halt whenever a position is filled.
As a hiring manager you are being paid to do that work, while the job-seeker is doing it on speculation. These are not equal positions, even though your falsely equate them.
Think about this: If you are not externalizing the costs, why not disclose in the job listing that this job posting does not correspond to a job opening ? What do the company gain ? What does the job-seeker lose ?
As someone who has done hundreds of interviews and built a team from the ground up for my current startup as well as others, the rest of your post just strikes me as hyperbole and excuses.
rkeene2 commented on Ghost jobs – 7 in 10 hiring managers consider them morally acceptable stackoverflow.blog/2024/1... · Posted by u/zh3
And to actually answer the question: 2 and 50.
You’re replacing half the staff each year. Any given month you expect to lose .5 and 25 employees respectively. With a lead time of 3-4 months in the former, that means during any given hiring cycle you expect to lose 1-2 employees. Anyone interviewing during slot is eligible, even if a role is not open _right that second_. For the latter, 25-50.
One thing applicants don’t realize is that by keeping the pipeline full I can fill a position “immediately” upon vacancy. If it had to start up a hiring pipeline it’d take 3 months. This means that in aggregate the hiring process is _more efficient_ than it otherwise would be. This means that _you get hired_ more quickly than you otherwise would. A cold-start wouldn’t necessarily improve your odds, it’d just make the whole process longer and more expensive for everyone.
You are wrong.
It improves the efficiency for the company at the expense of all of the people who spent time applying for something other than what was stated.
For example, you could not tell them that you would or would not hire them after a certain point in time -- which is something they will ask about and you will be unable to disclose, and so you'll wrap your lie in some vague language.
If these kinds of pipeline hirings were disclosed as such then your math would be correct. But, as stated, the purposeful information asymmetry (lying by another name) means that you are externalizing the uncertainty to the job-seeker.
You're making a trade-off, not getting a free lunch -- that trade-off is just at the expense of someone you are not legally obligated to expose this to.
It isn't nice.
(disclaimer: I've never done it, but I have talked to people who have; additionally I've never applied to a ghost/pipeline rec)
rkeene2 commented on Trump wins presidency for second time thehill.com/homenews/camp... · Posted by u/koolba
No, I think lolinder is correct.
People don't like being told "here is what was said, here is what was MEANT because you're not educated enough and can't possibly understand" did Harris zero favors.
I'm not sure in what respects you are disagreeing with me on, since I didn't mention anyone's level of education or intelligence -- I didn't mention anything about the people who interpret the statement in a benign way at all.
I added my thoughts on why people would take that statement and infer some other meaning than his literal words, since those words are said as part of a broader context. This says nothing about the people who didn't do so.
So, you starting a comment with "No" but then not addressing any point I made is confusing to me.
rkeene2 commented on Trump wins presidency for second time thehill.com/homenews/camp... · Posted by u/koolba
Did you even listen to the video clip in the article?
> It’s true, because we have to get the vote out. Christians are not known as a big voting group, they don’t vote. And I’m explaining that to them. You never vote. This time, vote. I’ll straighten out the country, you won’t have to vote any more, I won’t need your vote any more, you can go back to not voting.
I hate Trump as much as anyone, but deliberately misconstruing every word he says is part of what cost Democrats the election. People saw through it.
I think that given the context that he illegally tried to retain power after losing in 2020 that many people infer something into his words about reducing the need to vote
rkeene2 commented on Back to the future: Writing 6502 assembler with Amazon Q Developer community.aws/content/2oE... · Posted by u/ingve
I don't know anyone who doesn't say "I wrote X assembler" with complete understanding by all involved, and I definitely don't know anyone so pedantic they said "acksually, it's 'I wrote X assembly code'". I guess none of the dozens of assembly code makers or whatever I've know over the last 40 years was enough of a stickler. Or care one way or another.
I also understood the title to mean writing an assembler rather than writing assembly language code, and I've never heard anyone refer to writing assembly as writing assembler (or heard anyone who writes assembly referred to as an "assembly code maker", nor anyone who writes in any language referred to as an "<language> code maker").
I could imagine such phrasing being done by non-native English speakers, of which I'm have no doubt that there are a significant number.
My (unresearched) guess is that this is simply different dialects of speakers emerging with respect to informal references over the decades.
[0] https://man.openbsd.org/mprotect.2