I only have a 3k monitor, and I can manage it. Sometimes I comment line-by-line even.
He/Him | Hu/En/some Jp | ASD | Bi | C/C++/D/C#/Java
I only have a 3k monitor, and I can manage it. Sometimes I comment line-by-line even.
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.).
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.
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).
All while anti-woke grifters be like “It must be because there’s WOMZ in it!”.
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”!
I almost did similar with SDLang as I was very desperate for a scripting language, but now I have a wasmtime API for D.
Let’s hope we also getting GPU drivers unlike on those cheaper SBCs…
Also web-native apps are a web 2.0 mistake, and lead to the abandonment of many portable GUI frameworks in favor of the “what if your pops didn’t had to install Word Processor, and instead just had to type wordprocessor.com into his browser” idea of some techbro. Do you know why your ÜBERGAMERMOUSE Ultrautility is 250+MB? Because they’re all Electron apps!
That’s actually a quite bad way of naming types, even if someone really insists on using 32 bit integers for bools for “performance” reasons.
There’s also jailbreaking the AI. If you happen to work for a trollfarm, you have to be up to date with the newest words to bypass its community guidelines to make it “disprove” anyone left of Mussolini.
Why is multiple levels of indentation bad?
IDK, but if the reason is “to break stuff into multiple functions”, then I’m not necessarily writing yet another single-use function just to avoid writing a comment, especially in time critical applications. Did that with a text parser that could get text formatting from a specifically written XML file, but mainly due to it being way less time critical, and had a lot of reused code via templates.
Issue with the US is that HFCS is heavily subsidized, and thus added to everything.
From what I’ve heard, manufacturers are afraid getting sued for dumb users breaking HDMI plugs into DP sockets and vice versa.