Xargon/Wiki
1
0
Fork 0
mirror of https://github.com/RetroDECK/Wiki.git synced 2024-11-23 14:15:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

wiki

Browse source
This commit is contained in:
Lazorne 2024-02-24 11:09:48 +01:00
parent 9aff60237e
commit ce30f837e1
1 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
wiki-rtd/docs/wiki_about/story-philosophy.md
View file

@ -6,21 +6,20 @@
Let's take a step back. Let's take a step back.
RetroDECK was born on March 4th 2022 in Kyoto, Japan, with the name of `351EDECK`. RetroDECK was born on March 4th, 2022, in Kyoto, Japan, with the name of `351EDECK`.
I am also one of the founding members of `351ELEC` now [AmberELEC](https://amberelec.org/). I am also one of the founding members of `351ELEC` now [AmberELEC](https://amberelec.org/).
What I wanted to do was to "port" `351ELEC` to the Steam Deck, but instead of doing a custom firmware to flash, doing it as an application that could be launched from Steam. What I wanted to do was to "port" `351ELEC` to the Steam Deck, but instead of doing custom firmware to flash, I wanted to do it as a full application that could be launched from Steam.
Eventually, after talking to the other team members, we decided that we didn't want to support another platform such as Steam Deck, so I decided to continue the project on my own, renaming it to RetroDECK.
Eventually, after talking to the other team members, we decided that we did not want to support another platform such as Steam Deck, so I decided to continue the project on my own, renaming it to RetroDECK.
Back then I had many options on how to create `351EDECK`, such as a bash script, appimage and flatpak. Back then I had many options on how to create `351EDECK`, such as a bash script, appimage and flatpak.
In the beginning I opted for a simple shell script, in fact `RetroDECK` aka `351EDECK` v0.1a existed as a mere shell script. In the beginning I opted for a simple shell script, in fact `RetroDECK` aka `351EDECK` v0.1a existed as a mere shell script.
However I had bad feedbacks from the community because someone was feeling unsafe to give my script the root privileges so evaluating the Steam Deck use case I felt like it was not the right direction to take, the people was not feeling comfortable to give the sudo to a random script downloaded from the internet, so they asked to packetize it in some way. However I had bad feedbacks from the community because someone was feeling unsafe to give my script the root privileges so evaluating the Steam Deck use case I felt like it was not the right direction to take, the people was not feeling comfortable to give the sudo to a random script downloaded from the internet, so they asked to packetize it in some way.
Valve suggests the flatpak technology to port the applications on Steam Deck so, I decided to follow their guidelines, and I created the `RetroDECK` that you know today, starting from a Manjaro virtual machine as a development environment because I didn't have a Steam Deck yet. Valve suggests the flatpak technology to port the applications on Steam Deck so, I decided to follow their guidelines, and I created the `RetroDECK` that you know today, starting from a Manjaro virtual machine as a development environment because I did not have a Steam Deck yet.
// Xargon // Xargon (Project Founder)
## What is RetroDECK's philosophy? ## What is RetroDECK's philosophy?
Emulation is a global multi-generational effort of development that has lasted for decades, motivated by the pure love for video game preservation for current and future generations. RetroDECK depends on the constant development of all our dependencies (the emulators, front-end, various assets, etc…). It would be unfair to both the hard work that has been done in those projects and to the entire open-source community if we said otherwise or tried to take credit, conceal, or obscure it for our own gain. Emulation is a global multi-generational effort of development that has lasted for decades, motivated by the pure love for video game preservation for current and future generations. RetroDECK depends on the constant development of all our dependencies (the emulators, front-end, various assets, etc…). It would be unfair to both the hard work that has been done in those projects and to the entire open-source community if we said otherwise or tried to take credit, conceal, or obscure it for our own gain.