I did not expect such a detailed code review (the fact that you wrote it on mobile impresses me even more), but I strongly agree with everything you mentioned. I think I was so caught up learning GLSL and its quirks, then playing and experimenting with the simulation, that I "forgot" my coding standards. Anyway, I'll make sure to take some time to update both the code and the article following your recommandations.

Ce n'est pas mon analyse, les blocs de citations que j'ai postés sont directement tirés de l'article (d'où mon autre commentaire qui dit que l'article est intéressant malgré le choix de son titre)

Hum, je crois que tu t'es trompé de post ? :)

Thanks for the details ! Still curious to know how a new instance, with an old domain and fresh keys, would be handled by other instances.

I'm pretty sure they are actually hosting it. The tech is quite different (cofractal uses urls ending with {z}/{x}/{y}, while their tile sever uses this stuff that works quite differently)

I'll try clarifying what I had in mind :

I tried running maptiler to generate tiles from OSM's data, which required an insane amount of time and resources (not doable for most self-hosters including myself, even for a single country) to process the data and store the results. I was wondering if there would be a way to ask maptiler (or another equivalent tool) to only generate tiles that contain points from a given set (in this case, photos) and maybe the tiles adjacent to them. What about doing this for every zoom level ? This would require generating at most zoom_levels * n_photos (* 9) if we include adjacent) tiles, and a lot less for the typical person taking several photos at the same place.

At this point, I don't know if you are trolling or not. You keep saying that this is nothing like timezones, while describing something that really looks like timezones to anyone else reading it.

Do you suggest we all use one unique time, regardless of local solar time? Or do you suggest we all use our own local solar time, based on each person's exact longitude on the globe, regardless of borders and current timezones ?

I prefer the CLI as well, but when I'm not a dev I supervise practical works in programming classes, where I don't have much saying in the recommended/required tools

I am not an actual teacher, I only supervise practical computer science work aside from my dev job, so I have no saying in what is taught. But don't worry, this is only a very basic introductory course, no factories, not even inheritance. Only classes, attributes and methods.

I can think of some "programming best practices" that can help with reducing merge conflicts, such as making small functions/methods, but I see it as a positive side effect.

I don't think avoiding merge conflicts should be a goal we actively try to reach. Writing readable code organized in atomic commits will already help you get fewer conflicts and will make them easier to resolve.

I've seen too many junior and students being distracted from getting their task done because they spent so much time "coordinating" on order to avoid these "scary" merge conflicts

Well, it kind of makes sense to give a figure in such an unit. It allows you to quickly calculate how much you're gonna spend on your electric bill (but only if you're based in the US), since all weird conversions are already done

What do you mean? Are you talking about the hash being spoofed?