This is my response to the call for blog posts on what Rust development focus ought to be during 2020. Much unlike my extremely late post for 2019, which focused entirely on compiler implementation details, the focus is on things that affect the end user experience, specifically the experience past the initial rose-coloured glasses phase of adoption.
As a part of the OS project for the university there has been a request to also write up the experiences and challenges encountered. This is the first post of the series on writing a x64 operating system when booting straight from UEFI. Please keep in mind that these posts are written by a not-even-hobbyist and content in these posts should be taken with a grain of salt.
For the ongoing project to make myself a custom mechanical keyboard, with an intention to get more familiar with embedded programming and soldering, I bought some blue pills (STM32F103C8T6 based microcontroller boards). At under €1.50 each, these extremely popular microcontrollers, seemed like a great enough deal to get 5 of them at once.
In Rust ecosystem it is fairly popular for a FFI binding library declare the “native” libraries it links to in a build.rs script. If the binding is intended for a cross-platform use, chances are that the build.rs script is written incorrectly.
A comment section is an expected feature of a modern web site and it is hard to find a page which does not contain a form to post a comment. I, however, will not include a commenting form into my blog and my reasoning, in a defensive fashion, as well as solutions are stated in this entry.
It is widely accepted to label energy produced from sources such as sunlight, wind, geothermal heat or even biomass as renewable energy. As soon as one looks at the bigger picture, it is inevitable for one to start noticing lack of renewability of all aforementioned sources.