HNHacker News
TopNewBestAskShowJobs

QUrprUd1nCeicw

137 karma · joined January 6, 2023

submissionscomments
QUrprUd1nCeicw··on Ask HN: Where are all the parties?
>many people are trying to milk Covid concerns merely to continue working from home or reaping other benefits that they value

How is this "milking" anything? The last few years have proved that lots of white collar jobs don't need to be done from an office building.

>Other than putting humanity in a total economic death spiral (that will be many times worse than Covid) I'm not sure what else can be done to give immunocompromised people a better situation.

This is a false dichotomy. The science is clear on this one. Continue wearing masks in public places, physical distancing, practicing basic hygiene, and continue requiring vaccinations. Yes, all of those things are proven to reduce transmission of COVID as well as other airborne viruses like the flu. Society doesn't need to shut down or enter a "death spiral" to do any of them. Leaders just caved to political pressure and stopped enforcing them.

>are genuinely trying to go out and live their lives as normally as they can and trying not to be a slave to their illness.

Yes, and they probably still have to wear masks and avoid certain places that are likely to carry an increased risk of infection. "Not being a slave to the illness" doesn't mean you go out and take stupid risks.

>Has anything qualitatively changed for immunocompromised people with Covid?

Yes, COVID is significantly more contagious than influenza, and causes more severe illness than influenza.

QUrprUd1nCeicw··on Ask HN: Where are all the parties?
No it clearly is targeted towards them too, judging from OP's other comments where they directly include people who have real issues.
QUrprUd1nCeicw··on Ask HN: Where are all the parties?
I'm really not sure what point you're trying to make here. Every example you gave is someone "managing" at their own expense. When an immunocompromised person gets sick from a rave, no one else suffers directly from that. Of course you can "manage" that way up until the moment you die. You can't get upset when society changes and some of those people decide the expense of "managing" isn't worth it any more.

I mean, come on. Just think about this. We've heard so much of this over the last few years like "some people died from the flu before, so you should accept you likely may die from COVID." Would you really say that to the face of an immunocompromised person?

QUrprUd1nCeicw··on Ask HN: Where are all the parties?
I don't need a reminder I'm in the extreme minority, my whole life is a reminder of that every single day.
QUrprUd1nCeicw··on Ask HN: Why are toggle switches replacing checkboxes? Isn't on/off less obvious?
Typescript and Rust didn't exist in the late 90s when GNOME was created.
QUrprUd1nCeicw··on Ask HN: Is an union for sw developers still a bad idea?
Police unions are a special case that deserve special attention. They have a unique position that essentially makes them lawless organizations. They can hold the rest of the system hostage or just decide not to enforce certain laws.
QUrprUd1nCeicw··on Ask HN: Why are toggle switches replacing checkboxes? Isn't on/off less obvious?
Have you reported that as a bug?
QUrprUd1nCeicw··on Ask HN: Is an union for sw developers still a bad idea?
It was never a bad idea. There are some problems that just can't be solved with throwing more money at it. The anti-union propaganda is so strong in some areas of this industry that it's manifested in that form of general apathy. Just ask yourself why it's always the highest paid workers who fight against unions the most.
QUrprUd1nCeicw··on Ask HN: Where are all the parties?
As someone who has health problems that forcibly put me in at least a few of those "discretionary lifestyle demands," it's a little condescending for you to just dismiss it later as "neuroticism and anxiety about maintaining purity." The worst is probably COVID-related -- immunocompromised people have been complaining for these past couple of years about how the world just stopped taking COVID seriously and they still have a point. Society is still effectively shut down for them and very few people seem to care.
QUrprUd1nCeicw··on Revisiting KDE
No, there wasn't a point. Making these accusations is the personal attack and it's a non-falsifiable claim anyway. Once you go that route you're on a complete descent into nonsense conspiracy theories.
QUrprUd1nCeicw··on Revisiting KDE
It's still not a rant. You didn't actually read my comment so you can stop with the characterizations and asking me to introspect, because you've already admitted nothing you say has any relation to what I actually typed.

And yes, it did happen near immediately compared to other comments on this site. Please respond to my actual words next time instead of continuing with these rude, low-effort comments. I try to make my comments more informational and have more depth each time, you're not giving me the same courtesy. If I give a short response people complain they don't understand what I'm talking about. If I give a long response people complain it's too long. If I give a medium response people complain I wasn't convincing enough. So there's just no winning with you folks. This is another case where what you call "complaining" and "expressing opinions" is actually just "trolling" and "making excuses to avoid listening to anyone else's opinion." It's another accusation in a mirror, you need to be doing some introspection and figure out why you're being so evasive.

