detuur

First thing I do at a new job is make friends with IT, if at all possible. I end up being the guy with the new high-dpi screens they're trialling, more RAM in my laptop, and "just DM me in Teams" privileges for tech support. All for not treating these people like tech janitors (and obviously there's nothing wrong with being a janitor).

Cheat code for this: ask them if they need any custom tooling. I spent a few hours at a past job on a userscript for their ticketing interface to fix some annoyances. Brownie points for life.

The answer to that reply is you don't need to explain it to your users. People are used to fuzzy/best-effort sort of matching, especially when it's specifically presented as a "matching algorithm" instead of a "filter".

I can't believe you're the first person I find in this conversation who raises this issue. This is the exact reason why Marcan flipped his lid. Linus publicly championed a very technically complex initiative and then left all those contributors to the wolves when things didn't progress without a hiccup. Especially damning when you consider that at every step, the fief lords in Linux have seemingly done everything in their power to set up the r4l people for failure and Linus hasn't so much as squeaked at them. He personally cut the knot and asserted that Rust is Linux's future, but he constantly allows those below him to relitigate the issue with new contributors (who can't fight back because even though they're contributing by the supposed rules, they don't have enough social buy-in).

I have a few projects that I've abandoned because they only made sense as a FOSS project, and I saw how FOSS maintainers were being treated. I love FOSS, I love the philosophy, and I would love to "give back" one day by making the ecosystem richer, but I've not yet found a project that I love enough to be abused over.

Yes yes and a reminder that BSD Jails are better than anything Linux does and a bunch of other dead horses we like beating on the regular around here.

Which is a fanciful way of saying that I don't understand the relevance of your comment at all to the topic at hand, which is an interactive frontend.

Ah yes, famously one can only be a sysadmin if they're unable to use a different cli verb order.

Come on now. Either present a real argument or accept the fact that tooling isn't forever going to be frozen to what you used in your 20's. Newer tooling uses newer best practices and the improved verb order is part of that.

I don't see how the real mode emulation on the 80386 (VM86) fails to meet the standard of the Popek and Goldberg definition. IA-32, yes, that took a while, but VM86 allowed 8086 (real mode) tasks to run as if they were running authentically in real mode while the 386 was in protected mode, and had all the features P&G describe in their definition. It runs natively, it runs with equivalent performance, and there's a VMM trapping privileged instructions to either emulate or arbitrate system resources. It's the full deal!

I looked right past `--resolve`, so yes that now makes sense.

    > one.one.one.one:443:64:ff9b::1.1.1.1

Is this a typo or a weird curl-specific address format I've never heard of?

NAT essentially has a "default deny" rule.

.de domains require a German postal address, so I would actually trust them more than the .ru equivalent. Plenty of other ccTLDs have even stricter nationality requirements for registration.

The pricing is $20/year if I'm not mistaken.

Can we add jxl to that list? Doesn't have nearly as wide support but you could be part of a turning tide.

Same. I can't be the only one who feels that Nix is doing the right thing the wrong way. The right thing being reproducible, declarative, composable environments; the wrong thing being its language and tooling. Too often I feel like serious Nix users spend a distressing amount of time manually doing package manager tasks, so the way forward is to stop doing exactly that. Going back to imperative composition is a step backward that will never help people free up time away from package management.