I started out when I got a new phone, and didn't know what to do with the old one. One of the ideas I had was a homeserver. Turns out it's not trivial to run Docker even on rooted Android phones, and you need a lot of kernel patching, tweaking and more and it still had issues after that.
The next step was when I figured out I could install postmarketOS on it, and I managed to flash it, SSH into it and set up Nextcloud for our photos and unbound as a recursive DNS for my home network. I thoroughly recommend postmarketOS, and the contributors are amazing as well.
I was however running out of storage, so I ordered an 256GB SD card, and set up mergerFS between it and local storage, worked fine.
After some time however, I got paranoid about having and old device with a LiPo battery constantly being charged in my home, so I decided to get a mini PC from Aliexpress and chucked a 2TB SSD in.
In the meantime, I discovered Immich, which turned out to be much better for photos than Nextcloud, and fell in love with it.
The final thing I added was a miniDLNA service to play my local movies and shows on my LG TV without having to bother with Plex/Jellyfin and reencode anything. Unfortunately, it kept disappearing after roughly 2 days of operation, so I just added a cron job to restart it at 5 AM.
For the time being, I don't need anything more and am turning my attention to other things.
The quote saying that people from 18 to 25 need a safe environment to "explore the world" and "find their purpose" seems very infantile and backward.
First off, it's not realistic at scale and presents a very sheltered worldview. Majority of worlds workforce is between those ages and no automation, nor AI will change this.
Second, even in the first world it's backward because you can also explore the world and find your purpose while working, infact working will teach you much more about the world than any college and you can always decide to get education when you're more mature and better off financially.
It really depends on what you classify under embedded. Everything more expensive than a Padauk or newer than PIC will have hardware support for the stack, and also most likely have the heap provided by newlib.
Bipartite buffers are amazing and criminally underused. For those looking for C and C++ implementations you can check out my libraries: lfbb and lockfee: https://github.com/DNedic/lfbb, https://github.com/DNedic/lockfree (although lockfree contains more data structures as well)
I am not sure how colleges work, but even at reputable universities this happens. Professors who have big fail rates will often be reprimanded for this, regardless of whether it's their fault or not.
Yes, sometimes this genuinely indicates a problem with the professor in question, but often times this leads to a long chain of responsibility passing, where if say a Calculus professor was afraid to have big failure rates, the Fluid Mechanics professor will be in a tough spot where they can either push back and have high failure rates or be more lenient, after that the Aerodynamics professor will inherit the same issue and so on.
>We've had things like reservoir lakes for hydro plants for a long time. Energy can be stored in more ways than electrical.
Hydro is great. Gravity batteries (e.g. pumped storage) are great. The problem is that they require particular geography to work - especially at grid-scale, and we pretty much exploited all of it already - so you cannot scale it.
If you're interested about practical uses of atomic operations, I wrote lockfree: https://github.com/DNedic/lockfree, a collection of lock-free data structures meant to be readable and both hosted system and embedded friendly.
GNSS satellites talk to base stations on earth to get correction data using the measurements they obtain (including measurements obtained by tracking satellites from the ground). I believe this is what the poster above is reffering to.
RTK is a whole another beast and the meaning of an RTK base station is something else.
Undefined behavior will bite you eventually. Updated the compiler? You have no idea what to expect. Changed lines of code related to that part of code? Again, no idea what to expect.
While I agree that undefined behavior should be avoided, it’s not as rigid as you put it. Just because something is undefined behavior by specification (or lack thereof) doesn’t mean it’s undefined behavior in practice. As a general rule though, I do agree with you.
Casting pointers to the correct integer types and again back isn't UB, but several things you can you can easily do along the way are at the very least implementation specific.
