Robertvokac (talk | contribs) |
Robertvokac (talk | contribs) m (Robertvokac moved page Speedy Blupi Future to Future without leaving a redirect) |
||
(No difference)
| |||
Revision as of 18:40, 8 December 2024
Speedy Blupi for Windows
The support of future versions of Windows (maybe Windows 12, 13, 14, ...) to run Speedy Blupi I/II is uncertain.
It should be the key goal for us to constantly ensure, that:
- The latest version of Wine project will still support the run of Speedy Blupi I/II - at least until the moment, the complete specification of Speedy Blupi I/II will be completed. This complete specification is necessary to develop Open Eggbert - the free and open source recreation of Speedy Blupi I/II. There should be recorded as much as possible or gameplay videos for various situations in the game. It would be also good to record on the screen some visualization of the pressed keys.
Wine is developed in the C programming language.
Fortunately, there is ongoing work on the decompilation of Speedy Eggbert II. This can later be used as the engine for all the desktop versions of the game. GitHub repository: https://github.com/jummy0/sb2-decomp
Speedy Blupi for Windows Phone
Regarding Speedy Blupi (Windows Phone), it is now not possible to run Windows Phone XAP executable files on Linux.
- It seems, that no such support will exist in the future, as the Windows Phone is a discontinued platform.
It should be the goal for us to document new features and differences (to desktop version) of Speedy Blupi (Windows Phone), but also record videos of playing Speedy Blupi (Windows Phone) via "Project My Screen App for Windows Phone" [1]
It seems, that Speedy Blupi for Windows Phone (the XAP file), can be decompiled using the ILSpy C# decompiler. An alternative implementation of the XNA Framework can be used. Summary: Speedy Blupi for Windows Phone can be probably modified to run on Android, Desktop, iOS or other platforms in the future.
What programming languages and libraries to use for the next decades
Good candidates: Java, C#, C++
Bad candidates: Node.js.
Node.js and other not stable programming langugaes
Node.js is not stable, its syntax and rules change very often, there is no backward compatibility, a game written for Node.js will not work even 20 years in the future. Node.js is not suitable for long-term software.
Node.js makes possible to quickly develop software, but then its maintenance is hard.