Sorry, your browser cannot access this site
This page requires browser support (enable) JavaScript
Learn more >

I’ve been using my current avatar for over ten years. Ever since I started working in bioinformatics, I’ve wanted to add more complexity to it—half with circuit‑board patterns, the other half with DNA patterns, connected by a smooth transition in the middle to symbolize the transformation from biology to information, which fits my professional field. However, I’m not very skilled at photo editing, so I couldn’t achieve the desired effect. This year, the newly released image‑editing models gave me hope to realize my idea.

I just wanted to set up a devcontainer environment to maintain the company website more efficiently, but I never expected to encounter three pitfalls in a single task…

I’ve developed a habit of listening to videos during my bike ride home after work. This week, I came across a video by XPIN about RISC-V. The video presents a viewpoint: RISC-V, as an instruction set architecture, suffers from severe fragmentation in its chip products, which poses significant challenges to the development of its application ecosystem. Therefore, it’s argued that fragmentation must be addressed through unified standards to achieve rapid development. This perspective reminded me of my years of experience using Linux, Android, and the R language, leading me to believe that the video’s argument might not be entirely accurate.

Recently, I attempted to use pixi to compile and run podman on FydeOS. While I made some progress, it ultimately only achieved half success. In this blog post, I’ll share the entire process and the issues encountered.

Last year, I actually used Fydetab Duo to compress videos from my travels. At that time, I found a pre-built library on GitHub, but now I can’t find that repository anymore… So this time, I tried to compile it myself…

When people are speechless, they really do laugh - my direct supervisor has resigned again and again and again. Why so many “agains”? Let me draw a timeline to see how many bosses I’ve “jinxed”.

Compared to two years ago at my previous company, I now use AI much more frequently. If the limitation back then was the convenience of the tools themselves, the current limitation seems to be my own knowledge and technical skills rather than AI.

After changing the motherboard and CPU, everything went smoothly… I’m not sure whether it was the motherboard or CPU that was causing the issue before - compilation would fail after tens of minutes, and subsequent attempts would fail at different points. This was actually the first time in my life I encountered real hardware incompatibility issues… Another “first time in my life” experience.

So here comes the second part of compiling openfyde. Unfortunately, during the time I was struggling with the faulty hardware, the prebuilt image for r132-dev version was already updated… Missed the hot topic…

Since my first encounter with ChromeOS/FydeOS, I’ve been trying various VSCode-like editors. Recently, after learning about Huawei’s CodeArt and its upstream project Theia, I started tinkering again.
Unfortunately, my current device is an 8GB FydeOS, not the 16GB Manjaro or PixelBook 2017 I used before. The available memory in the Linux container is very limited - I can’t even compile an ARM version of Theia-IDE browser edition… So… I had to “borrow” GitHub’s resources again.

At the beginning of this year, I tried to compile openfyde, hoping to learn about compiling and modifying the openfyde system, and also to make use of my extra engineering machine. However, half a year has passed… and the issues from the last compilation still haven’t been resolved…