“These beings have documented a perfect understanding of warp core, matter transmission, and matter replication technologies, yet they refuse to actually use any them and are stuck on a single planet fighting wars over limited resources.”
Oooh, that’s how grammar works in English language? Okay, so me as a developer of some obscure thing from this point forward are instructing everyone to pronounce “home” as “hume”, since that’s how you pronounce “o” in “tomb”. I decided that solely because my software is loosely related to the meaning of the word. K thx bai.
Neither did the author of graphic format. GIF is not a word, but initialism, like NSA, FBI, NASA, IBM, etc. And there are specific rules how they are read and pronounced.
NASA is an acronym, not an initialism. And guess how the last letter of NASA is pronounced versus how the A in the corresponding word is pronounced. Ah vs Uh.
Irrelevant comment to the discussion at hand as the matter is not set in stone in English language. More to the point it doesn’t change the fact how GIF is pronounced. Even if you consider it an acronym it’s still a form of abbreviation and not a word on its own with known heritage, hence the general rules on how to pronounce letter g do not apply.
Had the word originate from French part of the English dictionary (like gin, giraffe, etc.) then g is pronounced as j before vowels e and i and would make sense. But Germanic words (such as gift, geese) still use hard g. So applying normal rules is pointless, since English has no such thing.
In short, it’s pronounced whatever the way people pronounce it. End of story.
I may sound haughty and knowledgable when I say JiF then, but between just you and me, I didn’t know a damn thing about this and just decided to say it this way in my brain for reasons that remain unclear.
I always think all the arguments are ridiculous because it’s essentially saying that someone is pronouncing a product (not a word) that they created incorrectly. This product even has a catchphrase for it. There’s literally nothing you can say to contradict that. It’s a product with a catchphrase that describes how to pronounce it. If you pronounce it differently then you do you, but you are wrong.
It’s also pretty funny when it’s about actual product you will get corrected to the intended pronunciation, or at least, allowed because people acknowledge there might be multiple way of reading a word based on where you from. Like potato and tomato.
Well, there’ll be a lot less billionaires pretty quickly, from there it’s gonna be a lot of references to star trek, doctor who, dead philosophers and general southernisms.
lol … aliens arrive in 1960s era London police boxes to try to not alarm us as they make first contact
Aliens first message: … I say my good man, it’s quite a coincidence to find you in this part of the galaxy. I feel pecked by a hundred chickens, fuller than a tick on a big dog and fine as frog hair and not half as slick to greet you on this fair morning under god’s blue sky.
Alright now hook that shit up to the router, don’t forget to create a LAG or you’ll create a broadcast storm, and I’m in a WoW raid in ten minutes so make it fast.
The assumption is that they’re creating a high bandwidth trunk interface to the L3 switch/router, so if they forget to create an aggregate it’ll be two independent interfaces and will down the network (or a port will auto down itself with STP, MSTP, etc. but that’s not as funny)
A router of industrial scale which i see at work has its ports to be l3 ports by default. They don’t down the network as the router rejects config where two ports are given the same subnet… at least the ones i operate at work.
That’s true, the default for layer 3 switches is to have its port set as routable.
The original joke really kinda falls flat with modern tech, but it’s still funny to think about handing a switch to someone with zero knowledge and then watch as they accidentally lock up the environment.
LAG are aggregated interfaces and they can indeed be used to prevent (some) layer 2 loops. LAG as in Link Aggregation Group)
Using 2 non-LAG interfaces between the same 2 devices creates a loop.
In the case of a loop, if you’re running spanning tree, one of these interface will be blocking instead of forwarding, preventing the loop, but also percentile the use of this interface until the topology changes (ie: the current one goes down).
If you’re not running spanning tree for some reason, then both interface will chug along, oblivious to the fact that there’s a loop and broadcast packets will indeed keep being flooded on one and received on the other, again flooded, etc. creating a broadcast storm and impacting performance of the whole layer 2 domain and possibly even crashing devices.
A LAG more or less means the interfaces in the group behave as one big (aggregated) interface.
LAG also means you can push traffic on both interfaces for more bandwidth.
lemmyshitpost
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.