Reddit Programming – Telegram
Reddit Programming
211 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
Excel: The World’s Most Successful Functional Programming Platform By Houston Haynes
https://www.reddit.com/r/programming/comments/1pn7cea/excel_the_worlds_most_successful_functional/

<!-- SC_OFF -->Houston Haynes delivered one of the most surprising and thought-provoking talks of the year: a reframing of Excel not just as a spreadsheet tool, but as the world’s most widely adopted functional programming platform. The talk combined personal journey, technical insight, business strategy, and even a bit of FP philosophy — challenging the functional programming community to rethink the boundaries of their craft and the audience it serves. <!-- SC_ON --> submitted by /u/MagnusSedlacek (https://www.reddit.com/user/MagnusSedlacek)
[link] (https://youtu.be/rpe5vrhFATA) [comments] (https://www.reddit.com/r/programming/comments/1pn7cea/excel_the_worlds_most_successful_functional/)
IPC Mechanisms: Shared Memory vs. Message Queues Performance Benchmarking
https://www.reddit.com/r/programming/comments/1pn84ce/ipc_mechanisms_shared_memory_vs_message_queues/

<!-- SC_OFF -->Pushing 500K messages per second between processes and sys CPU time is through the roof. Your profiler shows mq_send() and mq_receive() dominating the flame graph. Each message is tiny—maybe 64 bytes—but you’re burning 40% CPU just on IPC overhead. This isn’t a hypothetical. LinkedIn’s Kafka producers hit exactly this wall. Message queue syscalls were killing throughput. They switched to shared memory ring buffers and saw context switches drop from 100K/sec to near-zero. The difference? Every message queue operation is a syscall with user→kernel→user memory copies. Shared memory lets you write directly to memory the other process can read. No syscall after setup, no context switch, no copy. The performance cliff sneaks up on you. At low rates, message queues work fine—the kernel handles synchronization and you get clean blocking semantics. But scale up and suddenly you’re paying 60-100ns per syscall, plus the cost of copying data twice and context switching when queues block. Shared memory with lock-free algorithms can hit sub-microsecond latencies, but you’re now responsible for synchronization, cache coherency, and cleanup if a process crashes mid-operation. <!-- SC_ON --> submitted by /u/Extra_Ear_10 (https://www.reddit.com/user/Extra_Ear_10)
[link] (https://howtech.substack.com/p/ipc-mechanisms-shared-memory-vs-message) [comments] (https://www.reddit.com/r/programming/comments/1pn84ce/ipc_mechanisms_shared_memory_vs_message_queues/)
JetBrains Fleet dropped for AI products instead
https://www.reddit.com/r/programming/comments/1pnz3n0/jetbrains_fleet_dropped_for_ai_products_instead/

<!-- SC_OFF -->JetBrains Fleet was going to be an alternative to VS Code and seemed quite promising. After over 3 years of development since the first public preview release, it’s now dropped in order to make room for AI (Agentic) products. – “Starting December 22, 2025, Fleet will no longer be available for download. We are now building a new product focused on agentic development” At the very least, they’re considering open sourcing it, but it’s not definite. A comment from the author of the article (https://blog.jetbrains.com/fleet/2025/12/the-future-of-fleet/#remark42__comment-f3d6d88b-f10d-4f0a-9579-a6b940314b01) regarding open sourcing Fleet: – “It’s something we’re considering but we don’t have immediate plans for that at the moment.” <!-- SC_ON --> submitted by /u/markmanam (https://www.reddit.com/user/markmanam)
[link] (https://blog.jetbrains.com/fleet/2025/12/the-future-of-fleet/) [comments] (https://www.reddit.com/r/programming/comments/1pnz3n0/jetbrains_fleet_dropped_for_ai_products_instead/)
"If you time-traveled to 1979 and found yourself sitting across from me in my office at Bell Labs—just as I was drafting the initial designs for what would become 'C with Classes'—what would you tell me?": A homework by Bjarne Stroustrup.
https://www.reddit.com/r/programming/comments/1po5nq5/if_you_timetraveled_to_1979_and_found_yourself/

<!-- SC_OFF -->This was a homework given by Bjarne Stroustrup when he was my professor at Texas A&M University in Spring Semester of 2013. The course, Generic Programming in C++, was one of the most fun classes I took at Texas A&M University. I'm posting it in my blog. https://coderschmoder.com/i-time-traveled-1979-met-bjarne-stroustrup
Take note that I updated the essay to reflect current C++ releases. My original essay was written when C++11 was released, and I mostly talked about RAII, and data type abstractions. Although I thought my essay was lacking in substance, he gave me a 95 :-D. So, I thought I update my essay and share it with you. When he gave the homework I think the context of the conversation was critics were ready for C++ to die because of lack of garbage collection or memory management, and the homework was akin to killing two birds with one stone(so to speak) - one, to see if we understand RAII and the life cycle of a C++ object, and two, how we see this "shortcomings" of C++. How about you? If you time-travel back to 1979, what would you tell him? <!-- SC_ON --> submitted by /u/CoderSchmoder (https://www.reddit.com/user/CoderSchmoder)
[link] (https://coderschmoder.com/i-time-traveled-1979-met-bjarne-stroustrup) [comments] (https://www.reddit.com/r/programming/comments/1po5nq5/if_you_timetraveled_to_1979_and_found_yourself/)
Sandboxing AI Agents: Practical Ways to Limit Autonomous Behavior
https://www.reddit.com/r/programming/comments/1po8ar9/sandboxing_ai_agents_practical_ways_to_limit/

<!-- SC_OFF -->I’ve been exploring how to safely deploy autonomous AI agents without giving them too much freedom. In practice, the biggest risks come from: unrestricted tool access filesystem and network exposure agents looping or escalating actions unexpectedly I looked at different sandboxing approaches: containers (Docker, OCI) microVMs (Firecracker) user-mode kernels (gVisor) permission-based tool execution I wrote a deeper breakdown with concrete examples and trade-offs here : https://medium.com/@yessine.abdelmaksoud.03/sandboxing-for-ai-agents-2420ac69569e I’d really appreciate feedback from people working with agents in production. <!-- SC_ON --> submitted by /u/After_Customer251 (https://www.reddit.com/user/After_Customer251)
[link] (https://medium.com/@yessine.abdelmaksoud.03/sandboxing-for-ai-agents-2420ac69569e) [comments] (https://www.reddit.com/r/programming/comments/1po8ar9/sandboxing_ai_agents_practical_ways_to_limit/)