I wrote an article speaking about PNPM, a possible alternative to both Yarn and NPM. You can read it on Pixelmatters blog.
In the previous post we talked about what emulators and virtual machines are, when they appeared, what is their current status and use.
What I want in this set of articles is to explain in a simple and summarized way how a computer works and the best way to do it is to create one, I don't mean physically, but rather an emulator. I will explain and write some code throughout the article. To implement the emulator I'll use Rust and the architecture we are going to use is from LC-3, since implementing an emulator for x86 is extremely laborious, even for an old system.
The word emulation appeared very close to the computer itself, since early engineers tried to run programs from other systems on their computers. As there were multiple platforms and architectures, everything was very incompatible, given the difference. Unfortunately, at the time, as the hardware was very slow and limited in its capacity, emulation was either impossible or very limited.
Apple releases a major version of their OS for Macs each year, but Big Sur was one of the more significant releases in the last decade. Big changes always break things, and this was no exception.
When we speak about significant CSS codebase, we automatically think of SASS or any other CSS pre-processor like stylus or LESS, to name a few. Using this type of tool is useful not only to share styles across multiple components, nesting, variables but also to allow functions and mixins for more complex logic.
This is a new version of an old article of mine on Medium. This version no longer uses XBuild since cargo nightly is receiving build-std that does the same job.
After two tweets that I made last week, playing around with UEFI and Rust, some people asked to publish a blog post explaining how to create a UEFI application fully written in Rust and demonstrate all the testing environment.
So todays objective it’s to create a UEFI application in Rust that prints out the memory map filtered by usable memory (described as conventional memory by the UEFI specification). But before putting the hands at work let’s review some concepts first.
Copyright © gil0mendes 2019-2022