Programming Languages

The choice of programming language for your Next Big Project can be difficult. Even worse, it can seem easy… when it is not. On the one hand, strictly speaking, you can write any program in any of Turing-complete languages. On the other hand, that doesn’t mean it will be easy. In fact, writing a program in a poorly suitable programming language could be extremely difficult.

‘Speedy Gonzales’ Serializing (Re)Actors via Allocators

May 1, 2018 by “No Bugs” Bunny

Serializing Allocators

Quote:

Allocator-based serialization for (Re)Actors is extremely fast (for x64 – around tens of ms per 100MB of state)

Another Quote:

Per-(Re)Actor allocators can be implemented without any changes within (Re)Actor itself (i.e. all the necessary changes can be confined to Infrastructure Code).

Filed under: On.ProgrammingProgramming LanguagesOptimizations

Read more

Using Parallel (algorithm) Without a Clue: 90x Performance Loss Instead of 8x Gain

March 27, 2018 by “No Bugs” Bunny

Parallel vs Single-Threaded

Abstract:

I made an experiment which demonstrates Big Fat Dangers(tm) of implying that parallelization can be made as simple as just adding a policy parameter to your std:: call.

Quote:

it is still necessary to understand what we’re doing

Filed under: On.ProgrammingTips and TricksProgramming LanguagesOptimizations

Read more

On Programming Language Complexity, or Our Brain as a CPU with 7+-2 Registers

March 20, 2018 by “No Bugs” Bunny


Quote:

Let’s consider our brain as a CPU, which consists of the control unit, ALU, and 7+-2 registers.

Another Quote:

Moving C++ one step farther from being a brainfuck is IMNSHO always a Good Thing(tm)

Filed under: On.ProgrammingProgramming Languages

Tagged With: C/C++GCC/Clang
Read more

A Usable C++ Dialect that is Safe Against Memory Corruption

March 14, 2018 by “No Bugs” Bunny

Memory-Safe C++

Quote:

we DID get a perfectly usable C++ dialect which is also 100% safe against memory corruption and against memory leaks.

Another Quote:

we can (and often SHOULD) have different approaches to safety of the Reactor::react() and the rest of the code.

Filed under: On.ProgrammingProgramming Languages

Read more