🌟 Go 1.26.1 and 1.25.8 are released!
🔐 Security: Includes security fixes for the standard library (CVE-2026-25679, CVE-2026-27137, CVE-2026-27138, CVE-2026-27139, CVE-2026-27142).
🗣 Announcement: https://t.co/WxJDiFl34E
⬇️ Download: https://t.co/7L1Iy3zfZF
#golang
one of the trickiest C++ bugs I’ve experienced involved the *physical* location of data in memory.
writing some tricky string decryption code, it worked...sometimes
recompilation slightly shifted the layout of the stack, which by pure luck contained a “safe” number
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
A very direct response from Lip Bu Tan last night. Biggest thing here to me is that he has board support right now. He reinforces that the US has been his home for 40 years and that he loves his country (good way to start), rejects the misinformation, and a reminder that Intel is working on the most advanced node of any U.S. based company.
We’re 24 hours in and this is just the start. The administration and Intel need to figure this out. From the foundry standpoint, the country needs this. For national security and competition.
Link 👇🏻