212
I will send you newest post from subreddit /r/programming
Moving Complexity Down: The Real Path to Scaling Up C++ Code - Malin Stanescu - CppCon 2025
https://www.reddit.com/r/programming/comments/1qi7jod/moving_complexity_down_the_real_path_to_scaling/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=SPHJ4yWE0Io) [comments] (https://www.reddit.com/r/programming/comments/1qi7jod/moving_complexity_down_the_real_path_to_scaling/)
Unconventional PostgreSQL Optimizations
https://www.reddit.com/r/programming/comments/1qi2gj7/unconventional_postgresql_optimizations/
submitted by /u/be_haki (https://www.reddit.com/user/be_haki)
[link] (https://hakibenita.com/postgresql-unconventional-optimizations) [comments] (https://www.reddit.com/r/programming/comments/1qi2gj7/unconventional_postgresql_optimizations/)
https://www.reddit.com/r/programming/comments/1qi0soq/par_language_update_crazy_if_implicit_generics/
<!-- SC_OFF -->Thought I'd give you all an update on how the Par programming language (https://github.com/faiface/par-lang) is doing. Par is an experimental programming language built around linear types, duality, automatic concurrency, and a couple more innovations. I've posted a video called "Async without Await" (https://www.reddit.com/r/programming/comments/1p0goii/what_if_everything_was_async_but_nothing_needed/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button) on this subreddit and you guys were pretty interested ;) Recently, we've achieved 3 major items on the Current Roadmap (https://github.com/faiface/par-lang/issues/127)! I'm very happy about them, and I really wonder what you think about their design. Conditions & if Read the full doc here. (https://faiface.github.io/par-lang/quality_of_life/if.html) Since the beginning, Par has had the either types, ie. "sum types", with the .case destruction. For boolean conditions, it would end up looking like this: condition.case { .true! => ... .false! => ... } That gets very verbose with complex conditions, so now we also have an if! if { condition1 => ... condition2 => ... condition3 => ... else => ... } Supports and, or, and not: if { condition1 or not condition2 => ... condition3 and condition4 => ... else => ... } But most importantly, it supports this is for matching either types inside conditions. if { result is .ok value => value, else => "", } And you can combine it seamlessly with other conditions: if { result is .ok value and value->String.Equals("") => "", result is .ok value => value, else => "", } Here's the crazy part: The bindings from is are available in all paths where they should. Even under not! if { not result is .ok value => "", else => value, // !!! } Do you see it? The value is bound in the first condition, but because of the not, it's available in the else. This is more useful than it sounds. Here's one big usecase. In process syntax (somewhat imperative), we have a special one-condition version of if that looks like this: if condition => { ... } ... It works very much like it would in any other language. Here's what I can do with not: if not result is .ok value => { console.print("Missing value.") exit! } // use `value` here Bind or early return! And if we wanna slap an additional condition, not a problem: if not result is .ok value or value->String.Equals("") => { console.print("Missing or empty value.") exit! } // use `value` here This is not much different from what you'd do in Java: if (result.isEmpty() || result.get().equals("")) { log("Missing or empty value."); return; } var value = result.get(); Except all well typed. Implicit generics Read the full doc here. (https://faiface.github.io/par-lang/types/implicit_generics.html) We've had explicit first-class generics for a long time, but of course, that can get annoyingly verbose. dec Reverse : [type a] [List] List ... let reversed = Reverse(type Int)(Int.Range(1, 10)) With the new implicit version (still first-class, System F style), it's much nicer: dec Reverse : [List] List ... let reversed = Reverse(Int.Range(1, 10)) Or even: let reversed = Int.Range(1, 10)->Reverse Much better. It has its limitations, read the full docs to find out. New Runtime As you may or may not know, Par's runtime is based on interaction networks, just like HVM, Bend, or Vine. However, unlike those languages, Par supports powerful concurrent I/O, and is focused on expressivity and concurrency via linear logic instead of maximum performance. However, recently we've been able to pull off a new runtime, that's 2-3x faster than the previous one. It still has a long way to go in terms of performance (and we even known how), but it's already a big step forward. <!-- SC_ON --> submitted by /u/faiface (https://www.reddit.com/user/faiface)
The Only Two Markup Languages
https://www.reddit.com/r/programming/comments/1qhzgtc/the_only_two_markup_languages/
submitted by /u/gingerbill (https://www.reddit.com/user/gingerbill)
[link] (https://www.gingerbill.org/article/2026/01/19/two-families-of-markup-languages/) [comments] (https://www.reddit.com/r/programming/comments/1qhzgtc/the_only_two_markup_languages/)
A hacker is making a list of vibecoded apps, 198 scanned 196 with vulnerabilities
https://www.reddit.com/r/programming/comments/1qhw9zg/a_hacker_is_making_a_list_of_vibecoded_apps_198/
submitted by /u/bored_wombat_v1 (https://www.reddit.com/user/bored_wombat_v1)
[link] (https://firehound.covertlabs.io/) [comments] (https://www.reddit.com/r/programming/comments/1qhw9zg/a_hacker_is_making_a_list_of_vibecoded_apps_198/)
Building Faster Data Pipelines in Python with Apache Arrow
https://www.reddit.com/r/programming/comments/1qhvr7t/building_faster_data_pipelines_in_python_with/
submitted by /u/Low-Engineering-4571 (https://www.reddit.com/user/Low-Engineering-4571)
[link] (https://python.plainenglish.io/stop-paying-the-json-tax-build-faster-data-pipelines-in-python-with-apache-arrow-a37ce670a1f1) [comments] (https://www.reddit.com/r/programming/comments/1qhvr7t/building_faster_data_pipelines_in_python_with/)
Lapce: A Rust-Based Native Code Editor Lighter Than VSCode and Zed
https://www.reddit.com/r/programming/comments/1qhuhw3/lapce_a_rustbased_native_code_editor_lighter_than/
submitted by /u/delvin0 (https://www.reddit.com/user/delvin0)
[link] (https://levelup.gitconnected.com/lapce-a-rust-based-native-code-editor-lighter-than-vscode-and-zed-627f6f2c2d84?sk=8cba9062b73a7731cc8fb692824326fe) [comments] (https://www.reddit.com/r/programming/comments/1qhuhw3/lapce_a_rustbased_native_code_editor_lighter_than/)
I decided to make a worse UUID for the pettiest of reasons.
https://www.reddit.com/r/programming/comments/1qhq372/i_decided_to_make_a_worse_uuid_for_the_pettiest/
submitted by /u/theghostofm (https://www.reddit.com/user/theghostofm)
[link] (https://gitpush--force.com/commits/2026/01/meet-smolid/) [comments] (https://www.reddit.com/r/programming/comments/1qhq372/i_decided_to_make_a_worse_uuid_for_the_pettiest/)
How revenue decisions shape technical debt
https://www.reddit.com/r/programming/comments/1qhisx9/how_revenue_decisions_shape_technical_debt/
submitted by /u/ArtisticProgrammer11 (https://www.reddit.com/user/ArtisticProgrammer11)
[link] (https://www.hyperact.co.uk/blog/how-revenue-decisions-shape-technical-debt) [comments] (https://www.reddit.com/r/programming/comments/1qhisx9/how_revenue_decisions_shape_technical_debt/)
Learning Rust as a working software engineer (real dev vlog)
https://www.reddit.com/r/programming/comments/1qhf5l3/learning_rust_as_a_working_software_engineer_real/
<!-- SC_OFF -->I recently started learning Rust and recorded a short dev vlog showing the very early phase - reading docs, writing code, getting confused, and dealing with the compiler. This isn’t a tutorial or polished content, just learning in public and sharing how Rust actually feels at the beginning. Video here:
https://youtu.be/0TQr2YJ5ogY Feedback from the Rust community is welcome 🦀 <!-- SC_ON --> submitted by /u/ms-arch (https://www.reddit.com/user/ms-arch)
[link] (https://youtu.be/0TQr2YJ5ogY) [comments] (https://www.reddit.com/r/programming/comments/1qhf5l3/learning_rust_as_a_working_software_engineer_real/)
Needy programs
https://www.reddit.com/r/programming/comments/1qhedcl/needy_programs/
submitted by /u/RevillWeb (https://www.reddit.com/user/RevillWeb)
[link] (https://tonsky.me/blog/needy-programs/?ref=dailydev) [comments] (https://www.reddit.com/r/programming/comments/1qhedcl/needy_programs/)
Using Servo with Slint
https://www.reddit.com/r/programming/comments/1qh7zeo/using_servo_with_slint/
<!-- SC_OFF -->Slint is a modern, open-source GUI Toolkit and Servo is a browser engine written in Rust. <!-- SC_ON --> submitted by /u/slint-ui (https://www.reddit.com/user/slint-ui)
[link] (https://slint.dev/blog/using-servo-with-slint) [comments] (https://www.reddit.com/r/programming/comments/1qh7zeo/using_servo_with_slint/)
How the Lobsters front page works
https://www.reddit.com/r/programming/comments/1qh44o1/how_the_lobsters_front_page_works/
submitted by /u/Xadartt (https://www.reddit.com/user/Xadartt)
[link] (https://atharvaraykar.com/lobsters/) [comments] (https://www.reddit.com/r/programming/comments/1qh44o1/how_the_lobsters_front_page_works/)
The Wasm Breach: Escaping Backend WebAssembly Sandboxes
https://www.reddit.com/r/programming/comments/1qh2aij/the_wasm_breach_escaping_backend_webassembly/
submitted by /u/JadeLuxe (https://www.reddit.com/user/JadeLuxe)
[link] (https://instatunnel.my/blog/the-wasm-breach-escaping-backend-webassembly-sandboxes) [comments] (https://www.reddit.com/r/programming/comments/1qh2aij/the_wasm_breach_escaping_backend_webassembly/)
New interview with Douglas Crockford
https://www.reddit.com/r/programming/comments/1qh1zz5/new_interview_with_douglas_crockford/
submitted by /u/yegor256 (https://www.reddit.com/user/yegor256)
[link] (https://youtu.be/BrlOIPEsSJ4) [comments] (https://www.reddit.com/r/programming/comments/1qh1zz5/new_interview_with_douglas_crockford/)
Accidentally making $1000 for finding Security Bugs as a Backend Developer
https://www.reddit.com/r/programming/comments/1qi3y9x/accidentally_making_1000_for_finding_security/
submitted by /u/overkiller_xd (https://www.reddit.com/user/overkiller_xd)
[link] (https://not-afraid.medium.com/accidentally-making-1000-for-finding-security-bugs-as-a-backend-developer-3e562c77eefc?post) [comments] (https://www.reddit.com/r/programming/comments/1qi3y9x/accidentally_making_1000_for_finding_security/)
[link] (https://github.com/faiface/par-lang) [comments] (https://www.reddit.com/r/programming/comments/1qi0soq/par_language_update_crazy_if_implicit_generics/)
Читать полностью…
Stop separating learning from building
https://www.reddit.com/r/programming/comments/1qi0k6l/stop_separating_learning_from_building/
submitted by /u/danielrothmann (https://www.reddit.com/user/danielrothmann)
[link] (https://blog.42futures.com/p/stop-separating-learning-from-building) [comments] (https://www.reddit.com/r/programming/comments/1qi0k6l/stop_separating_learning_from_building/)
C++17: Efficiently Returning std::vector from Functions
https://www.reddit.com/r/programming/comments/1qhwcnu/c17_efficiently_returning_stdvector_from_functions/
submitted by /u/Clean-Upstairs-8481 (https://www.reddit.com/user/Clean-Upstairs-8481)
[link] (https://techfortalk.co.uk/2026/01/18/c17-efficiently-returning-stdvector-from-functions/) [comments] (https://www.reddit.com/r/programming/comments/1qhwcnu/c17_efficiently_returning_stdvector_from_functions/)
Floating-Point Printing and Parsing Can Be Simple And Fast (Floating Point Formatting, Part 3)
https://www.reddit.com/r/programming/comments/1qhw709/floatingpoint_printing_and_parsing_can_be_simple/
submitted by /u/Dragdu (https://www.reddit.com/user/Dragdu)
[link] (https://research.swtch.com/fp) [comments] (https://www.reddit.com/r/programming/comments/1qhw709/floatingpoint_printing_and_parsing_can_be_simple/)
X has open-sourced their new 𝕏 algorithm, powered by the same transformer architecture as xAI's Grok model.
https://www.reddit.com/r/programming/comments/1qhunm9/x_has_opensourced_their_new_%F0%9D%95%8F_algorithm_powered/
submitted by /u/nix-solves-that-2317 (https://www.reddit.com/user/nix-solves-that-2317)
[link] (https://github.com/xai-org/x-algorithm) [comments] (https://www.reddit.com/r/programming/comments/1qhunm9/x_has_opensourced_their_new_%F0%9D%95%8F_algorithm_powered/)
Discussion: GitHub Copilot litigation highlights structural conflict of interest in code hosting & training — proposal for neutrality charter
https://www.reddit.com/r/programming/comments/1qhqj5k/discussion_github_copilot_litigation_highlights/
<!-- SC_OFF -->I’m an independent developer who’s been following the Copilot litigation closely, and I think the current legal approach misses a crucial structural fix. Fining Microsoft won’t resolve the underlying conflict of interest. As long as a trillion-dollar AI company controls the world’s most important code repository, the incentive to “harvest” code will always outweigh the duty to responsibly host it. Today I submitted a proposed Amicus Brief to lead counsel (Saveri & Butterick) that outlines a simple Charter of Neutrality: • Structural separation. Move GitHub into a neutral, foundation-backed utility (think Linux Foundation) so it serves the community rather than a single corporation. • Consent-first training. No code should be used for AI training without an explicit, transparent opt-in from contributors. • Neutral governance. Establish a community-led board with real authority to audit data usage and enforce the charter. I’m waiting for the legal team’s OK to file this officially with the court. We need to stop treating ourselves as passive “users” of GitHub and start acting as its architects. I’d love the community’s feedback on these pillars — if we don’t fix the structure now, when will we? <!-- SC_ON --> submitted by /u/Litteralybadenglish (https://www.reddit.com/user/Litteralybadenglish)
[link] (https://www.saverilawfirm.com/our-cases/github-copilot-intellectual-property-litigation) [comments] (https://www.reddit.com/r/programming/comments/1qhqj5k/discussion_github_copilot_litigation_highlights/)
Looking for subscription costs API
https://www.reddit.com/r/programming/comments/1qhjc2s/looking_for_subscription_costs_api/
<!-- SC_OFF -->I am looking for Api that has up to date prices of services like netflix amazon prime hulu xbox pass and etc. that gives me cost and tiers is there anything like that? <!-- SC_ON --> submitted by /u/department_of_eyes (https://www.reddit.com/user/department_of_eyes)
[link] (http://me.me/) [comments] (https://www.reddit.com/r/programming/comments/1qhjc2s/looking_for_subscription_costs_api/)
Fluxly - A lightweight, self-contained DAG workflow framework (decoupled from orchestration)
https://www.reddit.com/r/programming/comments/1qhikgp/fluxly_a_lightweight_selfcontained_dag_workflow/
<!-- SC_OFF -->Hi everyone, I wanted to share Fluxly, a framework I built for running portable, self-contained DAG workflows, inspired by architectural patterns I worked with at Mobileye. Core idea:
Each workflow is a standalone execution endpoint - structured, typed, and runnable without being coupled to any orchestrator. GitHub:
https://github.com/ShaharBand/fluxly --- 🚀 What Fluxly is Fluxly lets you define DAG-based workflows where: Each workflow runs as a single self-contained unit It can be triggered via CLI, API, or environment variables It can be packaged into a Docker image Any external scheduler (Airflow, Argo, CI/CD, cron, etc.) can trigger it without glue code The workflow owns its logic, validation, retries, and structure - orchestration is optional and external. --- ❓ Why I built it (the problem it tries to solve) From experience, many containerized pipelines end up as: Ad-hoc scripts scattered across containers Inconsistent inputs/outputs Retry, timeout, and logging logic duplicated or forgotten Tight coupling to a specific orchestrator SDK On the other hand: Heavy orchestrators (Airflow, etc.) introduce operational overhead when all you want is a portable job Orchestrator-coupled SDKs assume persistent backends and remote control planes, which don’t fit fire-and-forget workloads Fluxly keeps the workflow clean and isolated: Explicit DAG Typed I/O models Uniform entrypoints (CLI / API / env) Clear node boundaries No hidden runtime coupling It works especially well when: Each Docker image should be simple and autonomous You want structure without infrastructure overhead You want the same workflow to run locally, in CI, or under any scheduler In monorepos (or via thin wrappers), Fluxly can also standardize validation, logging, metadata, and interfaces across many pipelines. --- ✨ Key features DAG-based workflows with explicit dependencies Auto-generated CLI commands and FastAPI endpoints per workflow Strict validation using Pydantic models Nodes manage their own execution and retries Local-first development, production-ready execution Easy to extend with logging, metrics, or org-specific wrappers --- 🛠️ Stack Python, Pydantic, Typer, FastAPI, Uvicorn, Loguru, Diagrams, Pixi, Ruff, Mypy, Pytest, MkDocs --- 📦 Install pip install fluxly --- 🙏 Feedback welcome
I’d love feedback and Happy to answer questions or discuss tradeoffs. <!-- SC_ON --> submitted by /u/ShaharBand (https://www.reddit.com/user/ShaharBand)
[link] (https://github.com/ShaharBand/fluxly) [comments] (https://www.reddit.com/r/programming/comments/1qhikgp/fluxly_a_lightweight_selfcontained_dag_workflow/)
Building the world’s first open-source quantum computer
https://www.reddit.com/r/programming/comments/1qhex3i/building_the_worlds_first_opensource_quantum/
submitted by /u/donutloop (https://www.reddit.com/user/donutloop)
[link] (https://uwaterloo.ca/news/global-futures/building-worlds-first-open-source-quantum-computer) [comments] (https://www.reddit.com/r/programming/comments/1qhex3i/building_the_worlds_first_opensource_quantum/)
Copy-on-write teaches you everything about Swift Internals 🐮
https://www.reddit.com/r/programming/comments/1qh97lb/copyonwrite_teaches_you_everything_about_swift/
submitted by /u/jacobs-tech-tavern (https://www.reddit.com/user/jacobs-tech-tavern)
[link] (https://blog.jacobstechtavern.com/p/copy-on-write-swift-internals) [comments] (https://www.reddit.com/r/programming/comments/1qh97lb/copyonwrite_teaches_you_everything_about_swift/)
On rebuilding read models, Dead-Letter Queues and Why Letting Go is Sometimes the Answer
https://www.reddit.com/r/programming/comments/1qh6amq/on_rebuilding_read_models_deadletter_queues_and/
submitted by /u/Adventurous-Salt8514 (https://www.reddit.com/user/Adventurous-Salt8514)
[link] (https://event-driven.io/en/rebuilding_read_models_skipping_events/) [comments] (https://www.reddit.com/r/programming/comments/1qh6amq/on_rebuilding_read_models_deadletter_queues_and/)
Simulation of "The Ladybird Clock Puzzle"
https://www.reddit.com/r/programming/comments/1qh2b19/simulation_of_the_ladybird_clock_puzzle/
submitted by /u/lungi_bass (https://www.reddit.com/user/lungi_bass)
[link] (https://navendu.me/posts/ladybug-clock-puzzle/) [comments] (https://www.reddit.com/r/programming/comments/1qh2b19/simulation_of_the_ladybird_clock_puzzle/)
AI is Not Ready to Replace Junior Devs Says Ruby on Rails Creator
https://www.reddit.com/r/programming/comments/1qh23o0/ai_is_not_ready_to_replace_junior_devs_says_ruby/
submitted by /u/ImpressiveContest283 (https://www.reddit.com/user/ImpressiveContest283)
[link] (https://www.finalroundai.com/blog/ai-can-not-replace-junior-programmers) [comments] (https://www.reddit.com/r/programming/comments/1qh23o0/ai_is_not_ready_to_replace_junior_devs_says_ruby/)
The hidden cost of PostgreSQL arrays
https://www.reddit.com/r/programming/comments/1qh13xf/the_hidden_cost_of_postgresql_arrays/
<!-- SC_OFF -->Very thoughtful piece on the tradeoffs of Postgres ARRAYs that in many case can replace one-to-many & many-to-many relationships: Wait? Are we going to talk about JSONB arrays? Not at all. The whole concept of arrays in RDBMSs is actually document storage in disguise. In database design, locality ensures faster retrieval times by keeping related data close on physical storage.Whether you use a distinct integer[] type or a JSON list [1, 2, 3], you are making the exact same architectural decision: you are prioritising locality over normalisation. <!-- SC_ON --> submitted by /u/BinaryIgor (https://www.reddit.com/user/BinaryIgor)
[link] (https://boringsql.com/posts/good-bad-arrays/) [comments] (https://www.reddit.com/r/programming/comments/1qh13xf/the_hidden_cost_of_postgresql_arrays/)