LogMod: What if C had a logging framework with modern semantics?
https://www.reddit.com/r/programming/comments/1oc2h8k/logmod_what_if_c_had_a_logging_framework_with/
<!-- SC_OFF -->In my own experience when looking into C logging libraries, I found that they either rely on hidden global state or quietly calls malloc behind the scenes. In environments where you need deterministic memory usage and explicit control over resources, that’s problematic. I wanted to see if it was possible to bring more “modern” logging semantics - things like configurable contexts, custom labels, colour coding, callbacks and thread‐safety - into plain ANSI C without using dynamic memory or preprocessor magic. (it is possible!) LogMod is the result. It’s a single‑header library that lets you initialise a logging context with a fixed table of loggers, pass that context around instead of using globals, define your own severity levels and colours, hook in custom callbacks, and even make it thread‑safe with a user‑supplied lock. It avoids malloc entirely. The challenge was fitting all of this into a few hundred lines of portable code and retaining C’s “zero-overhead” philosophy. <!-- SC_ON --> submitted by /u/LucasMull (https://www.reddit.com/user/LucasMull)
[link] (https://github.com/lcsmuller/logmod) [comments] (https://www.reddit.com/r/programming/comments/1oc2h8k/logmod_what_if_c_had_a_logging_framework_with/)
https://www.reddit.com/r/programming/comments/1oc2h8k/logmod_what_if_c_had_a_logging_framework_with/
<!-- SC_OFF -->In my own experience when looking into C logging libraries, I found that they either rely on hidden global state or quietly calls malloc behind the scenes. In environments where you need deterministic memory usage and explicit control over resources, that’s problematic. I wanted to see if it was possible to bring more “modern” logging semantics - things like configurable contexts, custom labels, colour coding, callbacks and thread‐safety - into plain ANSI C without using dynamic memory or preprocessor magic. (it is possible!) LogMod is the result. It’s a single‑header library that lets you initialise a logging context with a fixed table of loggers, pass that context around instead of using globals, define your own severity levels and colours, hook in custom callbacks, and even make it thread‑safe with a user‑supplied lock. It avoids malloc entirely. The challenge was fitting all of this into a few hundred lines of portable code and retaining C’s “zero-overhead” philosophy. <!-- SC_ON --> submitted by /u/LucasMull (https://www.reddit.com/user/LucasMull)
[link] (https://github.com/lcsmuller/logmod) [comments] (https://www.reddit.com/r/programming/comments/1oc2h8k/logmod_what_if_c_had_a_logging_framework_with/)
AI bro introduces regressions in the LTS Linux kernel
https://www.reddit.com/r/programming/comments/1oc38d2/ai_bro_introduces_regressions_in_the_lts_linux/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://xcancel.com/spendergrsec/status/1979997322646786107) [comments] (https://www.reddit.com/r/programming/comments/1oc38d2/ai_bro_introduces_regressions_in_the_lts_linux/)
https://www.reddit.com/r/programming/comments/1oc38d2/ai_bro_introduces_regressions_in_the_lts_linux/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://xcancel.com/spendergrsec/status/1979997322646786107) [comments] (https://www.reddit.com/r/programming/comments/1oc38d2/ai_bro_introduces_regressions_in_the_lts_linux/)
Sinkhorn-Knopp Algorithm: Like Softmax but for Optimal Transport
https://www.reddit.com/r/programming/comments/1oc3ond/sinkhornknopp_algorithm_like_softmax_but_for/
submitted by /u/DataBaeBee (https://www.reddit.com/user/DataBaeBee)
[link] (https://leetarxiv.substack.com/p/sinkhorn-knopp-algorithm-24d) [comments] (https://www.reddit.com/r/programming/comments/1oc3ond/sinkhornknopp_algorithm_like_softmax_but_for/)
https://www.reddit.com/r/programming/comments/1oc3ond/sinkhornknopp_algorithm_like_softmax_but_for/
submitted by /u/DataBaeBee (https://www.reddit.com/user/DataBaeBee)
[link] (https://leetarxiv.substack.com/p/sinkhorn-knopp-algorithm-24d) [comments] (https://www.reddit.com/r/programming/comments/1oc3ond/sinkhornknopp_algorithm_like_softmax_but_for/)
Semaev's Index Calculus Attack on Elliptic Curves
https://www.reddit.com/r/programming/comments/1oc91no/semaevs_index_calculus_attack_on_elliptic_curves/
submitted by /u/DataBaeBee (https://www.reddit.com/user/DataBaeBee)
[link] (https://leetarxiv.substack.com/p/semaev-naive-index-calculus) [comments] (https://www.reddit.com/r/programming/comments/1oc91no/semaevs_index_calculus_attack_on_elliptic_curves/)
https://www.reddit.com/r/programming/comments/1oc91no/semaevs_index_calculus_attack_on_elliptic_curves/
submitted by /u/DataBaeBee (https://www.reddit.com/user/DataBaeBee)
[link] (https://leetarxiv.substack.com/p/semaev-naive-index-calculus) [comments] (https://www.reddit.com/r/programming/comments/1oc91no/semaevs_index_calculus_attack_on_elliptic_curves/)
AWS US-EAST-1 Outage (Oct 2025): What Happened and What We Can Learn
https://www.reddit.com/r/programming/comments/1oca1a9/aws_useast1_outage_oct_2025_what_happened_and/
<!-- SC_OFF -->Hope everyone’s fine :) <!-- SC_ON --> submitted by /u/BrilliantWaltz6397 (https://www.reddit.com/user/BrilliantWaltz6397)
[link] (https://www.techupkeep.dev/blog/aws-outage-october-2025-analysis) [comments] (https://www.reddit.com/r/programming/comments/1oca1a9/aws_useast1_outage_oct_2025_what_happened_and/)
https://www.reddit.com/r/programming/comments/1oca1a9/aws_useast1_outage_oct_2025_what_happened_and/
<!-- SC_OFF -->Hope everyone’s fine :) <!-- SC_ON --> submitted by /u/BrilliantWaltz6397 (https://www.reddit.com/user/BrilliantWaltz6397)
[link] (https://www.techupkeep.dev/blog/aws-outage-october-2025-analysis) [comments] (https://www.reddit.com/r/programming/comments/1oca1a9/aws_useast1_outage_oct_2025_what_happened_and/)
Walrus: a high performance storage engine built from first principles
https://www.reddit.com/r/programming/comments/1ocb0w2/walrus_a_high_performance_storage_engine_built/
<!-- SC_OFF -->Hi, recently I've been working on a high performance storage engine in Rust called Walrus, A little bit of intro, Walrus is an embedded in-process storage engine built from first principles and can be used as a building block to build these things right out of the box: Timeseries Event Log: Immutable audit trails, compliance tracking. Every event persisted immediately, read exactly once. Database WAL: PostgreSQL style transaction logs. Maximum durability for commits, deterministic crash recovery. Message Queue: Kafka style streaming. Batch writes (up to 2000 entries), high throughput, at least once delivery. Key Value Store: Simple persistent cache. Each key is a topic, fast writes with 50ms fsync window. Task Queue: Async job processing. At least once delivery with retry safe workers (handlers should be idempotent). ... and much more the recent release outperforms single node apache kafka and rocksdb at the workloads of their choice (benchmarks in repo) repo: https://github.com/nubskr/walrus If you're interested in learning about walrus's internals, these two release posts will give you all you need: v0.1.0 release post:https://nubskr.com/2025/10/06/walrus (yes, it was supposed to be a write ahead log in the beginning) v0.2.0 release post: https://nubskr.com/2025/10/20/walrus_v0.2.0 I'm looking forward to hearing feedback from the community and the works of a 'distributed' version of walrus are in progress. <!-- SC_ON --> submitted by /u/Ok_Marionberry8922 (https://www.reddit.com/user/Ok_Marionberry8922)
[link] (https://github.com/nubskr/walrus) [comments] (https://www.reddit.com/r/programming/comments/1ocb0w2/walrus_a_high_performance_storage_engine_built/)
https://www.reddit.com/r/programming/comments/1ocb0w2/walrus_a_high_performance_storage_engine_built/
<!-- SC_OFF -->Hi, recently I've been working on a high performance storage engine in Rust called Walrus, A little bit of intro, Walrus is an embedded in-process storage engine built from first principles and can be used as a building block to build these things right out of the box: Timeseries Event Log: Immutable audit trails, compliance tracking. Every event persisted immediately, read exactly once. Database WAL: PostgreSQL style transaction logs. Maximum durability for commits, deterministic crash recovery. Message Queue: Kafka style streaming. Batch writes (up to 2000 entries), high throughput, at least once delivery. Key Value Store: Simple persistent cache. Each key is a topic, fast writes with 50ms fsync window. Task Queue: Async job processing. At least once delivery with retry safe workers (handlers should be idempotent). ... and much more the recent release outperforms single node apache kafka and rocksdb at the workloads of their choice (benchmarks in repo) repo: https://github.com/nubskr/walrus If you're interested in learning about walrus's internals, these two release posts will give you all you need: v0.1.0 release post:https://nubskr.com/2025/10/06/walrus (yes, it was supposed to be a write ahead log in the beginning) v0.2.0 release post: https://nubskr.com/2025/10/20/walrus_v0.2.0 I'm looking forward to hearing feedback from the community and the works of a 'distributed' version of walrus are in progress. <!-- SC_ON --> submitted by /u/Ok_Marionberry8922 (https://www.reddit.com/user/Ok_Marionberry8922)
[link] (https://github.com/nubskr/walrus) [comments] (https://www.reddit.com/r/programming/comments/1ocb0w2/walrus_a_high_performance_storage_engine_built/)
Pasta/80 is a simple Pascal cross compiler targeting the Z80 microprocessor
https://www.reddit.com/r/programming/comments/1ocbg19/pasta80_is_a_simple_pascal_cross_compiler/
submitted by /u/mariuz (https://www.reddit.com/user/mariuz)
[link] (https://github.com/pleumann/pasta80) [comments] (https://www.reddit.com/r/programming/comments/1ocbg19/pasta80_is_a_simple_pascal_cross_compiler/)
https://www.reddit.com/r/programming/comments/1ocbg19/pasta80_is_a_simple_pascal_cross_compiler/
submitted by /u/mariuz (https://www.reddit.com/user/mariuz)
[link] (https://github.com/pleumann/pasta80) [comments] (https://www.reddit.com/r/programming/comments/1ocbg19/pasta80_is_a_simple_pascal_cross_compiler/)
URLPattern is now Baseline Newly available
https://www.reddit.com/r/programming/comments/1ocdsc8/urlpattern_is_now_baseline_newly_available/
submitted by /u/feross (https://www.reddit.com/user/feross)
[link] (https://web.dev/blog/baseline-urlpattern?hl=en) [comments] (https://www.reddit.com/r/programming/comments/1ocdsc8/urlpattern_is_now_baseline_newly_available/)
https://www.reddit.com/r/programming/comments/1ocdsc8/urlpattern_is_now_baseline_newly_available/
submitted by /u/feross (https://www.reddit.com/user/feross)
[link] (https://web.dev/blog/baseline-urlpattern?hl=en) [comments] (https://www.reddit.com/r/programming/comments/1ocdsc8/urlpattern_is_now_baseline_newly_available/)
Engineering is science is engineering
https://www.reddit.com/r/programming/comments/1oce4m3/engineering_is_science_is_engineering/
<!-- SC_OFF -->I've been thinking about how much software engineering feels like scientific work these days — experimentation, modeling, iteration. I tried to explore that overlap in an essay and would love to hear if this resonates with your experience. <!-- SC_ON --> submitted by /u/Tiendil (https://www.reddit.com/user/Tiendil)
[link] (https://tiendil.org/en/posts/engineering-is-science-is-engineering) [comments] (https://www.reddit.com/r/programming/comments/1oce4m3/engineering_is_science_is_engineering/)
https://www.reddit.com/r/programming/comments/1oce4m3/engineering_is_science_is_engineering/
<!-- SC_OFF -->I've been thinking about how much software engineering feels like scientific work these days — experimentation, modeling, iteration. I tried to explore that overlap in an essay and would love to hear if this resonates with your experience. <!-- SC_ON --> submitted by /u/Tiendil (https://www.reddit.com/user/Tiendil)
[link] (https://tiendil.org/en/posts/engineering-is-science-is-engineering) [comments] (https://www.reddit.com/r/programming/comments/1oce4m3/engineering_is_science_is_engineering/)
Connection Pool Exhaustion: The Silent Killer
https://www.reddit.com/r/programming/comments/1ochumi/connection_pool_exhaustion_the_silent_killer/
<!-- SC_OFF -->Why This Matters Connection pooling is how modern applications reuse expensive network sockets instead of creating fresh ones for each request. A pool of 50 connections can handle millions of requests—as long as connections circulate fast. But the moment a connection gets stuck (slow query, network hang, deadlock), the pool shrinks. When it hits zero, you’re not just slow; you’re dead. Real-world: LinkedIn experienced a 4-hour outage when a stored procedure became slow, holding connections until the pool was exhausted. Stripe saw cascading payment failures when a downstream service got sluggish, starving connections and blocking all transactions. These weren’t capacity problems; they were circulation problems. <!-- SC_ON --> submitted by /u/Extra_Ear_10 (https://www.reddit.com/user/Extra_Ear_10)
[link] (https://howtech.substack.com/p/connection-pool-exhaustion-the-silent) [comments] (https://www.reddit.com/r/programming/comments/1ochumi/connection_pool_exhaustion_the_silent_killer/)
https://www.reddit.com/r/programming/comments/1ochumi/connection_pool_exhaustion_the_silent_killer/
<!-- SC_OFF -->Why This Matters Connection pooling is how modern applications reuse expensive network sockets instead of creating fresh ones for each request. A pool of 50 connections can handle millions of requests—as long as connections circulate fast. But the moment a connection gets stuck (slow query, network hang, deadlock), the pool shrinks. When it hits zero, you’re not just slow; you’re dead. Real-world: LinkedIn experienced a 4-hour outage when a stored procedure became slow, holding connections until the pool was exhausted. Stripe saw cascading payment failures when a downstream service got sluggish, starving connections and blocking all transactions. These weren’t capacity problems; they were circulation problems. <!-- SC_ON --> submitted by /u/Extra_Ear_10 (https://www.reddit.com/user/Extra_Ear_10)
[link] (https://howtech.substack.com/p/connection-pool-exhaustion-the-silent) [comments] (https://www.reddit.com/r/programming/comments/1ochumi/connection_pool_exhaustion_the_silent_killer/)
Why Postgres FDW Made My Queries Slow (and How I Fixed It) | Svix Blog
https://www.reddit.com/r/programming/comments/1ock2c4/why_postgres_fdw_made_my_queries_slow_and_how_i/
submitted by /u/j_platte (https://www.reddit.com/user/j_platte)
[link] (https://www.svix.com/blog/fdw-pitfalls/) [comments] (https://www.reddit.com/r/programming/comments/1ock2c4/why_postgres_fdw_made_my_queries_slow_and_how_i/)
https://www.reddit.com/r/programming/comments/1ock2c4/why_postgres_fdw_made_my_queries_slow_and_how_i/
submitted by /u/j_platte (https://www.reddit.com/user/j_platte)
[link] (https://www.svix.com/blog/fdw-pitfalls/) [comments] (https://www.reddit.com/r/programming/comments/1ock2c4/why_postgres_fdw_made_my_queries_slow_and_how_i/)
Alexander Stathis: Scaling a Modular Rails Monolith at AngelList - On Rails
https://www.reddit.com/r/programming/comments/1ockyqe/alexander_stathis_scaling_a_modular_rails/
submitted by /u/robbyrussell (https://www.reddit.com/user/robbyrussell)
[link] (https://onrails.buzzsprout.com/2462975/episodes/17978596-alexander-stathis-scaling-a-modular-rails-monolith-at-angellist) [comments] (https://www.reddit.com/r/programming/comments/1ockyqe/alexander_stathis_scaling_a_modular_rails/)
https://www.reddit.com/r/programming/comments/1ockyqe/alexander_stathis_scaling_a_modular_rails/
submitted by /u/robbyrussell (https://www.reddit.com/user/robbyrussell)
[link] (https://onrails.buzzsprout.com/2462975/episodes/17978596-alexander-stathis-scaling-a-modular-rails-monolith-at-angellist) [comments] (https://www.reddit.com/r/programming/comments/1ockyqe/alexander_stathis_scaling_a_modular_rails/)
Build Your Own Database
https://www.reddit.com/r/programming/comments/1ocl9ko/build_your_own_database/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://www.nan.fyi/database) [comments] (https://www.reddit.com/r/programming/comments/1ocl9ko/build_your_own_database/)
https://www.reddit.com/r/programming/comments/1ocl9ko/build_your_own_database/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://www.nan.fyi/database) [comments] (https://www.reddit.com/r/programming/comments/1ocl9ko/build_your_own_database/)
Why Git’s HEAD isn’t what most developers think it is
https://www.reddit.com/r/programming/comments/1ocm5vj/why_gits_head_isnt_what_most_developers_think_it/
<!-- SC_OFF -->Wrote a short explainer on a subtle Git concept - the difference between HEAD (your current commit pointer) and branch heads (.git/refs/heads/). It uses simple examples to show why “detached HEAD” isn’t an error and how refs actually move. <!-- SC_ON --> submitted by /u/sshetty03 (https://www.reddit.com/user/sshetty03)
[link] (https://medium.com/stackademic/head-vs-head-branches-in-git-commonly-misunderstood-terms-317241c72b1a?sk=d49e0d55ce71f3ea5bd76651b61ead8d) [comments] (https://www.reddit.com/r/programming/comments/1ocm5vj/why_gits_head_isnt_what_most_developers_think_it/)
https://www.reddit.com/r/programming/comments/1ocm5vj/why_gits_head_isnt_what_most_developers_think_it/
<!-- SC_OFF -->Wrote a short explainer on a subtle Git concept - the difference between HEAD (your current commit pointer) and branch heads (.git/refs/heads/). It uses simple examples to show why “detached HEAD” isn’t an error and how refs actually move. <!-- SC_ON --> submitted by /u/sshetty03 (https://www.reddit.com/user/sshetty03)
[link] (https://medium.com/stackademic/head-vs-head-branches-in-git-commonly-misunderstood-terms-317241c72b1a?sk=d49e0d55ce71f3ea5bd76651b61ead8d) [comments] (https://www.reddit.com/r/programming/comments/1ocm5vj/why_gits_head_isnt_what_most_developers_think_it/)
RestClient.Net 7: Compile-Time Safety and OpenAPI MCP Generation
https://www.reddit.com/r/programming/comments/1ocpi83/restclientnet_7_compiletime_safety_and_openapi/
<!-- SC_OFF -->Compile time safety for REST calls in .NET, along with MCP Server Generation from OpenAPI documents! <!-- SC_ON --> submitted by /u/emanresu_2017 (https://www.reddit.com/user/emanresu_2017)
[link] (https://www.christianfindlay.com/blog/restclient-net-7) [comments] (https://www.reddit.com/r/programming/comments/1ocpi83/restclientnet_7_compiletime_safety_and_openapi/)
https://www.reddit.com/r/programming/comments/1ocpi83/restclientnet_7_compiletime_safety_and_openapi/
<!-- SC_OFF -->Compile time safety for REST calls in .NET, along with MCP Server Generation from OpenAPI documents! <!-- SC_ON --> submitted by /u/emanresu_2017 (https://www.reddit.com/user/emanresu_2017)
[link] (https://www.christianfindlay.com/blog/restclient-net-7) [comments] (https://www.reddit.com/r/programming/comments/1ocpi83/restclientnet_7_compiletime_safety_and_openapi/)
Finding the sweet spot for using AI as a developer
https://www.reddit.com/r/programming/comments/1od15lx/finding_the_sweet_spot_for_using_ai_as_a_developer/
<!-- SC_OFF -->I'm on a journey (as most of you probably are) finding myself in this new hyped up AI world. This morning I had a bit of an aha-moment that I wanted to share. Currently there is a war going on between the programmers that love their craft, and people that just want results. While this is very polarizing, and probably generates a lot more interest. I'm just here in the middle trying to find the right balance with these new tools we are provided. This morning I had a bit of an aha-moment that I just wanted to share with you guys, and maybe get your two cents. If you have similar experiences, or are even further along on the journey than I am right now. <!-- SC_ON --> submitted by /u/mkdirusername (https://www.reddit.com/user/mkdirusername)
[link] (https://herland.me/blog/finding-the-sweet-spot-for-using-ai-as-a-developer/) [comments] (https://www.reddit.com/r/programming/comments/1od15lx/finding_the_sweet_spot_for_using_ai_as_a_developer/)
https://www.reddit.com/r/programming/comments/1od15lx/finding_the_sweet_spot_for_using_ai_as_a_developer/
<!-- SC_OFF -->I'm on a journey (as most of you probably are) finding myself in this new hyped up AI world. This morning I had a bit of an aha-moment that I wanted to share. Currently there is a war going on between the programmers that love their craft, and people that just want results. While this is very polarizing, and probably generates a lot more interest. I'm just here in the middle trying to find the right balance with these new tools we are provided. This morning I had a bit of an aha-moment that I just wanted to share with you guys, and maybe get your two cents. If you have similar experiences, or are even further along on the journey than I am right now. <!-- SC_ON --> submitted by /u/mkdirusername (https://www.reddit.com/user/mkdirusername)
[link] (https://herland.me/blog/finding-the-sweet-spot-for-using-ai-as-a-developer/) [comments] (https://www.reddit.com/r/programming/comments/1od15lx/finding_the_sweet_spot_for_using_ai_as_a_developer/)
What is good software architecture?
https://www.reddit.com/r/programming/comments/1od1l97/what_is_good_software_architecture/
submitted by /u/thewritingwallah (https://www.reddit.com/user/thewritingwallah)
[link] (https://newsletter.pragmaticengineer.com/p/what-is-good-software-architecture) [comments] (https://www.reddit.com/r/programming/comments/1od1l97/what_is_good_software_architecture/)
https://www.reddit.com/r/programming/comments/1od1l97/what_is_good_software_architecture/
submitted by /u/thewritingwallah (https://www.reddit.com/user/thewritingwallah)
[link] (https://newsletter.pragmaticengineer.com/p/what-is-good-software-architecture) [comments] (https://www.reddit.com/r/programming/comments/1od1l97/what_is_good_software_architecture/)
Race to the Root Cause — Talk at PyCon NL 2025
https://www.reddit.com/r/programming/comments/1od1siq/race_to_the_root_cause_talk_at_pycon_nl_2025/
<!-- SC_OFF -->Examples include: Chained Exception Puzzle: Python’s “During handling of the above exception, another exception occurred” messages rarely make the real flow obvious. We’ll see how these stacktraces force you to piece together what actually happened. The Missing Curly Bracket: Sometimes Python blames a line with a with statement, even though no code runs there. Why does this happen? And what does it have to do with curly brackets? By the end, you’ll have a better feel for Python’s stacktraces, some new strategies for debugging faster, and at least one story to share the next time a stacktrace tries to trick you. You’ll walk away with sharper debugging instincts, some practical tricks, and maybe a laugh at Python’s expense. If you’ve ever felt outsmarted by a stacktrace, this is your chance to race to the root cause — and win. <!-- SC_ON --> submitted by /u/klaasvanschelven (https://www.reddit.com/user/klaasvanschelven)
[link] (https://www.youtube.com/watch?v=S67A1WYiMZU&t) [comments] (https://www.reddit.com/r/programming/comments/1od1siq/race_to_the_root_cause_talk_at_pycon_nl_2025/)
https://www.reddit.com/r/programming/comments/1od1siq/race_to_the_root_cause_talk_at_pycon_nl_2025/
<!-- SC_OFF -->Examples include: Chained Exception Puzzle: Python’s “During handling of the above exception, another exception occurred” messages rarely make the real flow obvious. We’ll see how these stacktraces force you to piece together what actually happened. The Missing Curly Bracket: Sometimes Python blames a line with a with statement, even though no code runs there. Why does this happen? And what does it have to do with curly brackets? By the end, you’ll have a better feel for Python’s stacktraces, some new strategies for debugging faster, and at least one story to share the next time a stacktrace tries to trick you. You’ll walk away with sharper debugging instincts, some practical tricks, and maybe a laugh at Python’s expense. If you’ve ever felt outsmarted by a stacktrace, this is your chance to race to the root cause — and win. <!-- SC_ON --> submitted by /u/klaasvanschelven (https://www.reddit.com/user/klaasvanschelven)
[link] (https://www.youtube.com/watch?v=S67A1WYiMZU&t) [comments] (https://www.reddit.com/r/programming/comments/1od1siq/race_to_the_root_cause_talk_at_pycon_nl_2025/)
Streamed data transformation in JavaScript and Clojure via Iterators and Transducers
https://www.reddit.com/r/programming/comments/1od6fbb/streamed_data_transformation_in_javascript_and/
submitted by /u/roman01la (https://www.reddit.com/user/roman01la)
[link] (https://www.youtube.com/watch?v=KU4HnjTV9m8) [comments] (https://www.reddit.com/r/programming/comments/1od6fbb/streamed_data_transformation_in_javascript_and/)
https://www.reddit.com/r/programming/comments/1od6fbb/streamed_data_transformation_in_javascript_and/
submitted by /u/roman01la (https://www.reddit.com/user/roman01la)
[link] (https://www.youtube.com/watch?v=KU4HnjTV9m8) [comments] (https://www.reddit.com/r/programming/comments/1od6fbb/streamed_data_transformation_in_javascript_and/)
React Server Components with Rust: 12x faster P99 latency than Next.js
https://www.reddit.com/r/programming/comments/1od6vja/react_server_components_with_rust_12x_faster_p99/
<!-- SC_OFF -->I built Rari, a React framework with a Rust runtime. We just added proper app router support, SSR, and correct RSC semantics. The results: - 0.69ms avg response (3.8x faster than Next.js) - 20,226 req/sec throughput (10.5x higher) - 4ms P99 latency under load (12x faster) - 68% smaller bundles The architecture: server components by default, 'use client' for interactivity, true SSR from the Rust runtime. When your implementation matches React's design philosophy, performance follows naturally. Read the full story: https://ryanskinner.com/posts/the-rari-ssr-breakthrough-12x-faster-10x-higher-throughput-than-nextjs Try it: npm create rari-app@latest GitHub: https://github.com/rari-build/rari All benchmarks: https://github.com/rari-build/benchmarks <!-- SC_ON --> submitted by /u/BadDogDoug (https://www.reddit.com/user/BadDogDoug)
[link] (https://ryanskinner.com/posts/the-rari-ssr-breakthrough-12x-faster-10x-higher-throughput-than-nextjs) [comments] (https://www.reddit.com/r/programming/comments/1od6vja/react_server_components_with_rust_12x_faster_p99/)
https://www.reddit.com/r/programming/comments/1od6vja/react_server_components_with_rust_12x_faster_p99/
<!-- SC_OFF -->I built Rari, a React framework with a Rust runtime. We just added proper app router support, SSR, and correct RSC semantics. The results: - 0.69ms avg response (3.8x faster than Next.js) - 20,226 req/sec throughput (10.5x higher) - 4ms P99 latency under load (12x faster) - 68% smaller bundles The architecture: server components by default, 'use client' for interactivity, true SSR from the Rust runtime. When your implementation matches React's design philosophy, performance follows naturally. Read the full story: https://ryanskinner.com/posts/the-rari-ssr-breakthrough-12x-faster-10x-higher-throughput-than-nextjs Try it: npm create rari-app@latest GitHub: https://github.com/rari-build/rari All benchmarks: https://github.com/rari-build/benchmarks <!-- SC_ON --> submitted by /u/BadDogDoug (https://www.reddit.com/user/BadDogDoug)
[link] (https://ryanskinner.com/posts/the-rari-ssr-breakthrough-12x-faster-10x-higher-throughput-than-nextjs) [comments] (https://www.reddit.com/r/programming/comments/1od6vja/react_server_components_with_rust_12x_faster_p99/)