Because they want to replace them with more corporate-controlled languages.

Just add @safe: after your module declaration, and you’ll be safe by default if you don’t want to wait until D3.

Also, unlike in Rust, you can opt-out from RAII with int foo = void;, although it primarily has a performance advantage with arrays, not singleton variables (might be also useful for aquiring an RNG seed in a dumb way).

Not if you opt in it. You can even put @safe: in the beginning of your D source code, then you’ll have a memory safe D (you have to opt out by using @trusted then @system).

I personally prefer the memory safety tools offered by D over Rust. D also doesn’t come with const by default, and you can even opt out of the RAII stuff a certain graphics driver developer boasted about in the Linux developer mailings (RAII can be a bad for optimization).

/// Throws: MoneyNotFoundExcetion if person does not have enough money

D

I only have a 3k monitor, and I can manage it. Sometimes I comment line-by-line even.

It’s time to return to the roots, the times when you used goto instead of function calls! Fortran and COBOL all the way! /s

Once you look beyond the “git gud” and “we must gatekeep programming from the normies” aspects of coding, you might want a language that is either way more productive than C (D), a language that offers memory safety and functional programming paradigms (Rust), or even a language that has relatively good portability even at the cost of performance (Javascript).

If you’re only grumpy about Electron apps, then be mad at the corporations that:

• forced colleges and universities to teach Javascript and nothing else to students, so now we have programmers afraid of type declarations,
• jumped on the “Big Data” and “software as a service” train, so every app needed to be a “website”, because “it’s so convenient, pops no longer need to install wordprocessor dot exe, just type wordprocessor dot com into a browser”.

If you thought misspelling a variable was bad, then get ready for misreading documentation of OS API, then not realize why your implementation doesn’t work for a quite a long time.

This is highly inaccurate:

D: Esperanto. Highly derivative of C (Latin), designed by people previously writing compilers. It’s not being taken seriously as such.

Russian is nowadays being speaken by right-wing authoritarians instead, and any programmer that is auth-right is either coding in C/C++, or a Javascript/Python dev pretending to be a C/C++ dev to “gatekeep” nulangs (sic).

Leaked Windows code made Wine and ReactOS devs anxious, since MS could sue over it. On the other hand, I’ve looked up the keycodes from the Linux kernel for X11 (it’s literally just PS/2 with the unused codes being used in place of the E0 keys), and they haven’t yet came after us.

D seems to getting traction yet again, and some stuff might get better (D3, new GC, new standard library, etc).

While the borrow checker has its downsides, so its legitimate uses. A few people in the D community were thinking about implementing it as a library.

Some of these people are Javascript web developers idealizing system development and the C language.

I called the SWAT on them.😈

Update: The SWAT came to my home!😅

gigachad_yes.gif

https://www.youtube.com/watch?v=AzezZhvIyS4&t=17070s

https://github.com/ZILtoid1991

Please, do pull requests on my projects! I might even accept them.

There’s a third state: “Where’s the documentation on how to do <commonly done thing>, so I don’t have to steal it from a GPL code?”

Same for enemy AI, for which I’m planning to implement some fuzzy logic support into my game engine, if there’s no solution for it already in some D library.

What does pring do?