gittea ltd was founded without adhering to the governance model gittea had and also claimed copyright on atleast the name and logo of gittea. many felt a non-profit would be a better way to organize development and thats how codeberg e.v. came to be.

the problem is not, and never was offering support and service against money, you can right now start selling forgejo if you’d desire to, it was allways about how the project itself should be organized.

https://kalpadesktop.org/ is basend on opensuse MicroOS, a distro with atomic updates. this comes with KDE, there is also a version with gnome of which i forgot the name.

the script makes various assumptions about the system ranging from

/home/deck is the users home dir, to kde plasma is the used desktop environment or can be launched from gamemode.

so probably not without tweaks ;)

that is the selling point of the head first books, they all feature bad jokes and other oddities to help you remember what you’ve read. it works.

oh, i was not aware that there is a head first just about desgin patterns, thanks for the heads up.

And Archicture is something that gets more and more important for devs, because it’s likely that the code we write is just a part of a complex system of which we don’t control every part and understanding communication channels and the reasoning behind the setup of the system allows us to write our part in a way that it works well in the bigger thing and not something others (or worse, we) have to work around later.

• Refactoring by Martin Fowler, having patterns to help identify parts of code that could be changed for the better helps a lot.
• Test-Driven Development with Python, because testing is important and you should atleast have tests in mind when writing you code, even if you dont write them first. I like this one, because it’s very hands-on.
• Head first java by Sierra and Bates, good introduction to programming with languages that offer object orientation and not as dry as the gang of four book, but definitely aimed at beginners
• Fundamentals of Software Architecture by Richards and Ford, working as a programmer often means talking with big picture people or being one yourself, and they have their own strange language.
• Domain Driven Design by Evans, for a similiar reason as Fundamentals of Software Architecture.
• Neuromancer by William Gibson, because fun is important ;)

The n64 controller is a very cautious design.

they were not sure if people(players and devs) would utilize the analogstick and chose to design the controller in a way that it could be used in the same way established controllers were used, the n64 predates the dualshock by a whole year afterall.