As an American who was raised Lutheran, who was taught a bunch of Romance-Euro-centric world history in school, I always considered Roman Catholic to be the "default" flavor of Christianity. Protestantism in all of its forms are hard forks. It's in the name, even--the Roman Catholic church is what Protestants are "protesting".

To unironically "-and Zoidberg" Catholicism out of Christianity while leaving Protestant flavors included feels completely backwards. I've never heard anyone do it.

But if I did, I could only assume it was due to some No True Scotsman bullshit. "Only we practice the correct way. Everyone else isn't just interpreting it differently, but interpreting it wrong." Sounds like an Evangelical line of thought to me.

Tab hoarding is just poor man's bookmarks.

Oh wait, you're on Gelbooru. Nevermind, I get it.

This is almost word for word what I said in another friend group today. Protecting individuals is literally why LLCs exist. It's what "LLC" stands for.

Nintendo Hyper Beam'd them into oblivion but they got a Substitute up first. The defense strategy was smart. The strategy that put them in the position of needing to use the defense strategy was idiotic, yes, but the defense was smart.

Short of Nintendo doing nothing at all, this is probably the best outcome that could have realistically happened.

I don't think there are any desires I carried over from childhood that I finally fulfilled later. Most things I wanted in the past I simply stopped wanting as I changed with age.

I have, however, on numerous occasions in my adult life, looked at something that probably would've made my kid self go into orbit with excitement and thought, "Man, if only I could get an adult to buy me this..." only to blink a couple times, see the lightbulb turn on, and go, "HEY, WAIT A MINUTE..!"

They upgraded their orbital copyright laser cannon into an orbital trademark laser cannon. The beam is narrower and hits fewer targets, but it willl never expire and its firing range is even vaguer than before.

Here's the ELI5 answer I'd give to your friend:

Computers are like servants. They do whatever you ask of them. But to be able to ask them things, you must do so in their language. On the extreme low level that means writing code to make programs, but on a higher level, it means talking to programs someone else already wrote using special commands.

The buttons and switches on a GUI that you can click on with a mouse are like pre-recorded commands that instruct the computer to do some specific thing. The button or whatever will have a symbol or text description that lets you intuitively know what it's for, and when you click on it, it plays a pre-recorded command to the computer in its language that tells it to do that thing. With these buttons, you can ask things of the computer in its language without having to know that language.

As you get more intimate with the computer, this system can start to feel a bit stiff. You've essentially got a butler who doesn't speak your language, and any time you need to give him a task, you have to fumble through a basket of pre-recorded tape recorder messages to find the one for the task at hand, and play it to him. For more complex tasks, you may need to chain several of these together. It gets slow and awkward. And god forbid you don't even have a tape recording for the thing you need.

It's easier if you learn the butler's language yourself. Then you can ask him for things directly. You're not bound to any collection of pre-recorded messages to use, you can tell him exactly what you need. And if you don't happen to know the word for something, you can look it up. It cuts out all the faffery with fumbling over a tape recorder looking for the messages you need to play.

Using a terminal is roughly the computer equivalent of speaking to your butler in his native language. You're not limited to only the buttons and features any particular program lets you have; you can make up exactly what you need on the spot. And you never have to bounce your hand between a mouse and keyboard to do it, you can keep your hands in one position at all times, which really adds up over time in both speed and comfort.

Practicing this will also give you the side perk of better understanding how the computer actually works overall, and what it's actually doing. This knowledge can come in super handy when diagnosing problems with the thing. When a GUI gives up, a terminal can keep digging.

Pretty sure they are asking, "Why would I ever want the tracking copied, why is this relegated to a bespoke option instead of being the default behavior?"

I buy Royal Crown and mix it with Crown Royal.

The perfect marraige of the king of middle shelf soda and the queen of middle shelf whisky.

If only shibboleet actually worked...

I keep my 160GB iPod Classic on life support.

I think the clickwheel design is, in my view, the single best one-thumb no-looking-required input scheme for an MP3 player I think anyone has ever made. Plug it into, say, my car stereo AUX port and I can pick it up with a free hand to control volume, select tracks, and even navigate mostly by memory without having to look at the thing. I can just tell where I am based on the feel of the control. Infinitely better than a featureless flat slab of a touch screen that gives you no sensory feedback.

