From http://www.nyx.net/~gthompso/quine.htm
总结的很全,各种语言都有,至少我听说的语言都提及了
摘录一些有趣的:
C的,很早就知道了,今天想起来帖出来
char*f="char*f=%c%s%c;main(){printf(f,34,f,34,10);}%c";main(){printf(f,34,f,34,10);}
可以把char*去了,只报warning
对这段代码,要么看不懂,要么会为其精妙的构思叫绝
很佩服作者
C++的,有点麻烦,但换汤不换药
Author: lapinski@utexas.edu
#include
main(){char*s="#include%cmain(){char*s=%c%s%c;cout.form(s,10,34,s,34,10);}%c";cout.form(s,10,34,s,34,10);}
Javascript的,有投机取巧的感觉
Author: Geoffrey A. Swift(blimey@toke.com)
function a() {
document.write(a, "a()");
}
a()
My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Comments