New HTTP QUERY Method
https://www.reddit.com/r/programming/comments/1udwfsp/new_http_query_method/
<!-- SC_OFF -->What do you think about the new HTTP Query method? <!-- SC_ON --> submitted by /u/Perfect-Scale902 (https://www.reddit.com/user/Perfect-Scale902)
[link] (https://datatracker.ietf.org/doc/rfc10008/) [comments] (https://www.reddit.com/r/programming/comments/1udwfsp/new_http_query_method/)
https://www.reddit.com/r/programming/comments/1udwfsp/new_http_query_method/
<!-- SC_OFF -->What do you think about the new HTTP Query method? <!-- SC_ON --> submitted by /u/Perfect-Scale902 (https://www.reddit.com/user/Perfect-Scale902)
[link] (https://datatracker.ietf.org/doc/rfc10008/) [comments] (https://www.reddit.com/r/programming/comments/1udwfsp/new_http_query_method/)
Apache Pulsar 5.0.0-M1: introducing Scalable Topics — topics that split/merge themselves, no partition count required
https://www.reddit.com/r/programming/comments/1udxdd5/apache_pulsar_500m1_introducing_scalable_topics/
submitted by /u/mmerli (https://www.reddit.com/user/mmerli)
[link] (https://pulsar.apache.org/blog/2026/06/23/announcing-apache-pulsar-5-0-m1/) [comments] (https://www.reddit.com/r/programming/comments/1udxdd5/apache_pulsar_500m1_introducing_scalable_topics/)
https://www.reddit.com/r/programming/comments/1udxdd5/apache_pulsar_500m1_introducing_scalable_topics/
submitted by /u/mmerli (https://www.reddit.com/user/mmerli)
[link] (https://pulsar.apache.org/blog/2026/06/23/announcing-apache-pulsar-5-0-m1/) [comments] (https://www.reddit.com/r/programming/comments/1udxdd5/apache_pulsar_500m1_introducing_scalable_topics/)
[video] WebSockets at Scale: System Design
https://www.reddit.com/r/programming/comments/1ue8voi/video_websockets_at_scale_system_design/
submitted by /u/lucian-12 (https://www.reddit.com/user/lucian-12)
[link] (https://youtu.be/ASF6snvxZUE) [comments] (https://www.reddit.com/r/programming/comments/1ue8voi/video_websockets_at_scale_system_design/)
https://www.reddit.com/r/programming/comments/1ue8voi/video_websockets_at_scale_system_design/
submitted by /u/lucian-12 (https://www.reddit.com/user/lucian-12)
[link] (https://youtu.be/ASF6snvxZUE) [comments] (https://www.reddit.com/r/programming/comments/1ue8voi/video_websockets_at_scale_system_design/)
An opinionated (and mainly correct) guide to naming
https://www.reddit.com/r/programming/comments/1ue916q/an_opinionated_and_mainly_correct_guide_to_naming/
submitted by /u/nephrenka (https://www.reddit.com/user/nephrenka)
[link] (https://adamtornhill.substack.com/p/an-opinionated-and-mainly-correct) [comments] (https://www.reddit.com/r/programming/comments/1ue916q/an_opinionated_and_mainly_correct_guide_to_naming/)
https://www.reddit.com/r/programming/comments/1ue916q/an_opinionated_and_mainly_correct_guide_to_naming/
submitted by /u/nephrenka (https://www.reddit.com/user/nephrenka)
[link] (https://adamtornhill.substack.com/p/an-opinionated-and-mainly-correct) [comments] (https://www.reddit.com/r/programming/comments/1ue916q/an_opinionated_and_mainly_correct_guide_to_naming/)
How Grafana Alloy Builds and Runs Its Component Graph
https://www.reddit.com/r/programming/comments/1uebi9d/how_grafana_alloy_builds_and_runs_its_component/
<!-- SC_OFF -->I spent some time reading Grafana Alloy’s source code to understand how it loads configuration, builds a dependency graph, evaluates components, and runs them. I wrote a short breakdown of what I learned, mainly focused on the runtime/controller, loader, scheduler, services, and component lifecycle. It is not a complete deep dive into the whole project, but more of a source-code reading note from exploring a real production Go codebase. Feedback is welcome, especially from people familiar with observability systems or large Go codebases. <!-- SC_ON --> submitted by /u/am0123 (https://www.reddit.com/user/am0123)
[link] (https://abdellani.dev/posts/2026-06-23-how-grafana-alloy-builds-and-runs-its-component-graph/) [comments] (https://www.reddit.com/r/programming/comments/1uebi9d/how_grafana_alloy_builds_and_runs_its_component/)
https://www.reddit.com/r/programming/comments/1uebi9d/how_grafana_alloy_builds_and_runs_its_component/
<!-- SC_OFF -->I spent some time reading Grafana Alloy’s source code to understand how it loads configuration, builds a dependency graph, evaluates components, and runs them. I wrote a short breakdown of what I learned, mainly focused on the runtime/controller, loader, scheduler, services, and component lifecycle. It is not a complete deep dive into the whole project, but more of a source-code reading note from exploring a real production Go codebase. Feedback is welcome, especially from people familiar with observability systems or large Go codebases. <!-- SC_ON --> submitted by /u/am0123 (https://www.reddit.com/user/am0123)
[link] (https://abdellani.dev/posts/2026-06-23-how-grafana-alloy-builds-and-runs-its-component-graph/) [comments] (https://www.reddit.com/r/programming/comments/1uebi9d/how_grafana_alloy_builds_and_runs_its_component/)
A batch job, in The Elm Architecture
https://www.reddit.com/r/programming/comments/1ueboqi/a_batch_job_in_the_elm_architecture/
submitted by /u/cekrem (https://www.reddit.com/user/cekrem)
[link] (https://cekrem.github.io/posts/elm-run-batch-job/) [comments] (https://www.reddit.com/r/programming/comments/1ueboqi/a_batch_job_in_the_elm_architecture/)
https://www.reddit.com/r/programming/comments/1ueboqi/a_batch_job_in_the_elm_architecture/
submitted by /u/cekrem (https://www.reddit.com/user/cekrem)
[link] (https://cekrem.github.io/posts/elm-run-batch-job/) [comments] (https://www.reddit.com/r/programming/comments/1ueboqi/a_batch_job_in_the_elm_architecture/)
The Evolution of User Interfaces • Ken Pfeuffer
https://www.reddit.com/r/programming/comments/1uebttq/the_evolution_of_user_interfaces_ken_pfeuffer/
<!-- SC_OFF -->Every generation gets a new interface: ⌨️ Keyboard
🖱️ Mouse
📱 Touchscreen What's next? <!-- SC_ON --> submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/c0oewpwkwOg?list=PLEx5khR4g7PINwOsYrkwz3lTTJUYoXC53) [comments] (https://www.reddit.com/r/programming/comments/1uebttq/the_evolution_of_user_interfaces_ken_pfeuffer/)
https://www.reddit.com/r/programming/comments/1uebttq/the_evolution_of_user_interfaces_ken_pfeuffer/
<!-- SC_OFF -->Every generation gets a new interface: ⌨️ Keyboard
🖱️ Mouse
📱 Touchscreen What's next? <!-- SC_ON --> submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/c0oewpwkwOg?list=PLEx5khR4g7PINwOsYrkwz3lTTJUYoXC53) [comments] (https://www.reddit.com/r/programming/comments/1uebttq/the_evolution_of_user_interfaces_ken_pfeuffer/)
Measuring cache misses on macOS with Instruments
https://www.reddit.com/r/programming/comments/1uecln7/measuring_cache_misses_on_macos_with_instruments/
<!-- SC_OFF -->I couldn't find many resources online that showed how to see cache misses on macOS. I thought I'd learn a bit about Instruments, throw some toy problems at it, and write about the experience in a blog post. These toy examples - iterating sequentially then randomly, summing elements in a matrix, naive vs tiled matmul and iterating AoS vs SoA - are great to see some real numbers from L1 data cache misses, but they're far away from real programming problems. What's your experience using tools like Instruments/perf/cachegrind to actually optimize an algorithm? Is it ever needed to measure this at the hardware counter level or can you get away with intuition about the size of your data structure, how it's been accessed and using basic timers? <!-- SC_ON --> submitted by /u/markuzo1 (https://www.reddit.com/user/markuzo1)
[link] (https://www.markuzo.me/2026/06/24/caching-profiling-macos.html) [comments] (https://www.reddit.com/r/programming/comments/1uecln7/measuring_cache_misses_on_macos_with_instruments/)
https://www.reddit.com/r/programming/comments/1uecln7/measuring_cache_misses_on_macos_with_instruments/
<!-- SC_OFF -->I couldn't find many resources online that showed how to see cache misses on macOS. I thought I'd learn a bit about Instruments, throw some toy problems at it, and write about the experience in a blog post. These toy examples - iterating sequentially then randomly, summing elements in a matrix, naive vs tiled matmul and iterating AoS vs SoA - are great to see some real numbers from L1 data cache misses, but they're far away from real programming problems. What's your experience using tools like Instruments/perf/cachegrind to actually optimize an algorithm? Is it ever needed to measure this at the hardware counter level or can you get away with intuition about the size of your data structure, how it's been accessed and using basic timers? <!-- SC_ON --> submitted by /u/markuzo1 (https://www.reddit.com/user/markuzo1)
[link] (https://www.markuzo.me/2026/06/24/caching-profiling-macos.html) [comments] (https://www.reddit.com/r/programming/comments/1uecln7/measuring_cache_misses_on_macos_with_instruments/)
Running database drivers as sandboxed external processes (and why a HashMap insert was a security boundary)
https://www.reddit.com/r/programming/comments/1ueg71x/running_database_drivers_as_sandboxed_external/
submitted by /u/debba_ (https://www.reddit.com/user/debba_)
[link] (https://tabularis.dev/blog/database-drivers-as-external-processes?rdt) [comments] (https://www.reddit.com/r/programming/comments/1ueg71x/running_database_drivers_as_sandboxed_external/)
https://www.reddit.com/r/programming/comments/1ueg71x/running_database_drivers_as_sandboxed_external/
submitted by /u/debba_ (https://www.reddit.com/user/debba_)
[link] (https://tabularis.dev/blog/database-drivers-as-external-processes?rdt) [comments] (https://www.reddit.com/r/programming/comments/1ueg71x/running_database_drivers_as_sandboxed_external/)
Risks in Software Development: How to Match Your Caution to What’s Actually at Stake
https://www.reddit.com/r/programming/comments/1uegdl5/risks_in_software_development_how_to_match_your/
<!-- SC_OFF -->One of the most important blogs I have written in the last 25 years that most devs struggle with. <!-- SC_ON --> submitted by /u/watson_full_scale (https://www.reddit.com/user/watson_full_scale)
[link] (https://fullscale.io/blog/risks-in-software-development/) [comments] (https://www.reddit.com/r/programming/comments/1uegdl5/risks_in_software_development_how_to_match_your/)
https://www.reddit.com/r/programming/comments/1uegdl5/risks_in_software_development_how_to_match_your/
<!-- SC_OFF -->One of the most important blogs I have written in the last 25 years that most devs struggle with. <!-- SC_ON --> submitted by /u/watson_full_scale (https://www.reddit.com/user/watson_full_scale)
[link] (https://fullscale.io/blog/risks-in-software-development/) [comments] (https://www.reddit.com/r/programming/comments/1uegdl5/risks_in_software_development_how_to_match_your/)
How to Write an Effective Software Design Document
https://www.reddit.com/r/programming/comments/1uevttg/how_to_write_an_effective_software_design_document/
submitted by /u/mtlynch (https://www.reddit.com/user/mtlynch)
[link] (https://refactoringenglish.com/excerpts/write-an-effective-design-doc/) [comments] (https://www.reddit.com/r/programming/comments/1uevttg/how_to_write_an_effective_software_design_document/)
https://www.reddit.com/r/programming/comments/1uevttg/how_to_write_an_effective_software_design_document/
submitted by /u/mtlynch (https://www.reddit.com/user/mtlynch)
[link] (https://refactoringenglish.com/excerpts/write-an-effective-design-doc/) [comments] (https://www.reddit.com/r/programming/comments/1uevttg/how_to_write_an_effective_software_design_document/)
Best Simple System for Now • Daniel Terhorst-North
https://www.reddit.com/r/programming/comments/1uf8d96/best_simple_system_for_now_daniel_terhorstnorth/
<!-- SC_OFF -->Software teams often face a false choice: move fast and accumulate technical debt, or build the perfect system and miss the deadline. But there may be a third path, the Best Simple System for Now (BSSN). This session introduces a pragmatic yet principled approach to software design: systems that are as simple as possible but no simpler. You’ll learn how to design code that is robust, change-friendly, and fit for purpose, while avoiding both gold-plating and corner-cutting. Through practical examples, we explore how to manage complexity, embrace uncertainty, and make sound decisions using concepts like Cost of Delay and RAROC. <!-- SC_ON --> submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/u4Cv65F9DcY) [comments] (https://www.reddit.com/r/programming/comments/1uf8d96/best_simple_system_for_now_daniel_terhorstnorth/)
https://www.reddit.com/r/programming/comments/1uf8d96/best_simple_system_for_now_daniel_terhorstnorth/
<!-- SC_OFF -->Software teams often face a false choice: move fast and accumulate technical debt, or build the perfect system and miss the deadline. But there may be a third path, the Best Simple System for Now (BSSN). This session introduces a pragmatic yet principled approach to software design: systems that are as simple as possible but no simpler. You’ll learn how to design code that is robust, change-friendly, and fit for purpose, while avoiding both gold-plating and corner-cutting. Through practical examples, we explore how to manage complexity, embrace uncertainty, and make sound decisions using concepts like Cost of Delay and RAROC. <!-- SC_ON --> submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/u4Cv65F9DcY) [comments] (https://www.reddit.com/r/programming/comments/1uf8d96/best_simple_system_for_now_daniel_terhorstnorth/)
The dogma of entity-based Services and Repositories
https://www.reddit.com/r/programming/comments/1ufc0ki/the_dogma_of_entitybased_services_and_repositories/
<!-- SC_OFF -->Every day I see more projects where a layer-per-entity approach is created by default: UserService, UserRepository, OrderService, OrderRepository, and so on. My issue is not with layering itself, but with how these layers are used. In theory, a Service should represent application behavior: something that encapsulates real use cases or meaningful interactions with external systems (payments, emails, APIs, etc.). Something with enough significance to justify being isolated. A Repository, in theory, should exist when there is real complexity in data access: multiple data sources, non-trivial persistence logic, evolving storage mechanisms, etc. However, in practice, they often degrade into something else: services that simply delegate calls repositories that are thin wrappers around an ORM interfaces with no meaningful alternative implementation At that point, the abstraction starts to lose its purpose. Why not use the ORM directly when there is no real complexity to hide? Why do we default to intermediate layers that don’t truly represent either a service or a repository in their original sense? It often feels like they add files, indirection, and noise without improving clarity. I’m not saying these layers are inherently bad. I’m trying to understand why they are so often applied by default, even when they don’t serve their actual purpose. Does this approach really improve clarity, or does it just introduce unnecessary complexity? For example, instead of organizing code around generic services per model, we could structure it around explicit use cases for concrete system actions. These would still live within an application/service layer in the sense described by Fowler, but without forcing a generic ModelService structure for everything. The goal would be to design around intent rather than around structural templates—so the code reflects what the system does, not just how it is layered. <!-- SC_ON --> submitted by /u/Character-Method-720 (https://www.reddit.com/user/Character-Method-720)
[link] (https://martinfowler.com/eaaCatalog/serviceLayer.html) [comments] (https://www.reddit.com/r/programming/comments/1ufc0ki/the_dogma_of_entitybased_services_and_repositories/)
https://www.reddit.com/r/programming/comments/1ufc0ki/the_dogma_of_entitybased_services_and_repositories/
<!-- SC_OFF -->Every day I see more projects where a layer-per-entity approach is created by default: UserService, UserRepository, OrderService, OrderRepository, and so on. My issue is not with layering itself, but with how these layers are used. In theory, a Service should represent application behavior: something that encapsulates real use cases or meaningful interactions with external systems (payments, emails, APIs, etc.). Something with enough significance to justify being isolated. A Repository, in theory, should exist when there is real complexity in data access: multiple data sources, non-trivial persistence logic, evolving storage mechanisms, etc. However, in practice, they often degrade into something else: services that simply delegate calls repositories that are thin wrappers around an ORM interfaces with no meaningful alternative implementation At that point, the abstraction starts to lose its purpose. Why not use the ORM directly when there is no real complexity to hide? Why do we default to intermediate layers that don’t truly represent either a service or a repository in their original sense? It often feels like they add files, indirection, and noise without improving clarity. I’m not saying these layers are inherently bad. I’m trying to understand why they are so often applied by default, even when they don’t serve their actual purpose. Does this approach really improve clarity, or does it just introduce unnecessary complexity? For example, instead of organizing code around generic services per model, we could structure it around explicit use cases for concrete system actions. These would still live within an application/service layer in the sense described by Fowler, but without forcing a generic ModelService structure for everything. The goal would be to design around intent rather than around structural templates—so the code reflects what the system does, not just how it is layered. <!-- SC_ON --> submitted by /u/Character-Method-720 (https://www.reddit.com/user/Character-Method-720)
[link] (https://martinfowler.com/eaaCatalog/serviceLayer.html) [comments] (https://www.reddit.com/r/programming/comments/1ufc0ki/the_dogma_of_entitybased_services_and_repositories/)
Building an Entity Component System: Data Oriented Hierarchies
https://www.reddit.com/r/programming/comments/1ufcwid/building_an_entity_component_system_data_oriented/
<!-- SC_OFF -->Data Oriented Design (https://en.wikipedia.org/wiki/Data-oriented_design) is the practice of building code that's optimized for the hardware it runs on. Entity Component Systems help writing DOD-friendly code by laying out otherwise allocation-heavy game data in contiguous arrays. A challenge in gamedev however is that lots of game data is stored and accessed as hierarchies that change frequently, which makes them notoriously difficult to store as contiguous arrays. This article goes over a number of techniques an Entity Component System can use to integrate hierarchies with the core datamodel in a way that improves the performance of the ECS. Written mostly for gamedev, but also applies to other hierarchy-heavy applications, like UI. <!-- SC_ON --> submitted by /u/ajmmertens (https://www.reddit.com/user/ajmmertens)
[link] (https://ajmmertens.medium.com/building-an-ecs-data-oriented-hierarchies-62fb2847d100) [comments] (https://www.reddit.com/r/programming/comments/1ufcwid/building_an_entity_component_system_data_oriented/)
https://www.reddit.com/r/programming/comments/1ufcwid/building_an_entity_component_system_data_oriented/
<!-- SC_OFF -->Data Oriented Design (https://en.wikipedia.org/wiki/Data-oriented_design) is the practice of building code that's optimized for the hardware it runs on. Entity Component Systems help writing DOD-friendly code by laying out otherwise allocation-heavy game data in contiguous arrays. A challenge in gamedev however is that lots of game data is stored and accessed as hierarchies that change frequently, which makes them notoriously difficult to store as contiguous arrays. This article goes over a number of techniques an Entity Component System can use to integrate hierarchies with the core datamodel in a way that improves the performance of the ECS. Written mostly for gamedev, but also applies to other hierarchy-heavy applications, like UI. <!-- SC_ON --> submitted by /u/ajmmertens (https://www.reddit.com/user/ajmmertens)
[link] (https://ajmmertens.medium.com/building-an-ecs-data-oriented-hierarchies-62fb2847d100) [comments] (https://www.reddit.com/r/programming/comments/1ufcwid/building_an_entity_component_system_data_oriented/)
What ORMs have taught me: just learn SQL
https://www.reddit.com/r/programming/comments/1uo1w91/what_orms_have_taught_me_just_learn_sql/
submitted by /u/Either_Collection349 (https://www.reddit.com/user/Either_Collection349)
[link] (https://wozniak.ca/blog/2014/08/03/1/index.html) [comments] (https://www.reddit.com/r/programming/comments/1uo1w91/what_orms_have_taught_me_just_learn_sql/)
https://www.reddit.com/r/programming/comments/1uo1w91/what_orms_have_taught_me_just_learn_sql/
submitted by /u/Either_Collection349 (https://www.reddit.com/user/Either_Collection349)
[link] (https://wozniak.ca/blog/2014/08/03/1/index.html) [comments] (https://www.reddit.com/r/programming/comments/1uo1w91/what_orms_have_taught_me_just_learn_sql/)
Faster Builds with Elm 0.19.2
https://www.reddit.com/r/programming/comments/1uoumse/faster_builds_with_elm_0192/
submitted by /u/wheatBread (https://www.reddit.com/user/wheatBread)
[link] (https://elm-lang.org/news/faster-builds) [comments] (https://www.reddit.com/r/programming/comments/1uoumse/faster_builds_with_elm_0192/)
https://www.reddit.com/r/programming/comments/1uoumse/faster_builds_with_elm_0192/
submitted by /u/wheatBread (https://www.reddit.com/user/wheatBread)
[link] (https://elm-lang.org/news/faster-builds) [comments] (https://www.reddit.com/r/programming/comments/1uoumse/faster_builds_with_elm_0192/)
Addition by subtraction in software design
https://www.reddit.com/r/programming/comments/1uozd0o/addition_by_subtraction_in_software_design/
submitted by /u/Adventurous-Salt8514 (https://www.reddit.com/user/Adventurous-Salt8514)
[link] (https://www.architecture-weekly.com/p/addition-by-subtraction-in-software) [comments] (https://www.reddit.com/r/programming/comments/1uozd0o/addition_by_subtraction_in_software_design/)
https://www.reddit.com/r/programming/comments/1uozd0o/addition_by_subtraction_in_software_design/
submitted by /u/Adventurous-Salt8514 (https://www.reddit.com/user/Adventurous-Salt8514)
[link] (https://www.architecture-weekly.com/p/addition-by-subtraction-in-software) [comments] (https://www.reddit.com/r/programming/comments/1uozd0o/addition_by_subtraction_in_software_design/)
Girls Just Wanna Have Fast Wait-free MPMC Queues · Nahla
https://www.reddit.com/r/programming/comments/1up1c4a/girls_just_wanna_have_fast_waitfree_mpmc_queues/
submitted by /u/nee_- (https://www.reddit.com/user/nee_-)
[link] (https://nahla.dev/blog/waitfree_queue/) [comments] (https://www.reddit.com/r/programming/comments/1up1c4a/girls_just_wanna_have_fast_waitfree_mpmc_queues/)
https://www.reddit.com/r/programming/comments/1up1c4a/girls_just_wanna_have_fast_waitfree_mpmc_queues/
submitted by /u/nee_- (https://www.reddit.com/user/nee_-)
[link] (https://nahla.dev/blog/waitfree_queue/) [comments] (https://www.reddit.com/r/programming/comments/1up1c4a/girls_just_wanna_have_fast_waitfree_mpmc_queues/)
Odin 1.0 Announcement
https://www.reddit.com/r/programming/comments/1upmnop/odin_10_announcement/
submitted by /u/gingerbill (https://www.reddit.com/user/gingerbill)
[link] (https://www.youtube.com/watch?v=dLPAqXi9In0) [comments] (https://www.reddit.com/r/programming/comments/1upmnop/odin_10_announcement/)
https://www.reddit.com/r/programming/comments/1upmnop/odin_10_announcement/
submitted by /u/gingerbill (https://www.reddit.com/user/gingerbill)
[link] (https://www.youtube.com/watch?v=dLPAqXi9In0) [comments] (https://www.reddit.com/r/programming/comments/1upmnop/odin_10_announcement/)
Drunk Post: Things I’ve Learned as a Senior Engineer
https://www.reddit.com/r/programming/comments/1upo7f6/drunk_post_things_ive_learned_as_a_senior_engineer/
submitted by /u/fagnerbrack (https://www.reddit.com/user/fagnerbrack)
[link] (https://luminousmen.substack.com/p/drunk-post-things-ive-learned-as) [comments] (https://www.reddit.com/r/programming/comments/1upo7f6/drunk_post_things_ive_learned_as_a_senior_engineer/)
https://www.reddit.com/r/programming/comments/1upo7f6/drunk_post_things_ive_learned_as_a_senior_engineer/
submitted by /u/fagnerbrack (https://www.reddit.com/user/fagnerbrack)
[link] (https://luminousmen.substack.com/p/drunk-post-things-ive-learned-as) [comments] (https://www.reddit.com/r/programming/comments/1upo7f6/drunk_post_things_ive_learned_as_a_senior_engineer/)
The mask that compiles to nothing: how HotSpot's JIT learned to reason about bits
https://www.reddit.com/r/programming/comments/1ups1cn/the_mask_that_compiles_to_nothing_how_hotspots/
submitted by /u/j1897OS (https://www.reddit.com/user/j1897OS)
[link] (https://questdb.com/blog/jvm-jit-known-bits/) [comments] (https://www.reddit.com/r/programming/comments/1ups1cn/the_mask_that_compiles_to_nothing_how_hotspots/)
https://www.reddit.com/r/programming/comments/1ups1cn/the_mask_that_compiles_to_nothing_how_hotspots/
submitted by /u/j1897OS (https://www.reddit.com/user/j1897OS)
[link] (https://questdb.com/blog/jvm-jit-known-bits/) [comments] (https://www.reddit.com/r/programming/comments/1ups1cn/the_mask_that_compiles_to_nothing_how_hotspots/)