This was, without any doubt, a prophetic dream. The apocalypse will soon be upon us! Be wary of the four horsemen: Ronald, King, Wendy, and… Chihuahua
Inbred: chaorace’s family has been a bit too familiar. (Can be inherited)
This was, without any doubt, a prophetic dream. The apocalypse will soon be upon us! Be wary of the four horsemen: Ronald, King, Wendy, and… Chihuahua
Still waiting for git good
unfortunately 😔
Sugarcoating pills is fairly common, especially for pills which are frequently ingested or target older demographics. It’s because sugar coatings are much gentler on the esophagus (i.e.: less likely to cause esophagitis, “pill burn”). Advil (i.e.: ibuprofen) is a cheap, well tolerated, and non habit-forming pain reliever – it’s about as safe as such a thing could possibly be, so hopefully that helps to explain why a sugar coating might be warranted given the aforementioned upsides (for the love of all that is holy; always read the directions on the label, it’s still quite possible that Advil is not safe for you specifically). FWIW: the bottles also have childproofing mechanisms built into the caps (… at least in U.S. markets. Not sure about elsewhere?)
Watch out I saw these guys about to show up at your inbox
Yeah, I’m subscribed to notifications for the PR and have been holding out waiting for it to get merged because it’s easier to maintain a clean git history that way. If the PR’s still not merged by this evening I’ll just bite the bullet and do it the (slightly) harder way for the sake of staying current with the new seasonals
Male A to Male C is abolutely possible. It’s the Male A to Female C adapters which are evil. There is no pinout mapping that will turn an A host into a “real” C host and that’s exactly what a Male A to Female C adapter purports to do.
In any case, if you know what you’re doing then all bets are off the table. Hack away freely because at the end of the day it’s all just copper and bits anyway. With that being said, anyone who knows what they’re doing does not require my permission to… vague gesture know what they’re doing.
Like I said: in order to do it the non-evil way you need to cram in an onboard USB chip. Female USB-C from a Male USB-A plug-in is explicitly not possible to implement in a spec-compliant manner because of the pinouts.
You can brute-force a smaller passive adapter like those online but it’s a devil’s bargain. Nobody targets these janky adapters when designing products. USB-C things will just break without any rhyme or reason because you’re fundamentally breaking the hardware contract and “lying” about the capabilities of your port.
No, but now that you mention it that would be a pretty plausible thing to have happen. Just grabbing hold of a random armchair analysis and then repeating it ad nauseum until it transforms into an irony-poisoned meme totem… you’ve really gotten my hopes up now!
No, it’s because I read an expert opinion on the subject: https://old.reddit.com/r/UsbCHardware/comments/m7rcu5/any_reliable_usbc_female_to_usba_male_adapters_yet/grducjr/
If you hate Amazon you can buy it on the CableCreation website instead.
EDIT: that monoprice adapter isn’t even active lol!
First thing’s first: all such adapters should be considered evil by default. The only way to make a compliant adapter is with active circuitry in the adapter essentially providing an entirely standalone USB controller interface.
With that being said, here’s an adapter which does exactly that. Back when I researched this topic in October I found that the linked adapter is essentially the only one of its kind on the market right now.
I like flakes a lot, speaking as a type of user which I’ll call a “casual packager”.
This is to say that I like being a good citizen and sharing my packaging efforts… while also simultaneously feeling totally uninterested in becoming an owner-for-life. Flakes let me share a package without those pesky strings – when the user installs a package using one of my flakes, a personal lockfile gets generated at the latest git commit and that’s that. If the user doesn’t like the version they get, then the power is in their hands to choose a different git ref via their own generated lockfile.
Obviously this is something of a user footgun, especially for consumers of high-impact or security-critical applications, but most of those things are already important enough to get packaged. When it comes to niche, infrequently updated stuff, this approach works super well and helps to draw many reluctant packagers like myself out into the open.
95% of the time he plays the straight-man and then the other 5% of the time he behaves like an unhinged lunatic. It’s the perfect recipe for cultivating an audience of viewers who love to torment him with his own words. After that it’s just one step further to put words he didn’t say into his mouth and see how he reacts to getting gaslit.
I make it sound like a cynical ploy but really this kind of thing is just intrinsically tied to Jerma’s online personality. Lightning in a bottle. If you ask me the most impressive part’s actually how he manages to stay in control of the situation and not get totally swallowed up by the increasingly bizzare behavior of his viewership.
This article is good, really good. Somehow despite having used plenty of builders in the past I barely even knew half of the stuff documented here.
I’m particularly interested in learning more about the special paths that derivation outputs can provide – looking forward to seeing that section expanded.
Still no free blowjobs!
“He who smelt it dealt it, and I am no blacksmith good sir”
I burst into a short musical number, then put my coat on and peoplewatch at the park with a sandwich.
In-group signalling. One of the many microhabits you need to acquire in order to fit in with the local culture and nothing more. As usual, people make up reasons to justify why their cultural proclivities are objectively right but these are without exception completely post-hoc.
A self-portrait. If it turns out unrecognizable, just move the goalposts and tell the viewer that it’s a depiction of their mum.
You may be interested in reading this post about the process of packaging Steam.
tl;dr: It’s mostly an annoyance reserved for packagers to deal with. Dynamically linked executables can be patched in a fairly universal fashion to work without FHS, so that’s the go-to approach. If the executable is statically linked, the package may have to ship a source patch instead. If the executable is statically linked & close-source, the packagers are forced to resort to simulating an FHS environment via chroot.