"Memory" game logic

In April I implemented "Memory" game logic in Python as limited language model and successfully converted the code to C++ by the instrument under development.

Limited language model assumes the following architecture of two parts:

1. state context
2. pure functions without side effects working only with the context

Game logic state context in Python currently looks like this (C++):

```python class memory_Context: def init(self): self.hiddenItems = []. . .

Supported platforms

To verify code portability, I selected the following platforms and languages:

• C++: Linux, macOS, OpenWrt, Windows
• JavaScript: Chrome, Firefox, Safari
• Kotlin: Android
• Python: Linux, macOS, Windows
• Swift: iOS, macOS

I created a simple "Hello World" example for each language to understand the basic requirements of each platform.

By the way, OpenWrt turned out the most complex platform to create "Hello World" for, because my TP-Link TL-MR3020 r1 router is considered obsolete since 2018. I had to use the old 17.01.7 firmware, which took about three weeks.. . .

The first Bus pattern implementation for iOS

I spent January and February making Bus pattern implementation in Swift for iOS. The end result looks nice to me.

I have also done load testing. Turns out, the Bus is 92 times more expensive than a function call. Nonetheless, this doesn't mean the Bus is bad. On the contrary, the numbers highlight the Bus should be used in architectural glue code where it can save up to 30% of code

This example demonstrates several states rendered through a single instance:. . .

On the way to portable code

To gain code portability, we have to divide whole code into two parts:

• repeatable: logic
• unique: environment

To simplify portable code construction, we want to be able to place any code - both repeatable and unique - without hierarchy requirements of operating systems. Bus design pattern seems to be the best option. The Bus makes all code chunks equal because they interact through the Bus only.

Bus-01

Currently we have:

. . .

The dream of an open source RPG is over

In 2005 the Opensource Game Studio project started under the name of the Opensource RPG, because we wanted to create "the first competitive open free game". In 2011 right after releasing OGS Mahjong 0.7 we have already had the numbers that it would take us 540 years to create RPG.

In 2011 we had a dream that we as a team would grow, which could decrease 540 years to someting reasonable. However today in the end of 2023 it's clear we are unable to create RPG.. . .

In this article Michael shares his experience of creating durable applications.

In 2013 Canonical tried to crowdfund Ubuntu Edge smartphone. Its main feature could be the ability to use the smartphone as a full-fledged PС. Unfortunatly, the crowdfunding campaign did not accumulate enough money, so a dream of having a universal device remained to be the dream.

I've been searching for universality, too, on the software side, not the hardware one. Today I can confidently say I found the necessary. . .

In this article Michael shares his experience of using Git+JS.

Hi, folks, let me share my experience of creating an application to keep track of my spendings. Specifically, let me do it by answering the following questions:

1. Why keep track of spendings in an application?
2. Why did I create the application as a personal project?
3. Why does the project use Git+JS?

1. Why keep track of spendings in an application?

I, like many people out there, wanted to become rich and successful. To become rich, one is often advised to run a personal budget, that's what I started to do several years ago. I'd like to point out that running my personal budget hasn't made me rich and successful, and I increased income simply by moving to Moscow.. . .

In this article Michael shares his thoughts on teaching folks to program in 2019.

Preface

Autumn 2019 was the third time I participated as one of the teachers in the course to teach 10-15-year-old folks to program. The course took place from mid. September to mid. December. Each Saturday, we were studying from 10 AM to 12 PM. More details about the structure of each class and the game itself can be found in the 2018 article.

I have the following goals for conducting such courses:. . .

Anyone, who watches our progress long enough, can say that we restarted the development from scratch plenty of times.

Even before releasing "OGS Mahjong", we changed the underlying technology more than once. After that, we did it again several times, throwing away already completed features. It seems that right now we have less completed features than before the release of "OGS Mahjong". It's true, but not entirely.

When "OGS Mahjong" was released, we had a descent looking (for that moment) open-source game, that worked under Windows and Linux. With some luck and effort it still works today, but not out of the box.. . .