Qualcomm talked a lot about Snapdragon X Elite as the future of Windows and Linux on ARM, but results so far are mixed. Windows on ARM is finally usable on recent laptops, yet compatibility gaps remain, and Linux support is still far from mature.
The high idle power on the Framework ARM upgrade board shouldn’t be blamed solely on MetaComputing or CIX. Poor idle power efficiency is a long-standing issue on Linux laptops, especially with new platforms, so this looks more like an ecosystem-level power-management problem than a single-vendor failure.
What stands out to me is that Chinese companies are actually shipping hardware and pushing into every possible market segment. Their decentralized, diversified corporate ecosystem seems to enable fast experimentation and broad market penetration.
While it makes sense that LLMs and machine translation systems primarily rely on English Wikipedia as a data source, depending on smaller-language Wikipedias for training is far less ideal. English Wikipedia is generally well-regulated by its community, but many other language editions are not — so treating all of Wikipedia as an authoritative source is misguided.
For instance, my mother tongue’s Wikipedia (Korean Wikipedia) suffers from serious governance issues. The community often rejects outside contributors, and many experienced editors have already moved to alternative platforms. As a result, I sometimes get mixed, low-quality responses in my native language when using LLMs.
Ultimately, we need high-quality open data. Yet most Korean-language content is locked behind walled gardens run by chaebols like Naver and Kakao — and now they’re lobbying the government to fund their own “sovereign AI” projects. It’s a lose-lose situation.
Whether you use Bazel or not, this is a well-known issue with an equally well-known solution. There’s no need for such a lengthy write-up: just use a consistent sysroot across your entire build environment.
If you can’t create your own sysroot image, you can simply download Chromium’s prebuilt one and configure your C++ compile rules correctly. Problem solved.
It seems I’m not the only one who feels that Google’s ad tracking has improved a lot — to the point where it makes me a bit nervous. A few days ago, I searched for a medicine just once using Firefox’s private mode, and now both Google search ads and YouTube ads are filled with related topics. Maybe I need to reset all my Google ad tracking IDs and stop using Google for anything sensitive.
If I remember correctly, the issue was related to newer APIs like MediaStreamTrackProcessor, offscreen surfaces, and WebRTC–WebCodecs interoperability, as well as the ability to run ML inference efficiently in the browser. At the time, Firefox hadn’t fully implemented some of these features, which impacted Google Meet’s ability to apply effects like background blur or leverage hardware-accelerated video processing.
I know many people are dissatisfied with existing C++ build systems like CMake, and I understand why. However, before creating a new build system, one must first understand C++’s current position. These days, C++ is chosen less frequently due to the wide range of alternatives available. Still, C++ shines when it comes to bridging distinct components. While it’s tempting to optimize for the simplest use cases and make things as concise as possible, real-world C++ build systems often need to handle a wide variety of tasks—many of which are not even C++-specific. That’s where CMake proves its value: it can do almost anything. If a new build system can’t handle those cases, it’s likely to be dead on arrival.
Framework’s current policy in Asia—limiting deliveries solely to Taiwan—warrants reconsideration. Due to these restrictions, I had no choice but to purchase Apple products instead. To prevent further customer dissatisfaction, Framework should re-evaluate its shipping policies.
I understand that Framework’s logistics cannot match those of major retailers like Amazon or AliExpress. However, many customers rely on freight forwarders to access products from other countries. It is deeply disappointing that Framework does not allow shipments to these intermediaries, as they are a common and well-established workaround for limited international shipping. Given the widespread use of such services, excluding them seems unjustified.
I’ve never used FFmpeg-kit—I always use FFmpeg from distro packages (Linux, Homebrew) or build it selectively—so I’m not sure how important it is. Is it just a thin wrapper around the FFmpeg C API for various platforms?
If that’s the case, software engineers relying on it should learn how to build FFmpeg from source and handle platform-specific challenges (especially on Android). The loss of the overall community support doesn’t seem that significant, right?
That said, whether someone uses FFmpeg-kit or builds FFmpeg manually, the legal risks remain the same. If they don’t understand codec patents (like x264 and MPEG-LA) or GPL/LGPL obligations, they could face lawsuits or be forced to release their code under GPL. The real issue isn’t FFmpeg-kit—it’s whether developers actually understand these legal implications.
Or set the compiler flag -fno-exceptions and ban the use of exceptions. While it isn’t standard-compliant, a surprisingly large number of companies and projects follow these practices.
Maybe the experience varies depending on where the user is located. Users near Mastodon servers (possibly on the US East or West Coast) may not feel the slowness as much as users in other parts of the world. I notice noticeably slower response times when I use Mastodon in my location (Korea).
This is why I don't use Windows and refuse any SWE jobs that require Windows machines. Additionally, I believe kernel-level game anti-cheat software should be banned.
Hmm... Is China betting on RISC-V chips? China is too big to rely solely on a single chip architecture. I saw another attempt to develop a new chip architecture in China, called Loongson64.
In recent years, I've seen a lot of contributions to libraries/software, such as the Linux Kernel, Chromium, LLVM, V8, and ffmpeg, by Loongson, a Chinese chip company that produces an architecture called Loongson64.
Apparently, China wants to develop its own chip architecture, chip design, and chip manufacturing capabilities, and RISC-V is one of the options, but there isn't a single path to achieving that.
It is interesting to see how CPAP is used and covered by insurance in different countries. In my country, South Korea, CPAP is available for rent if you have certain medical conditions, and the rental price is fixed. I pay 15 USD (20K KRW), and the Korea NHS pays 60 USD (80K KRW) per month. I've been using Löwenstein's CPAP, and it works great without any problems.
It is interesting that many folks are comparing macOS native apps and Electron apps. As someone who uses macOS for work and Linux for everything else (FOSS, games), I'm thankful for Linux apps using Electron, CEF (Chromium Embedded Framework), and Flutters, otherwise, developers/companies might opt out of supporting Linux. While in many cases writing native apps using one's favorite compiled language such as C++, Swift, and Rust is preferred, many apps prioritize feature parity over perfection, making cross-platform usage perfectly acceptable.
If you're working in a controlled environment, such as proprietary software with a fixed number of toolchains or a few OSS projects like Chromium that use their own fixed toolchain, then it makes sense to turn on -Werror. However, most OSS projects deal with tons of different compilers, so it is not possible to enforce -Werror, as different compilers and versions handle warnings differently.
Problems of Rust:
In Rust, there is a central package registry (crates.io), but there is a lack of ability to add dependencies using git URLs.
Problems of Swift:
Swift can add dependencies using git URLs, but there is no central package registry.
Both languages should have a central package registry and the ability to add dependencies using git URLs, as it would make flexible dependency management much easier. For a central package registry, it makes it easier to find popular packages, but it has a problem of centralization.
I believe that's a historical (19th-century) reason. Japan tried to live up to Western standards. They underwent radical changes and adopted Western culture, driven by the significant influence of the '脱亜入欧' (Leave Asia, Join the West) theory during the Meiji era. That's why they adopted a Western-style naming convention for English names (Personal name + Family name).
However, China and Korea didn't modernize as fast as Japan. They didn't have radical changes in the 19th century. (The result is that foreign concession in China, unequal treaties, colonization of Korea, etc.) So they didn't have to change their naming convention.
The reason why Japan is trying to change the English naming convention when they write in Japanese is similar to the reason mentioned above. The 21st century is Asia's century. Japan feels that they don't have to conform to Western standards anymore. They are trying to be more Asian. That's why they are attempting to change the convention to synchronize as if they were writing in Japanese.
I am a user of Samsung Galaxy and Apple MacBook Pro M1 Max. Both models offer Battery Limit/Battery Protect features to protect the lithium-ion battery. I first realized that other iPhones, except for the iPhone 15, don't have such a feature. Maybe it's a good idea to include it?
I think the problem is in setenv(3), not getenv(3). Reading shared global state is okay as long as it is not mutable. If someone relies on modifying environment variables, one should use execve(3), not setenv.
If Apple hadn't created Metal, the world would have been better off. Thank you, Meta, for your hard work.
Also, there are those who argue that starting new projects in C++ in 2023 is almost always wrong. How about checking out the new C++ library? Do you think your preferred language X would be better than C++ in this situation?
The larger the monitor, generally the better. However, considering GPU performance and power consumption, compromises must be made somewhere. I have a $500 Dell 4K 32-inch monitor, which is the maximum I can accommodate in terms of desk space. (The desk space is greatly influenced by real estate prices, currently estimated at $12,000 per square meter based on my home.)
Yet another library feature that will be used by nobody... While having a standard library is good, system programming presents tricky aspects like async-safety that are not adequately addressed. Therefore, considering the challenges involved, I believe it would be better to utilize existing libraries like crashpad to handle such scenarios.
Upvotes/downvotes are not good for democracy. Especially if the upvote/downvote history stays in your account. Think of the yes and no stickers in the Soviet Union and other totalitarian countries on the front of their government buildings. Even, moderators can pin their thoughts. It is not easy to express a different kind of opinion in the first place.