Is there anything like a “Windows From Scratch”?
like taking a full Windows installation and copying binaries and components to new machine one by one, mainly to understand how Windows is structured internally?
is it reasonable to have a keyword for tail-recusive return? basically it means I'm writing a tail recursive function and give me compile error if it occurs at non-tai-recursive positions
there's a hidden feature I don't like at all. if you double click on the "white area" just inside the border, it goes into a " maximized" state where title bar and menus will disappear.
it's so easy to enter this mode by mistake and no obvious way to get back
it's not true. Han Chinese are clearly genetically distinguishable from Yamato Japanese and Koreans, and internally the different Han Chinese subgroups are genetically closer to each other than any of them are to Koreans and Japanese.
We should not make fun of log4j2 developers for the work they're not paid for, they made it in their spare time. it's a shame so many companys are using log4j2 but few(if not none) sponsor them.
https://github.com/sponsors/rgoers
I was trying to write some function similar to `make` but in vein. Maybe I need to open the compiler like the author did. make() takes a type as argument but you can't define such functions in go. And `make` itself is not a keyword, how does golang implement it? is it a special case?
joke aside. we know a language is Turing-incomplete if it has only ifs and bounded for loops. And if 90% programmers' tasks can be done using a Turing-incomplete language, is there any benifits we can get from this?