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.

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.

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.

It’s not just about bad/good C programmers. It’s also about how much of the context, the given C programmer has read to make sure they know enough of what they are doing.

No matter how good one is at Programming, they need to make sure to read and remember what is happening in relevant parts of code, while making their one off contribution.

That’s where the part of “leaving it to the computer” comes in. Hence, the usefulness of code checkers and even better if the compiler itself enforces the stuff. As long as the rules are good enough.

Let’s just hope we are not jumping to another language 20 years down the line.

Anti Commercial-AI license

Even if you manage to keep all memory accesses in your memory, while writing the code, there’s a good chance you’ll forget something when reviewing another person’s MR. That’s probably the main problem creator.

Still, a language that you are familiar with, is better than a new language that you haven’t finished reading the specifications of. And considering that adding new maintainers comes with a major effort of verifying trustworthiness, I get how it would be harder to switch.

And automatically numbered too! Nice.

Though for me, instead of a scrolldown effect, it reloads the page on clicking the link. Trying a second time, it does the scrolldown properly. Weird
But that’s just an implementation detail and as long as this is standard, I’ll just start using it.

Thanks

I have been stopping myself from using those and instead restructure my sentence. But if people like it, guess I can start keeping it.

I do find it more useful, however, to have a kind of a reference to the thing written at the end instead [1], but markdown doesn’t seem to have anything for that, and using the syntax for Markdown references, is only useful for hyperlinks, or if the reader is willing to read the hover text 2.

[1]: Like This. I would love it if the markdown viewer would link the above [1] to this line. Maybe with a scrolldown effect.

Well, I got to dream for a bit…

Or it could just be laziness.

In case you don’t want to put the effort into making a system into your organisation, to update code in a public-facing versioning system hosted setup, just tell someone to zip whatever you compiled and package it along with the rest of the stuff.

• Packaging the whole .git directory would make it significantly larger
• This method is bankruptcy-safe, as compared to hosting on the internet.
  • Ideally, I would like there to be both, a zip (in case I don’t have an internet atm) and a link to the vcs
• Yes, the companies mostly don’t care enough and people doing it won’t think of it as being hostile, just as putting the least effort.

simply zip up their code and send it to the AGPL’ed software owner

That seems good enough to me. No?

Sure, it would be nice to have the whole versioning system history, but even having the current version of the code makes it possible to do a code review. And modification too.

Self-Building and deployment might turn out to be harder, but that would just be about which side is having to put the effort of making something comprehensive.

So the OSS projects that have been closed due to Cease and Desist notices are actually still viewable !?

Well, guess who’s not buying next gen Ryzen?

They are doing similar stuff with deliberately delaying Linux driver capabilities for Radeon 7xxx series, to make more GPUs die out faster, by overheating (zero RPM fan until 60°+).

Now we just need a friendly neighbourhood nanoscale fab.