QUrprUd1nCeicw··on Revisiting KDE
No, I wasn't being unfair or ranting. This is a classic case of "accusation in a mirror." When I push back on people for "shitting" on things, someone immediately tries to flip the script and accuse me of ranting. If you change your mind and still want to talk, please be honest with yourself and admit you were being unfair by dismissing my whole comment without even reading it.
QUrprUd1nCeicw··on Revisiting KDE
Ok, sorry. I misquoted you. I should have said "isn't an attack" instead of "isn't an insult."

Still, the rest of my comment is still relevant even with that change. There's no "attacks" anywhere in anything you've quoted. That response about Ubuntu and XFCE is a factual statement. GNOME, Ubuntu and XFCE are all different platforms and they have different APIs. You can't expect GNOME to implement every XFCE feature just like you can't expect XFCE to implement every GNOME feature. And if you decide to do port to another OS like Windows or Mac, then you have to decide if you're going to use Linux APIs or Windows APIs, and so on. This is all very basic concepts. As an app developer you have to decide which of these APIs you're going to use. It's not "attacking" anyone to point out that truth. It's also not an "attack" for them to respond with a firm "no" response. If you want to get along with others you need to learn to accept that sometimes you'll receive "no" for an answer.

And no, "Hey, don't take that away, I'm still using it" isn't legitimate feedback. You need to actually explain why you need to use it that way and why another way isn't going to work for you. And even after that, you still need to be able to accept that your explanations could be bad or wrong and could get thrown out by the developers. You're not the one paying the cost to maintain that code so you don't get the final say on what gets thrown out and what doesn't. That's the entire point of open source. If you don't like this, then you start sharing some of the costs by maintaining the code, and then you can be the one who makes that decision. But it simply isn't an "attack" on you when someone else decides your feature is too expensive for them to work on anymore. You need to not take that so personally.

>The gnome dev literally said that any way other than their way had was because the users weren't thinking!

>I mean, they literally said that the users are not thinking if they prefer the old way.

No, it doesn't say anything like that anywhere in the article. That article isn't written by a GNOME developer either. If you're referring to something else, please show the direct quote where they said that.

>If these designers knew that, they'd have more marketshare on Linux at least.

There's no "marketshare" and no "market." This is an open source project being given away for free. I think what you meant is "mindshare." None of these projects are concerned with trying to dominate the mindshare, they all work together.

QUrprUd1nCeicw··on Revisiting KDE
No, I'll continue calling people to task for expressing their opinions poorly or falling back on these bad justifications. Cut that out please, you're doing it now. Responding with "well I have a right to express my opinion" is just a platitude, it's not adding anything of value to the conversation or moving the discussion forward.

The guidelines of this forum say you should post "anything that good hackers would find interesting" and it's not interesting to just complain and rant. Even moreso when it's the same boring things we've all heard before like "XYZ sucks" or "I shit on XYZ" like the parent comment was doing. The guidelines also say "Please don't post shallow dismissals, especially of other people's work" and that's what the parent comment was doing too. Please make your comments better than that or don't post here. Make a commitment to be better every day of your life and you won't have to worry about this. No one's asking anyone to solve world hunger, you're falling back on the usual HN hyperbole and snark. So you can just avoid saying that. This is a series of very simple personal steps you can realistically take to improve yourself and improve this forum at the same time.

And maybe I wasn't fully clear the first time. Sure, you have a right to do whatever you want. But that isn't useful way to communicate in a lot of cases. Just put a little bit of thought into it please? Imagine you have a new open source project. Some person comes and makes a complex feature request that will take you years to implement. You ask "why do you need this" so you can try to get to a simpler solution and they respond with "because I have a right to express my opinion." Ok? That's not really answering the question, is it? Now imagine looking at it as an outsider and you can tell how the person refusing to give explanations is the one being stubborn and evasive and stonewalling the discussion. You can't even blame the developer for that at all. This is a public forum, you're not having a casual bullshit conversation with your friends when you comment here.

Please also consider that your opinions could just be wrong, and other people may know more about the subject than you. Maybe you're not as informed as you think. If that's the case then you're doing active harm to people around you by propagating misinformation with those opinions. If you've been helped by receiving useful information from this site then you owe it to other people to make sure your opinions are helping them, not harming them. So you shouldn't just express whatever opinion occurs to you without thought and research.

