Reddit Programming – Telegram
Reddit Programming
211 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
What if everything was "Async", but nothing needed "Await"? -- Automatic Concurrency in Par
https://www.reddit.com/r/programming/comments/1p0goii/what_if_everything_was_async_but_nothing_needed/

<!-- SC_OFF -->I made a new video, showcasing and explaining the "automatic concurrency" in the Par programming language (https://github.com/faiface/par-lang)! I think this is the first time I actually manage to convey this unusual, but absolutely foundational feature of my language. In the video, I walk through a "concurrent downloader" application, visualize how it's put together, and explain how Par's concurrent evaluation makes it all work. I'm very curious to hear what you think! And if you don't know, Par is an innovative (and WIP) programming language with linear types, duality, automatic concurrency, and more. Yesterday's discussion in r/ProgrammingLanguages (https://www.reddit.com/r/ProgrammingLanguages): https://www.reddit.com/r/ProgrammingLanguages/comments/1ozlvuw/what_if_everything_was_async_but_nothing_needed/ <!-- SC_ON --> submitted by /u/faiface (https://www.reddit.com/user/faiface)
[link] (https://youtu.be/tpICs7uG3n8) [comments] (https://www.reddit.com/r/programming/comments/1p0goii/what_if_everything_was_async_but_nothing_needed/)
Being Gullible About User Feedback Can Hurt UX
https://www.reddit.com/r/programming/comments/1p1dexs/being_gullible_about_user_feedback_can_hurt_ux/

<!-- SC_OFF -->A reflection on how easily teams can be misled by user feedback, especially when comments hide embarrassment or uncertainty, and how careful observation reveals a truth that words alone never fully show <!-- SC_ON --> submitted by /u/gamunu (https://www.reddit.com/user/gamunu)
[link] (https://fastcode.io/2025/11/19/being-gullible-about-user-feedback-can-hurt-ux/) [comments] (https://www.reddit.com/r/programming/comments/1p1dexs/being_gullible_about_user_feedback_can_hurt_ux/)
A breakdown of all OAuth 2.0 authorization flows (Server-side, PKCE, Device Code, Client Credentials)
https://www.reddit.com/r/programming/comments/1p1kplp/a_breakdown_of_all_oauth_20_authorization_flows/

<!-- SC_OFF -->I put together a practical deep-dive explaining the major OAuth 2.0 flows with diagrams: Authorization Code Flow (server-side apps) PKCE Flow (SPAs + mobile apps) Client Credentials (machine-to-machine) Device Authorization Flow (TVs, consoles, IoT) The goal was to make it easier for developers to know which flow to use for which type of app and why these flows exist at all. <!-- SC_ON --> submitted by /u/sshetty03 (https://www.reddit.com/user/sshetty03)
[link] (https://medium.com/stackademic/a-developers-guide-to-oauth-2-0-workflows-web-mobile-spa-machine-to-machine-and-device-flows-2651b6479e17?sk=b89d9953f37c87573c5f579fd0b6af08) [comments] (https://www.reddit.com/r/programming/comments/1p1kplp/a_breakdown_of_all_oauth_20_authorization_flows/)