Hello and sorry for the delay. I haven’t posted any new articles for more than a week because I ran into system issues.
In my most recent post I mentioned moving the blog to the new Deno Deploy, since Deploy Classic is being retired. The blog was still running on Deploy Classic, and they have blocked new deployments on Classic, so I had to switch to the new platform if I wanted to keep deploying. The migration took two to three days; I thought everything would go smoothly, but the new system uses a different way of counting limits. In less than two days the blog hit its limit and was at risk of being suspended (no longer accessible). So I had to point the domain back to the old version, making it read‑only so people can still view it, though I can’t add new content.
I have long realized the risk of relying on server‑side rendering (SSR). An SSR site needs a server, and a server isn’t free. In contrast, a purely static site—where the HTML files are generated at build time and no server is needed for data processing—can be hosted almost anywhere, often with unlimited bandwidth. What would happen if I rebuilt the blog that way?
Indeed, I purchased the OpenCode Go package and spent a week, together with Kimi 2.6, rebuilding the site from scratch using 11ty and preactjs, plus the phiresky/sql.js-httpvfs library. The result, as you can see, is the current blog. It’s faster, lighter, and no longer heavily dependent on a server (though a server is still needed for a few features). I’ll write a detailed post about it as soon as possible. Thank you!
Vẫn còn một số lỗi do thiếu sót, nếu bạn phát hiện ra có thể liên hệ với mình qua telegram: https://t.me/hoaitx để mình sửa 😅, cảm ơn rất nhiều.
OpenCode Go
Finally, I successfully moved to the new Deno Deploy, though it took me a few days to figure out how to do it 🫣
@@@@@@@@@@@@@@
Thread bình luận
Cawbg thang
@@@@@@@@@@
trong một threads
I’m really stressed—Deno Deploy is about to retire the Classic platform, so they’re no longer letting us push new versions. I haven’t been able to deploy anything for the past two‑three days, and the KV store is running out of resources, which means the Threads section will soon go dark.
Looks like we’ll have to switch to their new Deploy system soon 🥶.
Wow, everyone, come see the scores for the upcoming Qwen 3.6 Max Preview—it totally crushes Opus 4.5. If those versions keep whining like this, they should just be shut down, not released 😤.
I’m checking if there’s any noteworthy news today, and I ran into the Vercel April 2026 security incident - Vercel confirmed they were breached. There’s also a report that a hacker is trying to sell the entire source code and data for $2 million 🥶
I’m pretty scared; they just recently bragged about their “vibe coding” … I hope it’s just a coincidence.
You’ve probably heard a lot lately about Mythos being able to uncover numerous security flaws in software—and even operating systems, right? After the "vibe coding" phase, the next step is for large language models to dig deeper into finding potential bugs in open‑source tools. It’s a double‑edged sword: on one hand, it can quickly spot vulnerabilities and help fix them; on the other hand, it can just as easily discover those flaws and exploit them 🥶.
Cloudflare has just released a tool that checks how AI‑friendly your website is. As you probably know, nowadays we let agents do the searching instead of using traditional engines like Google. So if you want AI agents to be able to retrieve your site's content effectively, make your site easier for them to understand.
But it’s a strange thought—if an agent reads all of our web content, who is actually helping whom? 🤔
Looking back, I see that Opus 4.7 is out. Its score has reached a new high, and the price is still the same as the previous version.
Netizens claim Anthopic is deliberately pushing Opus 4.6 down to launch a few flagship products 🤔. But they lowered the price of 4.6 so we still have something to use 😅.
"Vibe Coding" Is Dead? The article’s headline may seem provocative, but it’s actually spot‑on, because Andrej Karpathy—the creator of the term "vibe coding" - has said we should now use the phrase “agentic engineering" instead.
"Today, programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. Personally, my current favorite term: 'agentic engineering.'".
Earlier I thought a JavaScript Promise could be cancelled with an AbortController, but I later realized that AbortController’s scope is rather limited, so cancelling a Promise isn’t feasible. Recently I read the article You can't cancel a JavaScript promise (except sometimes you can) that discusses the issue in more detail. It turns out a cancel‑Promise proposal already exists, but it’s so complex that it hasn’t become part of the specification.