I'm not trying to be negative here though. I've also seen lots of times here when people expressed their opinions in an engaging way, giving justifications and honest reasoning and useful suggestions. You can do it too, you just have to put in a little bit of effort and listen to the person you're talking to instead of just blindly saying "I have a right to express my opinion" at any opportunity.

QUrprUd1nCeicw··on Revisiting KDE
KDE isn't the environment of the Steam Deck. The environment of the Steam Deck is Steam running its own Gamescope compositor. The desktop mode runs KDE but that's optional and it's not the main mode because the Steam Deck isn't a desktop, it's a handheld gaming device.
QUrprUd1nCeicw··on Revisiting KDE
Clearly they didn't "ruin" it because there are people in this very comment thread with a mix of opinions. Some saying they like it, some saying it's okay, some saying they don't like it.
QUrprUd1nCeicw··on Revisiting KDE
I have bad news for you, every alternative is going to be the same or worse. There's no good and clean solution for early boot services. The Linux kernel expects you to handle any of those issues in userspace with a userspace daemon like dbus. If you're upset the documentation is sparse, well, welcome to open source.

Nobody is "screaming" at you to stop using libdbus. The issues with it are actually spelled out in the docs. Here's what they say:

>The low-level API documented in this manual deliberately lacks most convenience functions - those are left up to higher-level libraries based on frameworks such as GLib, Qt, Python, Mono, Java, etc. These higher-level libraries (often called "D-Bus bindings") have features such as object systems and main loops that allow a much more convenient API.

>The low-level API also contains plenty of clutter to support integration with arbitrary object systems, languages, main loops, and so forth. These features add a lot of noise to the API that you probably don't care about unless you're coding a binding.

So unless you really have your own object system, language and event loop, you shouldn't bother with using libdbus. Use literally any of the other bindings of which there are many. The glib one is only going to be good if you're already using glib's event loop and object system.

QUrprUd1nCeicw··on Revisiting KDE
That has nothing to do with GNOME. That's going to happen any time you try to theme 100 different programs and try to get them all to look consistent. Try to imagine writing one CSS and applying it to every website you visit and expecting it to work correctly. It's just not going to work, you'd have to manually rewrite the CSS for every site. The same is true of desktop applications. The only reason your desktop appears consistent with the default Ubuntu themes is because all the apps already did the work to target that theme. If you want another theme, you have to do all that work all over again. You can't avoid this just by adding more options, it's a large amount of extra code that needs to be written every time for every app.
QUrprUd1nCeicw··on Revisiting KDE
That would just be trading one set of problems for another set of problems. Be careful what you wish for.
QUrprUd1nCeicw··on Revisiting KDE
That goes both ways my friend. Open source maintainers have a right to dismiss substance-free complaints without needing to prove P = NP.

Complaining about potholes is a great analogy. Repeatedly bringing up the pothole problem at the local swing dancing meetup isn't going to solve anything. You need to actually send your complaints to the transportation office. If they've heard about a particular pothole before then you don't need to bring it up again and keep sending them the same complaints. They already know about it. When they can't fix everything in time then the problem is either bad planning or lack of budget, and louder complaining definitely won't do anything about that.

QUrprUd1nCeicw··on Revisiting KDE
"Shitting on GNOME" isn't going to solve anything. The people who made it the default in their distros already disagree with you and trash talking isn't going to change their mind. Everyone who's been around has heard all the common complaints before. Just saying "it's technologically better" doesn't even mean anything either. Technologically better at what? There's this myth that you seem to be bought into about how Qt and GTK are fighting against each other or are competing against each other when that's not true. They happily work together and borrow ideas from each other when it makes sense.
QUrprUd1nCeicw··on Revisiting KDE
Sure, some people think Windows XP (also roughly 20 years old) was more pleasant too. But somehow, few of them are racing to format their hard drive and replace everything with Windows XP. I bet you could name a few reasons why.
QUrprUd1nCeicw··on Revisiting KDE
I actually think the reason for that is economic and it does work IRL. What you think of as "power users" actually requires a lot of training, it's expensive to produce them. Their skill set still isn't enough to offload real development tasks on them, so whatever they do is still completely dependent on having a team of engineers to support them. If you're going to be paying the engineers anyway, it's cheaper to just make something that requires less training for the users up front.
QUrprUd1nCeicw··on Revisiting KDE
You can criticize all you want, but I notice you neglected to share any of that actual criticism in your comment. Closing a bug as wontfix isn't an insult, please stop taking that personally. All open source projects reject bugs sometimes. Every project gets to determine their own threshold for what features they remove and what bugs they close as wontfix. All projects reject bugs. There's a comment from down thread about KDE developers doing exactly the same thing: https://news.ycombinator.com/item?id=34395682

