I actually got into a fight over suggesting someone to use stock photos instead of grungy-smeary AI generated images for their (sh)articles, so at least I won’t believe it was too AI generated. Then they insisted on it being their own creation, and how they became an artist through words.

Spammers

XML has its strengths as a markdown format. My own formatted text format ETML is based on XML, as I could recycle old HTML conventions (still has stylesheet as an option), and I can store multiple text blocks in an XML file. It’s not something my main choice of human readable format SDL excels at, which itself has its own issues (I’m writing my own extensions/refinements for it by the name XDL, with hexadecimal numbers, ISO dates, etc.).

Not at all. They were wrong on certain things, which people like Stalin used to justify his own horrible stuff.

“Authoritarianism is when people want things, not when government exerts force!”

“Leftists” who are more interested in authoritarianism than leftism. At their very worst, they even ally with the far-right.

Everyone less authoritarian than Stalin (or even worse, being left of) is literally stormfront, except Russia, which is fine.

https://github.com/ZILtoid1991/newxml/tree/main

This XML parser of mine uses safe by default.

Pointers are not guaranteed to be safe. DIP1000 was supposed to solve the issue of a pointer referencing to a now expired variable (see example below), but it’s being replaced by something else instead.

int* p;
{
  int q = 42;
  p = &q;
}
writeln(*p);     //ERROR: This will cause memory leakage, due to q no longer existing

D has many memory safety features. For local variables, one should use pointers, otherwise ref does references that are guaranteed to be valid to their lifetime, and thus have said limitations.

That’s why I often recommend D instead.

Has a much more C-style syntax, except much more refined from the years of hindsight. The catch? No corporate backing, didn’t jump on the “immutable by default” trend when functional programming evangelists said for loops are a bad practice and instead we should just write recursive functions as a workaround, memory safety is opt-in (although “safe by default” can be done by starting your files with @safe:), some of the lead devs are “naive centrists” who want to “give everyone a chance at coding even if they’re bad people (nazis)”, implementing new changes to the lang has slowed down significantly up until the departure of Adam D Ruppe and the drama surrounding it, etc.

I’m very sad about kbin, I eve told Ernest that I’d volunteer with some admin work and potentially code (even if I despise PHP), but he declined, even when his health went really bad.

The sad thing is, there are other languages better at replacing C/C++ due to closer resemblance, except they’re rarely used due to lack of trendy technology that is being hyped in Rust. D lost a lot of ground due to its maintainers didn’t make it an “immutable by default” language at the time when functional programming paradigm was the next big thing in programming (which D can still do, as long as you’re not too fussy about using const everywhere).

Enough of what, nonce?🔪🪿

That knowledge needs active reaching out, otherwise you’ll just be in the “bigotry is when irrational hatred of group for the sake of doing evil” camp, which can be easily converted with “experiences”, “statistics”, etc.

I grew up in a very prejudiced family, and my family liked to scream off their lungs at me when I called them racists, because racism was supposed to be done for the sake of evil like in a cartoon, and them having “extensive experiences” of Roma wrongdoings against them makes it okay for them to throw everyone of them under the bus, for the illusion of safety.

I can see that in some circumstances, votes might need to be public due to protocol, otherwise public votes have their own uses, and so are private ones.

The “Don’t repeat yourself” mantra is also used with documentation, this leads to documentation which you first have to read and learn unless you frequently want to step into issues of the documentation assumed you read prior parts and didn’t just searched how to do XYZ.

Also while I used the more clean code oriented XML DOM implementation for my D XML parser (or at least copied such code as it was abandoned by its original creator), I planned a much simpler system for my SDLang parser. While everything originates from the DLElement abstract class, I didn’t go overboard with the interfaces, etc.

The “Don’t repeat yourself” mantra is also used with documentation, this leads to documentation which you first have to read and learn unless you frequently want to step into issues of the documentation assumed you read prior parts and didn’t just searched how to do XYZ.

“Code optimization is a cultural Marxist conspiracy!”

Don’t ask his opinions about the term “statutory rape”!