Programming Circlejerk

URL: https://www.linkedin.com/posts/andrei-saioc_people-advocating-against-usage-of-ai-in-activity-7347263117183057920-3w9h

url: https://lobste.rs/c/tp8tfa

url: https://github.com/realchonk/bsget

source: https://go.dev/blog/error-syntax

source: https://www.linkedin.com/posts/yurii-kolochkov_if-you-proudly-list-solid-principles-on-activity-7335938477265498112-LgIn

source: https://www.linkedin.com/posts/zachlloyd_anyone-else-having-a-hard-time-getting-their-activity-7333511252666662913-RK7g

url: https://www.linkedin.com/posts/anshupatelz_linux-servers-devops-activity-7331631681147232256-vHKf?

URL: https://notashelf.dev/posts/curse-of-knowing

URL: https://hachyderm.io/@alberto/114438133196397394

editorialised text to make it easier to understand

Every programming problem I have, when I track it down to it's source, seems to originate with C/C++. It wasn't till a few years ago that I realized how seriously everything I do somehow, some way, has C/C++ as a foundation. Basically every zero-day exploit in my cyber security class is because of something stupid in C/C++. And it goes well beyond security, the more I dive into C++ the more terrible stuff I find. When I found out even Rust needed the clib, it was like seeing an iron-clad fortress only to look closer and see it was being held up by sticks, ducktape, and prayers.

https://lobste.rs/s/pncgon/what_i_d_do_as_college_freshman_2025#c_rauruz

https://www.linkedin.com/posts/anmol-agarwal-674a21166_language-activity-7319042198430195712-vVJy

URL: https://www.linkedin.com/posts/absami_golang-nodejs-devhumor-activity-7316531911126933505-kH

URL: https://www.linkedin.com/posts/urielbitton_sql-is-not-easily-scalable-despite-what-people-activity-7315350270857666562-sbpV

URL: https://www.linkedin.com/posts/michelesollecito_in-my-own-company-i-wouldnt-hire-anyone-activity-7309491565603835904-uBhX

I can't wait to try out the groundbreaking but still traditional and comfortable C++ Profiles that are going to be "designed", "verified", and "implemented" in the span of about 3 years by the sharpest minds on the committee operating under the assumption that everybody is out to get them and that this feature is not only absolutely essential to the survival of C++ but at the same time the result of pointless bureaucracy cooked up by the perverted minds that seek to corrupt our way of life.

I am absolutely certain that I will be able to test out the feature in a functional compiler before the release of C++26.

Turns out we don't need a borrow checker after all. We can just use vague "AI code reasoning". This seems highly credible and I'm sure we're going to see a fully functional compiler and source release within the next 10 decades.