I like its solid build quality. Full metal chassis with that sexy anodized aluminum finish. I miss that. Despite having a spinning disk hard drive, it never skips, and I've never had read or write issues. Though I'd probably try to mod it over to some kind of flash NAND storage someday. There's also a USB-C mod available that I'd like to do someday, since Apple 30-pin connectors are an endangered species now, and even then, carrying around an outdated proprietary cable for only one device is something I'm eager to never need to do again.

I'm also pretty heavily conditioned to not have tens of gigabytes of music stored on my phone eating up all the precious space. But that's mostly a holdover from my previous phone, which had a 32 GB onboard memory limit and no SD card expansion slot. I guess now that I have a proper memory expandable phone and, and now that half terabyte microSD cards are relatively inexpensive, that's no longer a huge concern...

Also, Rhythmbox can sync to it. Maybe other software too. So I don't even need iTunes to use it.

We hired a greenhorn dev several months ago. He had two years experience at a larger company. I only have about five so far and my company doesn't really pay all that well to field great talent, so I wasn't hoping for the world. But we were expecting at least something a little above entry level experience.

The guy did know how to write basic code. Frankly not to the degree I hoped for, though. Also lacked all auxilliary skills like effective use of version control, logging in to remote servers over SSH, documenting code with doc comments. He doesn't even write particularly legible code without the formatter to fix it for him. Very sloppy with spacing, braces, etc.

But those are all of little concern. Those could all be taught. It meant more effort needed to be spent in onboarding than we wanted, but it could be done. Helps that he has a very positive oulook on constructive criticism and he uses it to improve.

One thing that I don't think I can teach him in any reasonable amount of time, though, is how he mentally tracks the structure of the program he's working on.

When I program, every time I change anything, I construct a mental web of everything this piece of code might affect when changed, and the ramifications it might have. I think of neighboring code and concepts looking for patterns, and whether the new thing I'm adding or changing could be better expressed differently to leverage those patterns. I think of the future trajectory of the module or feature, and whether it would be advantageous to bake-in a certain kind of forward-thinking extensibility now rather than after it becomes partially entrenched later. And most of all, I think of how someone completely unfamiliar with this code might read it, and how I can improve the way it is written to make the most important parts stand out clearest.

And when I'm debugging code, even if I see the problem and think I immediately know the solution, I still take time to read the surrounding code. I try to piece together the original bugged code's intent. Is this onvious-looking problem the real problem? Or is it a poorly documented, poorly structured mess that looks like it wants to do one thing but is intending to do an entirely different thing? This hesitation has saved my ass on several occasions.

New dev doesn't do any of these things. He pulls a bug ticket, figures out what module or function is the supposed source of the problem, and bangs on it until the effects of the problem disappear. Little research done to understand what the intent of the code he's altering wants to do, and even less spent on figuring out what downstream systems will be affected. And once he achieves his singular result, he just pushes it as-is. No cleanup pass, sometimes forgets to format it the way we ask him to.

To be fair, it's a big new codebase. I can't expect him to reason around things he is not familiar with, nor would I think it reasonable that he study the entire codebase before touching it.

I also don't think these things can't be learned. I had to learn them at some point, after all. But I do believe that people like myself and one of my fellow devs are more predisposed to picking these programming soft skills up, whether it be through nature or nurture or some combination. That, and I don't think these kinds of soft skills can really be "taught" in the traditional sense. These are wrenches you can only really learn to dodge after being hit by a few.

"Tubular" I can at least trace where it came from. It's surfer lingo. Sometimes when you catch a wave, the wave crests all the way over you and encloses into a tube. Surfing through that is supposedly the most euphoric thing about the sport. "Tubular" is thus "anything that makes you feel the way a surfer surfing through a tube-shaped wave feels". Thrill, wonder, excitement, etc.

I have no idea where tf "based" came from. Wiktionary suggests that it ultimately comes from the chemical definition of "base" (i.e. the opposite of an acid). "Freebasing" is a way of converting certain drugs, particularly cocaine, into smokable form by converting them from acid to base. Rapper Lil B. is alleged to have coined "based" to describe his lifestyle as someone who is unafraid to be himself as an individual (which, I guess, included smoking crack). This supposedly filtered into 4chan to become an alt-right slogan for "admirable person who bravely maintains alt-right opinions in spite of adversity" ("based and redpilled"), and later was claimed by groups outside the alt-right to simply mean, "someone with admirable opinions".