What you’re describing aren’t issues with Wayland.

Your complaints are that you’re using old versions and poorly designed software.

Those aren’t Wayland issues they’re poor management and lack of investment

That’s not semantic versioning…

It could be implemented the same as most email clients do. A simple message “load external content” with an option to always load.

What do you do differently? I’ve been on Bluefin for 2 years but still never bothered with dev containers or anything

It’s hardly diminishing your anonymity. There are plenty of services to create an anonymous email account.

Didn’t even need remote version control. All it required was essential files version controlled in the local folder.

Your comment “This question does not belong here.” currently has 22 downvotes and 1 upvote.

To me that suggests your view is in the minority.

There was a discussion about “ghost communities” a few days ago:

https://feddit.uk/post/24499702

People are quick to create communities but they sit unused, attract few posts and fewer subscribers. Often the mods move on so even if new posts were to appear they’d be unmoderated.

The simple reason for that is there isn’t enough demand. Lemmy is still small it’s too early to be spinning out ever more narrowed niche communities. If you think content belongs elsewhere then report it to the mods and let them decide. If they see a surge in unwanted Q&A topics then they can amend posting guidelines to direct people elsewhere or to a Q&A thread or something.

Creating a new community for one question is insane.

If there’s a surge in questions not relevant to 90% of readers then sure but Lemmy isn’t there yet

Is there an easy way of seeing the preceding emails in a threaded format?

I read some posted yesterday that were related but it’s damn confusing whether the conversation has been active in between?

https://feddit.uk/comment/15366243

@dengtav@lemmy.ml

This answer is probably the best here. It’s concise and answers your questions in a reasonably unbiased way.

A lot of the other answers are dripping with personal bias and a few verging on conspiracy.

OP wants to store all of their porn collection in RAM

understand what is the common idea about the fact that systemd could be a critical part of Linux which is in the hands of IBM and Microsoft and what this means for the linux community overall.

Either nobody cares, or it’s too much complottistic to be real.

I wasn’t familiar with the word complotism but yes I think this is the case - It’s just an unsubstantiated conspiracy.

Even if were true that Microsoft had taken over systemd by stealth. What is the harm? If they suddenly do something malicious with it then all the distros will just fork systemd and continue without the malicious elements.

I’ve read the update you made to your original post.

So I now understand your concern is Microsoft control systemd and the proof of that is that the project lead works for Microsoft? Is that the only proof?

I think it’s quite a grasp. There is no money in open source so the developers need jobs. In this case the developer happens to be employed by Microsoft.

I was impressed they resisted calling it micro$oft. That’s the usual sign of somebody adopting the tribal views of others.

In that case why not share your opinion?

Instead you’ve claimed you’re neutral and shared links to the views of 15 other people.

You haven’t even provided any context on these articles. Or quoted anything from them that you are concerned about.

Everything about this screams you’re asking in bad faith just hoping to waste people’s time or start an argument.

You provided 15 links.

Are you seriously expecting somebody to walk you through each one?

You’re claiming not to care either way about systemd and yet you’ve provided 15 sources against it and apparently done zero research into why it has been so widely adopted.

So, you don’t know Python at all AND you don’t know Bash, but you feel compelled to talk about how one is so much better than the other?

I have plenty of experience with Bash, hence why I was eager to question the implication that bash was less complicated than other solutions.

You’re correct that I don’t know python, but I do have plenty of familiarity with PHP, JS, C#, and Rust. From my experience with those languages I guessed that python probably has similar libraries for making API calls.

Thanks for providing the actual examples. Looking at them I’m curious if you still think I’m wrong?

In my opinion the bash is much more difficult to understand than the python and therefore it’s more likely for bugs to creep in. For example I think curl_exit_code=$? should be called immediately after the curl command as the way it’s presently written isn’t it capturing the exit code of the tail command?

You’ve explicitly called --connect-timeout and --max-time. imo it only comes from experience that you need to add these options. I had a script that had been funcitoning without issue for months then suddenly started to hang and it was a while before I figured out that the defaults for curl had no timeout so it didn’t gracefully fail like I would expect.

These are the kind of traps that I fall into all the time with bash and it’s painful to debug.

response=$(
  curl \
    --silent \
    --write-out "\n%{http_code}" \
    --connect-timeout "$CONNECT_TIMEOUT" \
    --max-time "$MAX_TIME" \
    "$API_URL"
)

http_body=$(echo "$response" | sed '$d')        
http_code=$(echo "$response" | tail -n1)

curl_exit_code=$?

Show us on the doll where the shell script touched you…

Everywhere.

I believed bash would be enjoyable, I believed we’d have fun. But all it ever gave was pain. I was young and naive.

That’s profoundly untrue. Scripting in bash is an indescribably painful experience.

You have absolutely no idea what version of a binary the user will be running so you’re limited to using only options that have been well established.

I’ve never worked with python but I understand it has at least got some semblance of package management providing assurance that methods you’re calling exist, and I imagine it has some standardised mechanism for handling errors unlike bash.

A simple example is making a GET request to an API and deserializing a JSON response if its successful, handling a timeout if the server can’t be reached or handling the HTTP status code if it’s not a 200 response.

JS, python, Rust, C#, Java etc will all handle that simple scenario with zero effort but in bash it’s a nightmare.