OIC. Good to know in case I ever have to work on some old CentOS 5 box lying around ever again.
It also looks kinda proper, using that instead of the @, so when making shell scripts, I might want to prefer this.

You get all Lemmy results! Yaay!

Sorry, that’s really all there’s to it.

Try searching Google for “Saganumenousness”

I didn’t get that.

Checked the man and it’s not deprecated. So what does it have to do with “old”?

I would have a problem if a terminal app were to do something like this, but for GUI apps, it is expected for them to make stuff easier.
And I feel like, if you were to use a slash in a file name, it would most probably be either an “or” slash or a fraction slash, so the substitution is fine in my books.

illegal characters

Not sure about calling it that, considering it is a standard UTF-8 character. (0x2044 in UTF-16)

Your machine translation is working well.

Well, considering that I am with coworkers who don’t remember when to and not to put the ‘/’ at the start of the file path (despite me explaining it to them multiple times), “slash e t c” is probably the better way.

Yeah, but we don’t know if we can do the case sensitive thingy on that, or do we?

Just tried. It processes the escape first and then finds the path with it. Essentially, making it look into a directory made by the characters before the \/.

The above was when I tried:

echo "asd" > asd\/dsa

But then I tried using Dolphin (GUI File Browser) to make a file and:

❯ ls
 1   2   3   4  'asd\⁄sad.txt'
❯ ls
1  2  3  4  asd⁄sad.txt

In the first one, the backslash is not the escape character, but part of the text.

Turns out Dolphin just replaces the forward slash with U+2044 “Fraction Slash” character, hence, not requiring any escape. I’d call that cheating, but it works well.

Isn’t there an application on Windows that allows you to open ext4? You check it out on that

I too expected it to be “et cetera”.

I used to pronounce it like yuzr, knowing that it wasn’t user, but not knowing what it was.
Now I have better context. Maybe I’ll go with U.S.R.

Maybe this article would be a good indicator.

By default, Ubuntu will give the Snap version, which Steam devs don’t like to support.
And installing another version will probably require some configuration and terminal stuff, so I’d suggest going with something that plays well with Valve.

Steam ⇒ No Ubuntu

For Word/Excel alternatives, I would suggest LibreOffice fresh. So, go with one that gives recent versions of it ^[1].

can I operate a Linux PC these days without needing to troubleshoot or type code.

That will vary greatly depending upon your Hardware selection. I was lucky enough to manage a good enough setup (adding extra effort to check Motherboard components) for Linux support and still have a few problems. [I am unable to get CPU fan speed (tachometer reading).]

I like Endeavour OS, but it being rolling on Arch, means, it is for someone who is happy with troubleshooting and bug reporting.

I had tried Open SUSE for a bit (back then, I hardy knew Linux) and liked that too.

Debian probably won’t work either, because, even though it is something you probably won’t need to troubleshoot for years, once setup, Steam will make it hard for you and Discord, well, no idea. I removed it after declining the new TOS.

sympathy for naive users, and FOSS devs mainly do not

From what I have seen, KDE devs that I interacted with, had a higher tolerance for mistakes, than I would want to have for myself.

I once submitted a wish for Kate, which was also submitted multiple times before and marked as Won’t Fix, because: a) low demand; b) nobody to do it.
But when I started trying to implement it, I as given more help than I should have asked for.

So, it’s probably just about chance. Don’t let a few rejections stop you. If you consider it useful, even if it gets rejected now, someone will see it eventually. And some programmer might find it worth implementing.

Yes.

I absolutely hated the feeling of helplessness when I found a problem somewhere, when using Windows.
On Linux, I am happy to give bug reports/ wishlist reports and follow through with them. Maybe even fix something, if I feel like I can. That (and the higher transparency in communication) makes me much more forgiving of problems I may find anywhere.

Gives me vibes of a second iteration of the OS writing boom. Though this time, the kernel mostly.

They are having to take on the burden of gently letting down other devs who are angry over a simple misunderstanding.

I feel like, if anyone would be happily willing to do that in their free time, they would have been a Politician or an HR and not a Developer.

I’m pretty n00b as a dev, but if I were to see someone misinterpreting my explanation, the most I would do is rephrase the same in a more understandable manner.
Definitely not going to resort to using “people management tactics”, specially not in an Open Source Free Work setting, where the expectation is that the other person wants the good of the project as much as I do ^[1].

Facts are more important than feelings, specially when written text is the medium, where the reader can, at any time, go back and re-read to make sure they are at the same page, which a responsible, non-sleepy, non-drunk person would do in such a case.

On this note, I went and re-read the above comment and I realise, the “But that’s the thing where you are wrong.” sentence is kinda useless. If the previous commenter were to have read the rest, they would realise that’s where they were wrong. Mental note to not use useless stuff like this as the first sentence in a reply, because I probably have the habit

Yes, I know I joined both circumstances, this comment thread and the condition of the Rust Linux dev. It seemed relevant to me.

Satellite Hello World + Telescope Hello World ⇒ Hubble Space Telescope Hello World

I honestly like the cognitive load. Just not when I am at the workplace, having to deal with said load, with the office banter in the background and (not so) occasionally, being interrupted for other stuff.
And my cognitive load is not even about the memory allocations, most of the time.

Off topic:

I think, if one is seriously learning programming from a young age, it is better to start with C, make a project, big enough to feel the difficulty and understand what the cognitive load is all about and get used to it, hence increasing their mental capability. Then learn the memory safe language of their choice.
I never made a big enough project in C, but you can get to feel the load in C++ too.