But you also have to make sure your criticism is good. Just complaining that a feature was removed "because I was using it" is not a useful criticism. I learn nothing from reading that. You have to actually explain why you needed the feature, how you were using it, and why the newer options don't work for you.

>Mostly the gnome supporters imply that the complainers are just plain stupid

I don't see the author claiming anyone's stupid in that article. This is what the author says:

>it is just bad file organisation coupled with a bunch of old bad habits

And maybe on that note, you could consider that designers know a lot more about the habits of users than a random drive-by commenter, considering they study it for a living?

QUrprUd1nCeicw··on Revisiting KDE
The comment on the higher up graph still says "I've excluded personal accounts" so a lot of data is just missing there.

I'm not saying it's illegitimate to criticize anything. Please don't put words in my mouth. This is the entire original comment I was responding to:

>What volunteers? GNOME is a Red Hat project.

There's no legitimate criticism in this comment. If you do have real opinions, you never communicated them. The only thing here is the usual substanceless FUD and complaining about Red Hat that pops in every Linux thread. It's bad discussion. You did add some more information afterwards, but your original comment didn't have that. This is why it's trolling. Do you see it now? Next time, lead with the information. Please don't just make snarky comments. I really don't get this vehement denial when it's right there. It was a snarky comment, judging by the language you're still using I think you know that it was snarky. You can just own it and we can move on.

EDIT: And about being an ex-user. People and projects change over time. It just happens. That's life. It's fine to have strong opinions and be passionate but you're letting that passion take you in a bad, angry direction. For yourself, please don't do that. It's like getting upset about a divorce, you have to find some way to deal with it that doesn't involve stewing over the person who left. And that analogy is stretching it because unless you make an effort to get involved and get to know people personally, then open source developers are not your friends. They're just random people giving away free stuff on the internet in a parasocial relationship not unlike anyone else you might encounter on social media. It's not worth it to bother having strong opinions if that's the case. I can tell you, the endless Linux flame wars complaining that software XYZ sucks aren't a place where good productive discussion happens.

QUrprUd1nCeicw··on Revisiting KDE
I never denied anyone that. Go criticize all you want. Just please stop with the conspiracy theories, it's bad discussion. You don't have to be a Red Hat customer, you could pay any other Linux consultancy.
QUrprUd1nCeicw··on Revisiting KDE
GNOME can be fiddled with, just not in the same way as KDE.

And KDE can simplified for installation on work computers, just not in the same way as GNOME.

Personally I use GNOME now because it fits my current workflow better, but in the past I had a different workflow and I used KDE more. I still have both of them installed so it's not difficult to switch.

QUrprUd1nCeicw··on Revisiting KDE
No, that page is misleading because it doesn't include unaffilated developers. Red Hat may be the biggest corporate contributor, but most contributors are actually not affiliated with any corporation.

I say you're trolling because even if it were entirely a corporate Red Hat project, Red Hat still wouldn't owe anyone any features. They would still be the "volunteers" in that case. Insisting anyone meet some threshold of features for a random free product they give away is leaning heavily into toxic entitlement. I suspect you know this full well. This isn't just about a disagreement and it's not that they're putting their interests above "the user." A corporate contributor puts the interests of their paying customers over anyone else. That's how they work. But then you immediately jump from there to equating "the user" with your own personal choice. Can you not see how this is a very trolly way to approach conversation about anything? Just be clearer next time and say it's not to your liking and be done with it, you don't need to turn every conversation about this into a Red Hat flame war.

And before someone makes more trollish comments accusing me of "defending Red Hat," I don't have any connection to them. It's just bad conversation to have people trying to turn every comment thread into a hate-fest directed at some corporation. Yeah I get it, capitalism is terrible. But isn't this what we want companies to be doing? Taking labor their customers paid for and giving it back for free to open source projects?

QUrprUd1nCeicw··on Revisiting KDE
Please stop with the trollish responses. Even if that was true (it's not), what makes you think Red Hat wants to start paying those costs?
QUrprUd1nCeicw··on Revisiting KDE
Please stop with the conspiracy theories. GNOME is still very much a volunteer project. And KDE also gets corporate contributions too which they're very grateful to receive.

GNOME isn't really against "choice" either, they just optimize for a different workflow.

Page 1 of 4Next →