43
The IBM mainframe: How it runs and why it survives
(arstechnica.com)
Thanks, fixed!
Language is inherently messy, localized, and ephemeral, so it could be unwise to expect that kind of conformity on the global internet. It can be jarring, for example tech folk here in the EU seem to use corporate slang a lot differently than when I was working near SFO or DFW, we're I'd suspect the greater non-homogeneity of native speakers, as compared to the US, had a lot to do with it.
That aside, I think we merely disagree on the colloquial use of FAANG in 2023, as (from my anecdotal perspective) it seems to have semantically shifted into a categorical noun in common vernacular, rather than a once precise acronym from a decade ago, given most of the conglomerates behind the initial spelling have either re-branded, fallen in stock valuation, declined in labor desirability, or whatever else that had originally garnered acclaim and publicity. In that respect, pluralization of such a noun seems mundane, if not a little odd looking for typographical formatting.
Perhaps this could be coined as another stage of acronymization, or "acronym drift"; the process by which an acronym's original expansion and meaning become less relevant or obscured over time, and the acronym itself is treated and used as a regular word, independent of its original expansion. This can happen when the original meaning of the acronym is no longer relevant, but the acronym continues to be used and recognized based on its familiarity. An example that comes to mind is Google's original acronym for the QUIC protocol, which is no longer used to mean "Quick UDP Internet Connections", as was initially proposed.
Ex. An NBA or Sports instance containing /c/NBA /c/NFL /c/NHL and all the related teams.
My phone keyboard spelling aside, when the acronym was first coined, correct, but it seems to have sence devolved into more of a colloquialism for large scale tech related corporations, outliving the precise corporate restructuring that once comprised the old acronym. At least that's what I've experienced in my workplaces, as well as the comments here:
Was there a equivalent house hold colloquialism for IBM, HP, Xerox, Bell System, etc. back in the day?
The first link you listed (viewing the remote community from our local instance) shows 0 subscribers from the sidebar. From my understanding, no one from our instance is then subscribed to that remote community, so our instance has no reason to index those posts. Although I could be wrong, and it could be that no one from our local instance is subscribed to any community on the remote instance. I'm unsure if only instance federation or community subscription is necessary for merrioring/indexing remote posts.
Email is too big to change, too broken to fix… and too important to ignore.
That is such a great quote! Here is my attempt at such a quip:
Email's own complexity, legacy, and backwards compatibility divines its own Incorruptibility.
My order of thoughts/preferences:
- I think
people catchingwill transition well for us the best, especially once mods can migrate posts to better suited communities. General discussionwould nicely reduce junior help questions, and improve the SNR for real discussions.Cross postingwould really encourage growth of the long tale of smaller communities here, but Lemmy mods can't (yet) manual/auto merge threads over instance cross-posts (technical missing feature?) so keeping with a conventionalmaincommunity is a bit better for now in avoiding too many duplicate posts across the instance, or splintering of discussions.General topiconly is a bit too restrictive, and could harm post traffic, while still making it difficult to moderate consistently.
One thing that could help improve this is better first-class support for cross-posting, integrations such as selectively merging discussion threads from communities on the same instance, to avoid fragmenting discussions, e.g. like how Hacker News can merge topics that reach mega-thread status. Posters could choose or be force to enable such cross posting for certain communities. E.g. if you want to post to the general !programming community, you first have to put forth a little effort to categorize your post by cross-posting from the most relevant community first. Although, this could be more akin to #tags, that may scale better with multiple matching categories.
Another feature that could help would be more advance moderation tools, such as post migration. Instead of closing or deleting offtopic posts, moderators could migrate posts with existing discussion threads to more appropriate communities on the same instance, e.g. just like how Discourse can re-categorize and manage user posts. I'm not sure how the logistics like the handoff between communities could work or how votes should be retained, but it's just a thought.
Checking the issues tracker for RES, there's not yet any mention of lemmy or kbin:
Perhaps you could ask there. I'd also recommend checking out the Lemmy Plugins & Userscripts community:
You know how folks inherit tools, workshops, or auto projects from parents and family? Stuff like wood working equipment, sewing machines, or whatever tools of the trade. It's got me wondering, what's it like for children that inherit their parents' codebase, computers, keyboards. Surely with the growth of the tech sector and job market, compared to half a century prior, this could be a growing re-occurrence.
E.g. like the entire premise of this YouTube channel titled "Inheritance Machining": https://youtu.be/hearLttbrLo
For example, my grandfather worked for IBM, and my family recalls growing up surrounded by punch cards around the house. Of course that form of programming only lasted so long, so the next generation was unlikely to reuse the same tools of the trade, but as tech stacks have matured and interfaces standardized, what are the chances are that folk's children will use the same Linux kernel modules, custom mechanical keyboards or desktop chassis that their parents used today?
ruffsl
joined 1 year ago
I fell for it. It took me a minute into the game time to figure what was up and double check today's date.