I’ve read interesting argumentation against nesting. I’m not confident in whether it’s more useful or not, in some situations or in general.

praise thy

I like to tinker, I like to implement and improve things for myself, I like the idea of collaborative and public good efforts being to the advantage of everyone, I’m a very good systematic and structured thinker, I like learning, I’m good at it, I like efficiency, I like creativity, I like some stuff that you can get out of it. And for better or worse; honestly worse; I have nothing “better” to do, so I end up with projects even after work.

It was not a conscious decision to get into it. I slid into it. Using software and web, contributing content, changing websites, themes, game scripting, hosting, and then more and more development.

I can certainly understand and relate to loneliness within the job. I’ve been fully remote for a long time now, with social anxiety, which at the same time makes it more sustainable but also not a good or healthy situation.

I’m lucky to have a very small and good team, work environment, and customer. Such a good situation makes it hard to leave as well.

Do you think that applies to this question?

Null coalesce operator vs comparison operator precedence? Both questions are about that. I don’t see one having a different answer to the other. In that case, duplication would only lead to spread out partially outdated information, instead of one place being updated.

I asked 1 high-quality question in 2024, and it was closed almost immediately, and I haven’t engaged with the site since.

If someone with 20,000+ karma has their nicely-formatted questions closed so quickly, what must the newbies and rank-in-file encounter? This is probably a big reason why it’s declining.

It’s a high quality question, yes.

The close as already answered elsewhere is valid though. It’s not saying that the question is wrong; at least a decade ago StackOverflow explicitly allowed and encouraged asking the same question in different ways so they and their answers can be found.

It’s about operator precedence. And the referenced question asks the same thing, about ?? and a comparison operator.

The head note says:

This question already has an answer here:

Notably, it refers to answers, not the invalidity or duplication of a question.

The header also mentions [previously] opinion based, so I looked into the question edit history. It most certainly was not a “high quality” question at the beginning - at the very least to the degree it looks like now.

Title: “is finally rolling out to the wild”

Content:

Ahead of Legion Go S shipping, we will be shipping a beta of SteamOS which should improve the experience on other handhelds, and users can download and test this themselves.

So, neither that product is rolling out yet, nor the SteamOS beta is rolling out yet?

(This quote is from Valves announcement, but meaning-equivalent to the linked article sentence regarding it.)

Exactly. It’s a matter of barrier and interest. Signup requirements are a barrier to drive-by improvements and reports, and them as entry points to further contributions.

PDF is a broad format with various standards and formats. Which ones does PdfDing support?

https://github.com/Stirling-Tools/Stirling-PDF

Your link is broken, linking to https://programming.dev/post/Stirling-PDF

Their README has a section regarding that https://github.com/mrmn2/PdfDing/blob/master/README.md#comparison-with-stirling-pdf

… Stirling PDF focuses on performing various operations like splitting, cropping and rotating on your PDFs. PdfDing however has a different focus, it is all about reading and organizing your PDFs. …

You picked one concern of multiple: Code discoverability of an already known project.

Multiple times I have found project sources on their own platforms, and when I would have contributed tickets or code, I did not because of requiring yet another account on yet another platform, with whatever yet unknown signup workflow.

And there is man other concerns, some of which the comment you are replied to mentioned.

Pushing commits is just one of many concerns.

Do you want to suggest synchronizing issue tickets as well?

Account requirements seem like a worthwhile safeguard against spam.

Projects can still use and accept emails or whatever outside of GitHub.

We don’t need to trust anybody.

Reviewing every change and discovering every issue is unfeasible on multiple levels. Even skipping that fundamental, base level requirement; you need to trust in trustworthiness from submitters and reviewers, and that people review. You need to trust those maintainers that can push and pull and merge. You need to trust the builders and publishers and distributors.

I doubt you’re reviewing every code change and compiling or verifying reproducible builds on every software and patch version you run. You put trust in the chain. And the chain decided to cut at some point because of risk.

Besides, the idea that employed developers with a Russian day job are a risk… but one fails to consider these were the honest ones who declared their day job.

So you think people do only one job and have only one concern? Do you think people of sanctioned countries, contributing to an unjust war, more or less directly, are a bad place to start reducing risks?

I feel like properly vetting commits to the kernel that does not involve the core contributors and maintainers too much is the way to go.

I’m baffled you can make this point while at the same time not accepting their decision after review, assessment, and consequence. You’re asking them to review while not accepting their decision. From the same people.

I think your dim repo first impression could be improved; with a repo description (there is none), and instead of a description that requires pre-knowledge and one huge example, a more general, novice-friendly description and intro listing positives and short intro examples demonstrating distinct functionalities/advantages.

its a javascript UI framework

a very satisfied field, with a lot of established mainstream options

Microsoft needs some serious regulation.

Given their OS prevalence, their forceful push to cloud and cloud system user accounts is unacceptable. Optional suggestion would be fine; but they’re doing the opposite.

OS upgrades forgetting other programs and other program file associations while at the same time making it much harder to change them is unacceptable. Offering or suggesting their own products in a non-intrusive manner would be fine; but they’re doing the opposite.

There’s much more to criticize. But those are the worst and obviously unacceptable offenders to me.

Some niches switching to FOSS won’t change their dominance or behavior. Only forceful regulation by state unions will.

The post weblink target doesn’t seem to even play the video but redirect to a different video website.

This video is not available on this instance. Do you want to be redirected on the origin instance:

he l p

looks like a multi-threading or concurrency issue

Has features ✅