But will it fuck up my formatting when I add an image?

Ctrl+Shift+F+U+F

Hold up…I mean, yeah. Okay.

Good point. We’re a bunch of badasses.

And maybe they figure EU leaders aren’t smart enough to ask for reproducible builds.

…or if any part of the data processing happens on US soil…

“Are we the baddies?!”

was there some other reason?

Compiling to an additional OS, today, can be a pain in the ass.

Compiling to an additional OS, a couple decades ago, was a monumental ongoing never ending pain in the ass.

It’s weird to me that there isn’t a full four paragraph rant in the Wikipedia article about J# - just complaining about how everyone’s first “Hello World” was guaranteed to fail to compile due to bugs in the file rename algorithm.

The usability failures in J# are the stuff of legend.

Thanks. I hate being reminded about J#.

I have never of anyone calling C# Java.

Sounds like you missed the fun of it’s first release. We (C# developers) all called it Microsoft Java.

Edit: I remember answering the question "What the hell is C#?!” with: “It’s Microsoft Java”.

It gave folks new to the language all they need to know: It aimed to solve the same problems as Java, and didn’t have Sun’s commitment to Open Source behind it.

HTTP works pretty well, if you don’t mind various governments spying on the traffic.

Plan to share a link so the hackers can check your work?

I’ve heard good things about vibe coding primary use cases for common problems.

I have experience vibe coding unusual use cases. The AI was worse than useless for those.

So I’m curious how the corner cases and security stuff on common problems turn out. (I always get that kind of thing from a library, so I have no experience vibe coding those cases.)

(Genuinely curious. And obviously, no worries if you don’t want to risk sharing.)

It’s funny that Ouya’s brand recognition is so infamous that no additional explanation is needed.

Another tip I haven’t seen yet:

• It varies by client, but Markdown generally works, here.

• Spoiler tags seem to still be a separate extension from regular Markdown.

• Many of us try to be more careful to include ALT Text with images, as it supports both blind users, and anyone whose server is just being slow to load images:

Example of Image with Alt text in Markdown:

![alt text](/path/to/img.jpg "Title")

Here’s one I haven’t seen mentioned yet: many of us explicitly state our intended tone after our comments, to avoid miscommunication. Particularly in busy threads.

We have some great accessibility outreach communicators here, some of whom have shared how much it helps them or people they know.

Some examples:

• (Sarcasm)
• (Genuine)
• (Joke)

Sometimes these are abbreviated, but we often even avoid abbreviation - for general clarity, but probably mainly because we’re always gaining new users who might not recognize the abbreviation.

This is a great point.

There’s also very convenient block mechanisms for rude folks, and a “block and move on” culture for those who don’t keep their communication civil.

But why?

Probably because having two separate dependency management solutions can lead to a lot of needless headaches.

And it makes particular sense for Gnome to switch over, since Gnome is focused on user space apps. Flatpaks should generally be more relevant and lower risk, long term, since they don’t require root privileges to install.