He/Him | Hu/En/some Jp | ASD | Bi | C/C++/D/C#/Java
From what I’ve heard, manufacturers are afraid getting sued for dumb users breaking HDMI plugs into DP sockets and vice versa.
“You will be more conservative as you grow older” is not a truth, but a threat. If you don’t become a conservative under their regime, you won’t become old.
I only have a 3k monitor, and I can manage it. Sometimes I comment line-by-line even.
Strongman leaders create hard times.
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.
Fair point, at least they should give us two USB-C ports, at least on the flagship models.
Best if you get one of those USB DACs. Those even work on a PC with a converter.
And then you can sell USB-C -> Jack converters (which break after a while - I’ve dismantled one for recycling for my Raspberry Pi, later I might make one epoxy potted for my phone), easy to lose wireless earbuds, etc.
Headphone jacks can be waterproofed, manufacturers are just lazy.
Phones are so thin now that people are crying back the thicker ones…
Someone should saw off the legs of the techbros that came up with the idea of removing the headphone jacks from phones. Just like the headphone jacks, legs are technologically “superseeded” by cars and electronic wheelchairs.
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.
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.
❎️fixing her
✅️accepting her for what she is while accomodating her needs
Now I need two things: