Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.
Maybe we should one day include Golang or Rust to it
2,192 karma · joined July 1, 2017
Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.
Maybe we should one day include Golang or Rust to it
I would still define first-order Futamura projection as the original definition that you have direct encoding and code-to-code expansion and transformation between so.
Insane amount of bureaucracy, paperworks, and how we are missing deadlines so we write shit code that the quick and dirty solutions were never replaced.
Algorithms and data structures therefore are more like helping you utilize the machine economy better, but it doesn't have any meaningful impact on the social aspect of it. That's a hard lesson I had to learn from my two previous job, though now I'm considering starting my own small business just to make a little bit of living enough to survive.
But now my ADHD kicked in and is still lazy and I had so many concerns whether the market validation is great, how to deal with situations if I broke customers stuff, how to gain (and hopefully not regain) trust if any bad things ever happen, what if I want to go vacation and suddenly the server broke and got code zero (the highest level of alert I termed internally, when you had alertmanager flashing everything red, network storage is down, corruption happened) during a trip to Bahamas.
I'm still in the watershed of thinking really to do this or not, but the job market is filled with ghost jobs that are not worth my time either, I'm basically "dead locked" right now and had to make a decision quick.
Either choice is fucked for me, as I started to notice after going to work, despite I got some really interesting ideas in tech, but I'm not a charismatic person so I can't really make those idea to fruition, because no one wants to listen to me and implement it together, so I'm pretty sure it is impossible for me to be a great leader (tech lead probably, but CEO level of leadership and coordinator and manipulate the grand scheme of thing, nah, I pretty much can't do).
Now the problem is, even if I'm pretty sure to get fucked, you should choose the one that inflicts minimum pain to you. So far having my own business seems like a less painful to die and bankrupt, and I'm preparing to sell off some of my stuff to get a last dip of my fortunes and have fun. Will see how it looks. Bankruptcy is nothingburger in this modern society perhaps.
Now you see how the bottlenecks can't even be the code anymore and even goes beyond code, despite having the same core template: I don't even have to code, to repeat the same "quick and dirty" kind of mindset in another domain, in another instance. That's something LLM, heck not even AGI can solve: decision-making based on situations with limited time and resources, and it can be personal or organizational or even structural.
This is very much not going to be solvable by a bunch of lines and statements and expressions, but it really need some time to dig in and compromise. Pick your kool-aid and drink it
But the biggest problem is, even human itself is subjectable to hallucination. That is called being delusional, or being drugged. So it is inevitable from the first principle.
To me it seems more like leveraged buyouts + debt restructuring all at once. I rather coin this term "debt offloading", which could also cover the cases with Enron for the tactics they used about 25 years ago
By using a long distance communication device this eliminates the proximity strike problem. This could easily be extended to say like distributing the voting rights to different generals at different regions, and given that the device is genuine and not modified, can be a hardware voting key to say like launch the nuke in secrecy or not.
Whether adversarials can use the radio signals that it emits to triangulate you and thus track you is another story, though.
It is not like I don't know that Golang's interface could do that. It's just C# simply did better. I do enjoy using Golang for writing network application such as network protocols and IO intensive workload, which is where Golang really shine through Goroutines, but if you want a generalist that is famiilar and did all-rounds, I would still consider C#/Java/Kotlin for that purpose.
I hope there are jobs for company liquidators though it is usually the job of a junior solicitor/lawyer I reckon, as they will certainly have more demands amid this bankruptcy wave
I have to came all the way to attach it to a Future, that because Rust doesn't have any default argument, I mean I have to supply cancellation token from the top to bottom.
But in hindsight, Golang's context actually do mimick cancellation token in some sort, but in a way that the cancellation is cascaded and recursive by using done in canceler or deadline which means it is timing and latency sensitive.
If you truly want cancellation token style, you need to use semaphores or by explicitly polling the cancellation channel (which is what you can do with context) which can hurt if you don't have enough thread slack.
But still, internally we call it i586, because that's the way it is. so is Pentium MMX which I reckon is called i686.
Increasing the extreme and cruelty of violence. It always works. That also means the "investment" of each action will have higher stake, though.
It is not an intimidating thought experiment, it is being used in the 2026 Iranian Protest by the IRGC
The simplest binary saturating counter, ala bimodal predictor, already achieved more than 90% success rate. What comes next is just extension around that, just use multiple bimodal predictors and build a forest of it, but the core idea that treating the branch prediction using a Bayesian approach, never fades.
It is a combined effort between hardware design and software compiler, though.
What I could just do is obfuscate it a little bit and you can't tell whether it is AI-generated or not. If I just read that AI-generated snippet, and wrote a "human" version of it, would that still count as "AI-generated"
The idea of that rule is that we don't want HN to be Moltbook, not that it actually wanted to ban AI-comments.
## Opposing the Ban on AI-Generated/Edited Comments on HN
*The value of a comment should be judged by its content, not its origin.*
Here are key arguments against this policy:
- *Ideas matter more than authorship.* If a comment is insightful, well-reasoned, and contributes meaningfully to a discussion, dismissing it solely because AI assisted in its creation is a genetic fallacy — judging an argument by its source rather than its merit.
- *We already accept tool-assisted thinking.* People routinely use calculators, search engines, spell-checkers, and reference materials before posting. AI assistance exists on a spectrum with these tools. Drawing a bright line specifically at "AI-edited" is arbitrary when someone could use a thesaurus, Grammarly, or have a friend proofread their comment without objection.
- *It disadvantages non-native speakers.* Many HN users are brilliant engineers and thinkers who don't write fluently in English. AI editing can level the playing field, allowing their ideas to be judged on substance rather than prose quality. This policy inadvertently privileges native English speakers.
- *It's effectively unenforceable.* There is no reliable way to distinguish a lightly AI-polished comment from a naturally well-written one. Unenforceable rules erode respect for the rules that are enforceable and important.
- *The real problem is low-effort content, not the tool used.* What HN actually wants to prevent is shallow, generic, or spammy comments. A policy targeting quality directly (which HN already has) addresses the actual concern better than a blanket tool prohibition.
- *Human intent still drives the conversation.* A person who uses AI to articulate their own idea more clearly is still participating in a human conversation — they're just communicating more effectively. The thought, the intent to engage, and the underlying perspective remain human.
*In short:* This rule conflates the medium with the message and risks excluding valuable contributions in pursuit of an authenticity standard that is both philosophically fuzzy and practically unenforceable.