this post was submitted on 22 Jan 2024
11 points (64.9% liked)
Linux
48287 readers
657 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
All these people saying "Just use LibreOffice" are missing the point: if they ask about a program, then that means they have a usecase for said program.
This isn't StackExchange; let's not repeat that cycle.
Edit: Changed "is" to "are". Lol.
Sure, but they may also be unaware OpenOffice is unmaintained and its worth pointing out.
Then those people should say that as an addendum or side-note to an attempted answer to OP's question, not as a replacement for said attempted answer.
You're not wrong, and I'm upvoting everything you say because I hate the smug SO people who ask why instead of actually trying to help.
But in this specific case, there's literally no reason to use OpenOffice, it's discontinued. People shouldn't have to explain how to use a defunct software with an addendum.
It's not an obscure programming language with an edge case, it's a word processor.
Yeah, I hate those people too. I appreciate the support.
I can see where you're coming from. Still, I personally try to give them the benefit of the doubt and assume until demonstrated otherwise that they have considered alternatives and decided their current program is best for their particular usecase.
Is it naïve? Possibly. I fully admit that possibility.
I admire the respect you have for those who ask questions like this, but I think I disagree.
If there is something egregiously wrong with the premise of what a person is seeking to do, and there are no qualifying statements in their query about why they do in fact need to do this specifiic thing in this specific way, chances are high that they are uneducated about why the premise of what they're trying to do is flawed, and they are best served by being course corrected. Giving them the answer they're looking for to continue the bad thing while hiding your suggestion of what they should be doing instead in a footnote is just enabling them to double down on the short term path of least resistance that will probably come back to bite them again later.
If they really did know what they were doing with regards to doing an otherwise unsafe and/or unsupported thing, or if the restrictions tied their hands from using the obvious replacement solution, it either should have appeared in their question prompt, or it should be in the first replies to the first round of answers.
I say, withhold outdated advice unless the context of the conversation makes it explicitly clear that the old advice is genuinely required and not substitutable with current advice. But also don't be smug, rude, dismissive, or standoffish about it. Don't argue with someone who says they really do need a specific solution.
That said, this only applies in really cut and dry cases like this one, where there very clearly is an indisputable thing you shouldn't be doing, and a drop-in replacement you should be using. The ones I hate are moreso those you may see on StackOverflow where the question is like, "how do I do in JavaScript?" and five of the seven responses including the accepted answer offer a solution in some big dumb framework or lib that they apparently expect you to just incorporate into your project.
You are probably right about this. Still, as I said to another user, I just feel it's a bit of a slippery slope from a stance of concern to full-blown-StackOverflow-ignoring-the-question.
I can agree with this.
Fair enough.
Truth be told, I work in customer service, and have very little tolerance for bullshit, so I'm genuinely surprised to find myself as patient and giving-the-benefit-of-the-doubt as I am being. I guess this thread just reminded me a bit too much of the days of 2015. Lol.
Edit: Shit. Forgot to add the
>at the quote at the top. My bad.This is only correct when the software in question isnt abandonware from 2014
Eh, I can see where you're coming from, certainly, but I feel it's a slippery slope from this stance to full-blown StackOverflow levels of ignoring-the-question.