Must be binary…

I think every school in the USA needs a geostationary satellite with a high-powered laser so that any school shooter can be vaporized at the speed of light. Without high-precision orbital strike capability, the USA won’t be able to solve their gun problem… I mean, what else could you possibly do to combat gun violence… 🤔

I’m glad you liked the idea of the world building twist, and I think I agree with everything else you said as well. Thanks for the feedback!

This sounds a bit like hamster simulator, which we used in high school in our “programming” class, the site is in German, but you might the idea. But I can absolutely see how you can make this more compelling.

Deutsch wäre jetzt kein Problem für mich und ich glaube, ich erinnere mich sogar daran, das auch mal im IT Unterricht gehabt zu haben. Leider war die Lehrerin damals 'ne Katastrophe und ich hab’ das meiste von damals wohl schon ausgeblendet 😅

Building something in-game and extending the world with coding is an interesting perspective. I haven’t thought about it this way before. Instead, I always thought about solving programming tasks and, therefore, solving some issue in-game. I’d have to think about this more and see if I could incorporate that idea. Thanks for the suggestion!

Hmm… so thats why they say, Apple is a religion 🤔

Despite the name, audiobookshelf recently also added e-book support. It is still in development but (at least for me) is at a point where I’ve abandoned kavita and am now using it for both my audio, and e-books.

I can’t wait to learn more about the GPU. I really hope it’ll be able to run CUDA.

Hopefully, they fix their camera API so that GCam works properly this time. Being stuck with the stock photo app was the only downside of version 4 imo.

I second this but would recommend n8n instead, since you can self-host it and you’re not dependent on another online service.

There are a many approaches to implementing OOP in C. Since C doesn’t give you any language constructs to implement this out of the box, it’s up to you to do it in a consistent and understandable manner. Since there is no definite way to do it, let me just give you an example of how I would translate a Python file, and you can decide how you implement it from there:

--------------
class Parent:
    def __init__(self, param1: str, param2: int):
        self.__param1 = param1
        self.__param2 = param2
    def __private_method(self):
        print("private method")
    def public_method(self):
        print("public method")
    @staticmethod
    def static_method():
        print("static method")
    @property
    def param1(self):
        return self.__param1

class Child(Parent):
    def __init__(self):
        super().__init__("param1", 2)
--------------

I would split the C code for this into header and source files:

(header.h)

--------------
#pragma once

/// Parent Class ///
typedef struct Parent_obj {
    char* param1
    unsigned int param1_len
    int param2
} Parent_obj_t;
void Parent_init(Parent_obj_t* self, char* param1, unsigned int param1_len, int param2);
void Parent_public_method(Parent_obj_t* self);
void Parent_static_method();
void Parent_param1(Parent_obj_t* self, char* out, unsigned int max_len); // property method with upper bound string length
void Parent_del(Parent_obj_t* self); // destruct object (similar to __del__() in python)

/// Child Class ///
typedef struct Child_obj {
    Parent_hidden_state_t* super
    char* param
    unsigned int param_len
} Child_obj_t
void Child_init(Child_obj_t* self, Parent_obj_t* super);
void Child_del(Child_obj_t* self);
--------------

(source.c)

--------------
#include "header.h"

/// Parent Class ///
// private methods
void Parent_private_method(Parent_obj_t* self){...} // not visible in the header file
// public methods
void Parent_init(Parent_obj_t* self, char* param1, unsigned int param1_len, int param2){...}
void Parent_public_method(Parent_obj_t* self){...}
void Parent_static_method(){...}
void Parent_param1(Parent_obj_t* self, char* out, unsigned int max_len){...}
void Parent_del(Parent_obj_t* self){...}

/// Child Class ///
// public methods
void Child_init(Child_obj_t* self, Parent_obj_t* super){...}
void Child_del(Child_obj_t* self){...}
--------------

Modules and namespaces can be modeled using folders and prefixing your structs and functions.

There are a few approaches to implementing OOP in C. The language doesn’t give you any constructs to implement this out of the box, so it’s up to the developer to do it. Since there is no definite way to do it, let me just give you some examples and you can decide how to use it in your project:

class Parent:
    def __init__(self):
        self.__hidden_state = "properties"
    def __private_method(self):
        print("private method")
    def public_method(self):
        print("public method")
    @staticmethod
    def static_method():
        print("static method")

class Child(Parent):
    def __init__(self):
        super().__init__()
        self.__hidden_state = "child properties"

I would split the C code for this into header and source files:

(header.h)

I mean… true… but also: having fully autonomous commercially available drones flying around the city is unrealistic anyway, so I’m just committing to the bit at this point.

If the drone could fly around the city autonomously, I would use it to digitize my city and get a personal Google Street View on steroids. I already use drone shots for structure-from-motion projects, but it would’ve to be autonomous for such a large-scale operation