1,252 karma · joined January 21, 2016
test emph
verbatim
https://www.gnu.org/> In countries like China (83%), Indonesia (80%), and Thailand (77%), strong majorities see AI products and services as more beneficial than harmful. In contrast, optimism remains far lower in places like Canada (40%), the United States (39%), and the Netherlands (36%).
In a separate research at https://www.bloomberg.com/news/articles/2025-06-20/trust-in-... , people found that low income countries have higher trust in AI.
There are better choices if everything is built from scratch, but changing wheels from a running car isn't easy.
I would never expect our 10M+ LOC performance-sensive C++ code base to be formally memory safe, but so far only C++ allowed us to maintain it for 15 years with partial refactor and minimal upgrade pain.
I get this proposal's rationale, but it seems that it would implicitly make fd leaks more prone in python programs
There're hundreds of thousands of '3D worker' working behind the scene to create the 3D models for makeshift ads, and as far as I know many of them (including my high school mate) already got displaced by Midjourney and lost their job. This used to be a big industry but now almost entirely wiped out by AI.
- Shift: Self-Healing Independent File Transfer
- BASSHFS: Bash-Accessible SSH File System: SSHFS but without fuse dependency
- Ballast: Balancing Load Across Systems: load balance for SSH servers
An example: https://github.com/llvm/llvm-project/blob/main/clang/test/Se...
More details can be found at https://herbsutter.com/2018/09/20/lifetime-profile-v1-0-post...
Unfortunately it was never upstreamed according to https://github.com/mgehre/llvm-project/issues/98
1. FFI boundary will likely to exist forever in a milions-of-line C++ codebase, especially when the behavior of this system is not possible to be formally specified / tested (e.g., depending on an unknown external system, or some behaviors specified in hundreds of pages "specs" full of jargons)
2. In the above case, when C++ code dominates the FFI cost would be signified as you need to call C++ routines frequently to achieve stuffs. For example, when every struct has some methods returning std::string the std::string needs to be targeted.
In our case, the primary motivation of Rust isn't its safety - we just use it for syntax sugars and ease of extensions (with proc macros).
https://en.m.wikipedia.org/wiki/File:Sun_Oracle_type-7_keybo...
This is only true in new tech where data relationship isn't complicated. Any stored procedure in bank would contain joins with no fewer than that number of tables.
git-fuzzy seems to also support two-column diff view which isn't in tig. Good job.