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.

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.

https://github.com/j6t/kdbg might be to your liking, but it is still a gdb frontend.

depending on the language you use there might be an IDE with a good debugger for it, if so i’d have a look at that.

have a look at venv for your future projects :) there is also some tooling to help with all the warts around python and packaging.

last bigger python project i was part of used poetry, but it’s been ages, so there is probably a new cool thing i am not aware of.

yep, story is so-so, but gameplay wise it is the best pokemon i’ve played.

gyms, league and some story fights where actually tough and required bringing different pokemons without being unfair, the port of newer mechanics like raid dens and special evolutions are well done…

i should try the pokemon randomizer mode :D

does authentik offer an option to preview a jwt for a given user? might be as simple as that the claim is not named “ocisAdmin” or is not a toplevel entry in the jwt.

not an authentik user, but after skimming their docs i think you have to:

1. create a role “ocisAdmin” via authentiks admin interface
2. give this role to a group in the admin interface or create one.
3. assign a user thats supposed to be an owncloud admin to the group

it might be that you also have to define somekind of mapper to include this in the informations owncloud receives from authentik, but as i said i only skimmed the docs and would personally just try it without the mapper.

oh, thats good to know, forgejo seems way nicer for self hosting than the limited gitlab open source core.

https://distribution.github.io/distribution/

is an opensource implementation of a registry.

you could also self host something like gitlab, which bundles this or sonatype nexus which can serve as a repository for several kinds of artifacts including container images.

hotwire(turbo+stimulus.js)

used it with a java (spring) backend and with a python(flask) backend to get rid of some page reloads and an easy way to display information based on something happening in the backend via server sent events. did not need to do much more than wrap parts of the existing html templates in <turbo-frame>-elements and the client code to handle server sent events was pretty small to. fun experience, especially because most of my code stayed in languages, iam way more comfortable with than javascript.

htmx would have worked simmiliar, but i had prior experience with turbo, so i used that.

https://emudeck.github.io/ makes setting up a lot of emulators pretty easy on the deck.

i’ve played mario sunshine and the metroid prime games on it, so i’d think most of the wii and gamecube games wont be a problem.

hell, people are playing switch and some ps3 games on it so i everything from before the gamecubes generation will probably be fine, unless the emulators for a system are not in a great state in general.

The Flashpoint Launcher (FPL) is a desktop application made for browsing, storing and launching other applications (games, animations, web apps etc.). It is specifically made for Flashpoint Archive, a non-profit with the goal of furthering archival and accessibility efforts for games, animations and other digital interactive experiences on the web.

Flashpoint Archive seems to be a collection of mostly flash media content (think games on newgrounds or kongregate in the 2000s up to the death of flash)

for any one else wondering what this is.

I’ll have to take a look if i cand find that zombie wave defense game i used to play during compsci classes or the one about shooting a hamster into space.

multiple other objects might be holding a reference to the object you want to change, so you’d either have to recreate those too or mutate them to let them point to the new object.

however if you can do what you want to do in a side effect free way i suggest doing that, as it is indeed easier to reason about what happens this way.

mainly java dev here:

if i only have few classes i want to serialize/deserilize i implement the logic for that in the class, if they need special logic for that, and implement the serilizable interface. writing objects to somewhere or reading them from somewhere belongs in a different class.

if i have a lot of classes or use a framework like spring i’ll employ whatever they offer for serilization and deserilization or more likely a databinding library like jackson.

other languages with classes or structs offer simmiliar options(pythons pickling and unpickling or the json package in their standardlib for example) so my approach would stay mostly the same.

that this does not make us fools is exactly what i wrote.

i am just tired of that “joke” that developers don’t understand their own work. its neither funny nor does it help anyone.

i hate this joke.

yes, trial and error is part of the process, but that does not mean we are bumbling fools that don’t know how or why things work. trial and error is part of any complex endeavour or learning new things.

when i started programming i struggled with getting stuff to compile, because i didn’t know the language i was using well, i later struggled with getting my code to work on other machines because i didn’t understood how to package it.

we absolutely get more competent, but we use complex tools to do complex stuff and we seldom have to produce the exact same thing twice, so of course we often find ourselves in somewhat uncharted territory.