@jestdotty I knew historically it used to be an insult, but I thought that fell out of fashion before I was born, and at least in my circles it's just a convenient monosyllabic word for all non-binary people. Either way, to be non-binary in a country where even gay marriage only has a slim majority support requires thick skin so they don't really tend to mind what I call them within reason.

@retoor to clarify, I _know_ that "they" applies to a person whose gender you don't know or don't want to specify. I _believe_ that it also applies to a person who has different preferred pronouns that aren't relevant to the discussion, by the same exact mechanism. This is the controversial part of the argument, not the fact that the neutral "they" is at least as old as book printing in England.

There are a lot of reasons why you would want to refer to a single person of unknown gender, most notably unborn children and authors of text records, but also distant figures in the wilderness, titles which may belong to anyone in the future, and roles in the abstract such as customer. Everybody used "they" and no one gave a fuck for centuries. When queers wish to leave their gender unspecified, no matter how much history you invent, your problem isn't with the linguistics, it is purely with the queers.

@retoor The gender neutral singular "they" is older than the new world. If you were that old, you'd be bitching about improper use of "you" in place of "thou".

to be entirely honest, besides everyone whom I only know by handles, I also use it for outspokenly anti-trans people to piss them off. The fact that even when they're fully invested in their gender they rarely notice is further proof that it's completely universal in practice.

@retoor I firmly believe that "they" applies to everyone, so I can use it for anyone whose gender I'm not sure about or unwilling to memorise. It's a perfect middle ground because everyone except for casual allies like myself hates it. yet I've not heard an argument why it's actively offensive to any soul on this Earth.

Carpet denim indeed. Smell the roses.

@donkulator Hello world in Haskell is simpler than in most programming languages actually, so is the slightly complicated version with customizable names.

@donkulator top-level statements are useful if the top level program counter is useful, so typically in tools that do a well-defined task in a series of distinct stages and then halt.

In a program that spends a few seconds starting and stopping and days in between processing requests, the part readers should be focusing on is the dispatch mechanism, so top level statements don't contribute anything.

Top level statements in files other than the main entry point are awful. There was a time when C# didn't allow them, and I worry they relaxed the rules only to mitigate the equally bad idea of forcing every helper function into a class.

not been developed since 2019. We survive until the credit card on file expires.

@BordedDev modern c# can just do

Console.WriteLine("Hello World!")

it'll automatically get wrapped in a class and a method.

@Demolishun in middle school when we started programming I used to read MSDN in the evenings, it was very casual and clear for an utterly clueless maths nerd, and the examples explained pretty well why each language feature is useful.

@PaperTrail your boss has mastered thinking at scale about problems that are one-off and pocket-sized.

the only supported version of C# where this is still the case is the 4.x branch, which is going the way of COBOL and is in no way similar to modern .NET; you're complaining about the legacy version of a language that has already moved on to better problems in the main branch.

More than their own problems, LLMs reveal that a worrying proportion of people decide whether they should do something purely based on social pressure.

Are you my colleague?

It amazes me how some people will just ask a third party to do their job and assume that it's done because the third party said so.

@12bitfloat they do, but uBlock would never work with plain MV3 so "Chromium except for Chrome" is still a reasonable distribution target. Proxies don't want to keep supporting MV2 just because Chromium's implementation of MV3 is rushed and crap when all the functionality they need is part of the standard they develop against.

@12bitfloat MV2 is not needed for this in theory because MV3 offers an authentication callback, that callback is just not called in Chromium for some fucking reason.

@jestdotty the comic is edited, which means that the original message by stonetoss was some other nazi nonsense, and I couldn't think of another message that fit the comic well at first.

@jestdotty nazi doctrine is usually predictable but this time I have no idea what the heck else herr Toss could've originally written.

edit: actually, I bet it's about dei

I think the welfare state is going decently well across Europe, it's not great for everyone but it has been softening our concept of a really hard life, and it persisted for a while, and I think these two are some of the most important metrics of success for states, so I don't think we lack a path forward. That being said, it's certainly worth some experimentation.

@Demolishun Right, well, transnationals aren't known for that.

@iiii every Firefox user I know did at some point within the last year. The best assessment I've ever heard is "it doesn't break too often" or "it's just a reload so it's fine".

@iiii I have used firefox mainly for as long as I can remember, but YouTube works better on Chromium, as does Discord, Roll20, code-server, and a bunch of others. In this case I needed to proxy Discord because the company blocked it.

incredibly cool shit

it's still there when I re-open the rant editor usually, not sure why it isn't for others. Is this a Firefox thing, saving values for forms?

GNU Screen solves a problem that only exists because SSH is an underdesigned protocol that conflates transport layer connections with user sessions. I need to repeat that no modern program does this on purpose, not even developer-oriented ones, not even security critical ones.

And the only SSH module where this behaviour is actually justified is tunneling since this way the socket breakage gets transparently propagated to sockets within the tunnel. SFTP should be a sessionless request/response protocol that allows the underlying socket to timeout to save resources and transparently reconnects for each operation if needed, and shell access should ping by default and auto-reconnect with exponential backoff.

Tying sessions to TCP sockets is not taking a hit, that's breaking on literally the first hit. It's like resigning from your job because construction work prevents you from taking your usual route, and then re-applying if you find a new route. The only applications that do this are ancient programs from a different internet like SSH and shitty indie games.

@retoor SSH sessions end when the TCP socket breaks, do they not?