Native Android Application Development in Swift
https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/
<!-- SC_OFF -->Hi all, imike here. I just released Swift Stream IDE v1.17.0, which adds full native Android application development written entirely in Swift. That means you can now build Android apps without touching XML, Java, or Kotlin. Swift Stream IDE is an open-source VSCode extension that sets up a ready-to-use Swift development environment in Docker, supporting server-side, web, embedded, and now full Android development. With this release, you can create Android applications using familiar templates like Empty Activity, Basic Views (two fragments), or Navigation UI (tab bar), all in Swift. Under the hood, all projects are powered by SwifDroid, a framework I built to wrap the entire native Android app model. It handles the application lifecycle and manifest, activities and fragments, Android, AndroidX, Material, and Flexbox UI widgets, and even automatically wires Gradle dependencies. Supported SDKs are 28 to 35, and with Swift 6.3, it might go down (https://forums.swift.org/t/android-api-minimum-for-the-swift-sdk-for-android/82874) to 24+. Example UI code: ConstraintLayout { VStack { TextView("Hello from Swift!") .width(.matchParent) .height(.wrapContent) .textColor(.green) MaterialButton("Tap Me") .onClick { print("Button tapped!") } } .centerVertical() .leftToParent() .rightToParent() } The first time you create a project, make yourself a cup of tea/coffee. The IDE pulls the Swift toolchain, Android SDK, and NDK, and caches them in Docker volumes. After that, new projects are created instantly. The first build compiles Swift, generates a full Android project (ready to open in Android Studio), and creates a Gradle wrapper. After that, builds take just a few seconds. Once Swift is compiled, you can simply open the Application folder in Android Studio and hit Run or Restart to see your changes. All the necessary files from Swift Stream IDE are already in place, so iteration is fast and seamless. This is the first public release. Android is huge, and there are still widgets in progress, but the system is real and usable today. Documentation: https://docs.swifdroid.com/app/ <!-- SC_ON --> submitted by /u/imike3049 (https://www.reddit.com/user/imike3049)
[link] (https://docs.swifdroid.com/app/) [comments] (https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/)
https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/
<!-- SC_OFF -->Hi all, imike here. I just released Swift Stream IDE v1.17.0, which adds full native Android application development written entirely in Swift. That means you can now build Android apps without touching XML, Java, or Kotlin. Swift Stream IDE is an open-source VSCode extension that sets up a ready-to-use Swift development environment in Docker, supporting server-side, web, embedded, and now full Android development. With this release, you can create Android applications using familiar templates like Empty Activity, Basic Views (two fragments), or Navigation UI (tab bar), all in Swift. Under the hood, all projects are powered by SwifDroid, a framework I built to wrap the entire native Android app model. It handles the application lifecycle and manifest, activities and fragments, Android, AndroidX, Material, and Flexbox UI widgets, and even automatically wires Gradle dependencies. Supported SDKs are 28 to 35, and with Swift 6.3, it might go down (https://forums.swift.org/t/android-api-minimum-for-the-swift-sdk-for-android/82874) to 24+. Example UI code: ConstraintLayout { VStack { TextView("Hello from Swift!") .width(.matchParent) .height(.wrapContent) .textColor(.green) MaterialButton("Tap Me") .onClick { print("Button tapped!") } } .centerVertical() .leftToParent() .rightToParent() } The first time you create a project, make yourself a cup of tea/coffee. The IDE pulls the Swift toolchain, Android SDK, and NDK, and caches them in Docker volumes. After that, new projects are created instantly. The first build compiles Swift, generates a full Android project (ready to open in Android Studio), and creates a Gradle wrapper. After that, builds take just a few seconds. Once Swift is compiled, you can simply open the Application folder in Android Studio and hit Run or Restart to see your changes. All the necessary files from Swift Stream IDE are already in place, so iteration is fast and seamless. This is the first public release. Android is huge, and there are still widgets in progress, but the system is real and usable today. Documentation: https://docs.swifdroid.com/app/ <!-- SC_ON --> submitted by /u/imike3049 (https://www.reddit.com/user/imike3049)
[link] (https://docs.swifdroid.com/app/) [comments] (https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/)
Who Owns the Memory? Part 1: What is an Object?
https://www.reddit.com/r/programming/comments/1q2y2hc/who_owns_the_memory_part_1_what_is_an_object/
submitted by /u/Luke_Fleed (https://www.reddit.com/user/Luke_Fleed)
[link] (https://lukefleed.xyz/posts/who-owns-the-memory-pt1/) [comments] (https://www.reddit.com/r/programming/comments/1q2y2hc/who_owns_the_memory_part_1_what_is_an_object/)
https://www.reddit.com/r/programming/comments/1q2y2hc/who_owns_the_memory_part_1_what_is_an_object/
submitted by /u/Luke_Fleed (https://www.reddit.com/user/Luke_Fleed)
[link] (https://lukefleed.xyz/posts/who-owns-the-memory-pt1/) [comments] (https://www.reddit.com/r/programming/comments/1q2y2hc/who_owns_the_memory_part_1_what_is_an_object/)
Bold December Summary (text editor with lsp and dap support)
https://www.reddit.com/r/programming/comments/1q30n5l/bold_december_summary_text_editor_with_lsp_and/
submitted by /u/levodelellis (https://www.reddit.com/user/levodelellis)
[link] (https://bold-edit.com/devlog/25-12-summary.html) [comments] (https://www.reddit.com/r/programming/comments/1q30n5l/bold_december_summary_text_editor_with_lsp_and/)
https://www.reddit.com/r/programming/comments/1q30n5l/bold_december_summary_text_editor_with_lsp_and/
submitted by /u/levodelellis (https://www.reddit.com/user/levodelellis)
[link] (https://bold-edit.com/devlog/25-12-summary.html) [comments] (https://www.reddit.com/r/programming/comments/1q30n5l/bold_december_summary_text_editor_with_lsp_and/)
Naughty Words Every Programmer Should Know - a free eBook that uses NSFW Acronyms as mnemonic devices
https://www.reddit.com/r/programming/comments/1q31uq9/naughty_words_every_programmer_should_know_a_free/
submitted by /u/Mrsomud007 (https://www.reddit.com/user/Mrsomud007)
[link] (http://filipristovic.com/) [comments] (https://www.reddit.com/r/programming/comments/1q31uq9/naughty_words_every_programmer_should_know_a_free/)
https://www.reddit.com/r/programming/comments/1q31uq9/naughty_words_every_programmer_should_know_a_free/
submitted by /u/Mrsomud007 (https://www.reddit.com/user/Mrsomud007)
[link] (http://filipristovic.com/) [comments] (https://www.reddit.com/r/programming/comments/1q31uq9/naughty_words_every_programmer_should_know_a_free/)
Software craftsmanship is dead
https://www.reddit.com/r/programming/comments/1q3ed1a/software_craftsmanship_is_dead/
submitted by /u/R2_SWE2 (https://www.reddit.com/user/R2_SWE2)
[link] (https://www.pcloadletter.dev/blog/craftsmanship-is-dead/) [comments] (https://www.reddit.com/r/programming/comments/1q3ed1a/software_craftsmanship_is_dead/)
https://www.reddit.com/r/programming/comments/1q3ed1a/software_craftsmanship_is_dead/
submitted by /u/R2_SWE2 (https://www.reddit.com/user/R2_SWE2)
[link] (https://www.pcloadletter.dev/blog/craftsmanship-is-dead/) [comments] (https://www.reddit.com/r/programming/comments/1q3ed1a/software_craftsmanship_is_dead/)
Stackoverflow: Questions asked per month over time.
https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/
submitted by /u/lelanthran (https://www.reddit.com/user/lelanthran)
[link] (https://data.stackexchange.com/stackoverflow/query/1926661#graph) [comments] (https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/)
https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/
submitted by /u/lelanthran (https://www.reddit.com/user/lelanthran)
[link] (https://data.stackexchange.com/stackoverflow/query/1926661#graph) [comments] (https://www.reddit.com/r/programming/comments/1q3l83g/stackoverflow_questions_asked_per_month_over_time/)
21 Lessons From 14 Years at Google
https://www.reddit.com/r/programming/comments/1q41c87/21_lessons_from_14_years_at_google/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://addyosmani.com/blog/21-lessons/) [comments] (https://www.reddit.com/r/programming/comments/1q41c87/21_lessons_from_14_years_at_google/)
https://www.reddit.com/r/programming/comments/1q41c87/21_lessons_from_14_years_at_google/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://addyosmani.com/blog/21-lessons/) [comments] (https://www.reddit.com/r/programming/comments/1q41c87/21_lessons_from_14_years_at_google/)
Building a Monitoring System for Jobs That Never Ran
https://www.reddit.com/r/programming/comments/1q4dsko/building_a_monitoring_system_for_jobs_that_never/
<!-- SC_OFF -->Most monitoring systems tracks success and failure, but the hardest problems come from jobs that never ran at all. The article covers the architecture, the tricky parts such as detecting jobs that never ran, and some lessons learned along the way. <!-- SC_ON --> submitted by /u/Mythikos (https://www.reddit.com/user/Mythikos)
[link] (https://www.vincentlakatos.com/blog/building-a-monitoring-system-that-catches-silent-failures/) [comments] (https://www.reddit.com/r/programming/comments/1q4dsko/building_a_monitoring_system_for_jobs_that_never/)
https://www.reddit.com/r/programming/comments/1q4dsko/building_a_monitoring_system_for_jobs_that_never/
<!-- SC_OFF -->Most monitoring systems tracks success and failure, but the hardest problems come from jobs that never ran at all. The article covers the architecture, the tricky parts such as detecting jobs that never ran, and some lessons learned along the way. <!-- SC_ON --> submitted by /u/Mythikos (https://www.reddit.com/user/Mythikos)
[link] (https://www.vincentlakatos.com/blog/building-a-monitoring-system-that-catches-silent-failures/) [comments] (https://www.reddit.com/r/programming/comments/1q4dsko/building_a_monitoring_system_for_jobs_that_never/)
Managing database schema changes for beginners
https://www.reddit.com/r/programming/comments/1q4gvqb/managing_database_schema_changes_for_beginners/
submitted by /u/tanin47 (https://www.reddit.com/user/tanin47)
[link] (https://medium.com/@tanin_90098/the-basics-of-managing-database-schema-changes-fc31b4264297) [comments] (https://www.reddit.com/r/programming/comments/1q4gvqb/managing_database_schema_changes_for_beginners/)
https://www.reddit.com/r/programming/comments/1q4gvqb/managing_database_schema_changes_for_beginners/
submitted by /u/tanin47 (https://www.reddit.com/user/tanin47)
[link] (https://medium.com/@tanin_90098/the-basics-of-managing-database-schema-changes-fc31b4264297) [comments] (https://www.reddit.com/r/programming/comments/1q4gvqb/managing_database_schema_changes_for_beginners/)
Databases in 2025: A Year in Review
https://www.reddit.com/r/programming/comments/1q4jrk4/databases_in_2025_a_year_in_review/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://www.cs.cmu.edu/~pavlo/blog/2026/01/2025-databases-retrospective.html) [comments] (https://www.reddit.com/r/programming/comments/1q4jrk4/databases_in_2025_a_year_in_review/)
https://www.reddit.com/r/programming/comments/1q4jrk4/databases_in_2025_a_year_in_review/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://www.cs.cmu.edu/~pavlo/blog/2026/01/2025-databases-retrospective.html) [comments] (https://www.reddit.com/r/programming/comments/1q4jrk4/databases_in_2025_a_year_in_review/)
Gossip Gloomers in Rust
https://www.reddit.com/r/programming/comments/1q4jx47/gossip_gloomers_in_rust/
submitted by /u/glassycrow (https://www.reddit.com/user/glassycrow)
[link] (https://pureframes.eu/blog/gossip-gloomers) [comments] (https://www.reddit.com/r/programming/comments/1q4jx47/gossip_gloomers_in_rust/)
https://www.reddit.com/r/programming/comments/1q4jx47/gossip_gloomers_in_rust/
submitted by /u/glassycrow (https://www.reddit.com/user/glassycrow)
[link] (https://pureframes.eu/blog/gossip-gloomers) [comments] (https://www.reddit.com/r/programming/comments/1q4jx47/gossip_gloomers_in_rust/)
Simple and efficient visualization of embedded system events: Using VCD viewers and FreeRTOS trace
https://www.reddit.com/r/programming/comments/1q4l6jy/simple_and_efficient_visualization_of_embedded/
<!-- SC_OFF -->Relying on printf or simple breakpoints for real-time embedded debugging is often like flying blind - especially when dealing with complex timing and RTOS scheduling. The RTEdbg toolkit (https://github.com/RTEdbg/RTEdbg) has been extended to solve this, adding VCD-based (https://en.wikipedia.org/wiki/Value_change_dump) event and data visualization, native FreeRTOS trace support, and enhanced trace macros for deeper system insights. Because RTEdbg is open-source, it is accessible for any project, regardless of budget. It supports application and RTOS event visualization (see FreeRTOS trace demo (https://github.com/RTEdbg/FreeRTOS-trace-demo)) and allows for flexible data export and custom visualization—you can see it in action here: Various Data Export and Visualization Possibilities (https://github.com/RTEdbg/RTEdbg/blob/master/Views.md). <!-- SC_ON --> submitted by /u/BrankoP88 (https://www.reddit.com/user/BrankoP88)
[link] (https://github.com/RTEdbg/RTEdbg) [comments] (https://www.reddit.com/r/programming/comments/1q4l6jy/simple_and_efficient_visualization_of_embedded/)
https://www.reddit.com/r/programming/comments/1q4l6jy/simple_and_efficient_visualization_of_embedded/
<!-- SC_OFF -->Relying on printf or simple breakpoints for real-time embedded debugging is often like flying blind - especially when dealing with complex timing and RTOS scheduling. The RTEdbg toolkit (https://github.com/RTEdbg/RTEdbg) has been extended to solve this, adding VCD-based (https://en.wikipedia.org/wiki/Value_change_dump) event and data visualization, native FreeRTOS trace support, and enhanced trace macros for deeper system insights. Because RTEdbg is open-source, it is accessible for any project, regardless of budget. It supports application and RTOS event visualization (see FreeRTOS trace demo (https://github.com/RTEdbg/FreeRTOS-trace-demo)) and allows for flexible data export and custom visualization—you can see it in action here: Various Data Export and Visualization Possibilities (https://github.com/RTEdbg/RTEdbg/blob/master/Views.md). <!-- SC_ON --> submitted by /u/BrankoP88 (https://www.reddit.com/user/BrankoP88)
[link] (https://github.com/RTEdbg/RTEdbg) [comments] (https://www.reddit.com/r/programming/comments/1q4l6jy/simple_and_efficient_visualization_of_embedded/)
Functors, Applicatives, and Monads: The Scary Words You Already Understand
https://www.reddit.com/r/programming/comments/1q4lzac/functors_applicatives_and_monads_the_scary_words/
<!-- SC_OFF -->Do you generally agree with this? It's a tough topic to teach simply, and there's always tradeoffs between accuracy and simplicity... Open to suggestions for improvement! Thanks :) <!-- SC_ON --> submitted by /u/cekrem (https://www.reddit.com/user/cekrem)
[link] (https://cekrem.github.io/posts/functors-applicatives-monads-elm/) [comments] (https://www.reddit.com/r/programming/comments/1q4lzac/functors_applicatives_and_monads_the_scary_words/)
https://www.reddit.com/r/programming/comments/1q4lzac/functors_applicatives_and_monads_the_scary_words/
<!-- SC_OFF -->Do you generally agree with this? It's a tough topic to teach simply, and there's always tradeoffs between accuracy and simplicity... Open to suggestions for improvement! Thanks :) <!-- SC_ON --> submitted by /u/cekrem (https://www.reddit.com/user/cekrem)
[link] (https://cekrem.github.io/posts/functors-applicatives-monads-elm/) [comments] (https://www.reddit.com/r/programming/comments/1q4lzac/functors_applicatives_and_monads_the_scary_words/)
How Speeding Up RL Led to Pufferlib (4.8K Stars) | Interview with Joseph Suarez
https://www.reddit.com/r/programming/comments/1q4meae/how_speeding_up_rl_led_to_pufferlib_48k_stars/
submitted by /u/research_pie (https://www.reddit.com/user/research_pie)
[link] (https://youtu.be/Sirpfci74zU) [comments] (https://www.reddit.com/r/programming/comments/1q4meae/how_speeding_up_rl_led_to_pufferlib_48k_stars/)
https://www.reddit.com/r/programming/comments/1q4meae/how_speeding_up_rl_led_to_pufferlib_48k_stars/
submitted by /u/research_pie (https://www.reddit.com/user/research_pie)
[link] (https://youtu.be/Sirpfci74zU) [comments] (https://www.reddit.com/r/programming/comments/1q4meae/how_speeding_up_rl_led_to_pufferlib_48k_stars/)
The Data Triangle
https://www.reddit.com/r/programming/comments/1q4o3o3/the_data_triangle/
submitted by /u/benlorantfy (https://www.reddit.com/user/benlorantfy)
[link] (https://www.benlorantfy.com/blog/the-data-triangle-and-nestjs-zod-v5) [comments] (https://www.reddit.com/r/programming/comments/1q4o3o3/the_data_triangle/)
https://www.reddit.com/r/programming/comments/1q4o3o3/the_data_triangle/
submitted by /u/benlorantfy (https://www.reddit.com/user/benlorantfy)
[link] (https://www.benlorantfy.com/blog/the-data-triangle-and-nestjs-zod-v5) [comments] (https://www.reddit.com/r/programming/comments/1q4o3o3/the_data_triangle/)
Common Architectures: Monolithic, Distributed, and Serverless
https://www.reddit.com/r/programming/comments/1q4opun/common_architectures_monolithic_distributed_and/
submitted by /u/stmoreau (https://www.reddit.com/user/stmoreau)
[link] (https://www.systemdesignbutsimple.com/p/common-architectures-monolithic-distributed) [comments] (https://www.reddit.com/r/programming/comments/1q4opun/common_architectures_monolithic_distributed_and/)
https://www.reddit.com/r/programming/comments/1q4opun/common_architectures_monolithic_distributed_and/
submitted by /u/stmoreau (https://www.reddit.com/user/stmoreau)
[link] (https://www.systemdesignbutsimple.com/p/common-architectures-monolithic-distributed) [comments] (https://www.reddit.com/r/programming/comments/1q4opun/common_architectures_monolithic_distributed_and/)
Who Owns the Memory? Part 3: How Big Is your Type?
https://www.reddit.com/r/programming/comments/1q4qdxa/who_owns_the_memory_part_3_how_big_is_your_type/
submitted by /u/Luke_Fleed (https://www.reddit.com/user/Luke_Fleed)
[link] (https://lukefleed.xyz/posts/who-owns-the-memory-pt3/) [comments] (https://www.reddit.com/r/programming/comments/1q4qdxa/who_owns_the_memory_part_3_how_big_is_your_type/)
https://www.reddit.com/r/programming/comments/1q4qdxa/who_owns_the_memory_part_3_how_big_is_your_type/
submitted by /u/Luke_Fleed (https://www.reddit.com/user/Luke_Fleed)
[link] (https://lukefleed.xyz/posts/who-owns-the-memory-pt3/) [comments] (https://www.reddit.com/r/programming/comments/1q4qdxa/who_owns_the_memory_part_3_how_big_is_your_type/)
Rebuilding Event-Driven Read Models in a safe and resilient way
https://www.reddit.com/r/programming/comments/1q4s31j/rebuilding_eventdriven_read_models_in_a_safe_and/
submitted by /u/Adventurous-Salt8514 (https://www.reddit.com/user/Adventurous-Salt8514)
[link] (https://event-driven.io/en/rebuilding_event_driven_read_models/) [comments] (https://www.reddit.com/r/programming/comments/1q4s31j/rebuilding_eventdriven_read_models_in_a_safe_and/)
https://www.reddit.com/r/programming/comments/1q4s31j/rebuilding_eventdriven_read_models_in_a_safe_and/
submitted by /u/Adventurous-Salt8514 (https://www.reddit.com/user/Adventurous-Salt8514)
[link] (https://event-driven.io/en/rebuilding_event_driven_read_models/) [comments] (https://www.reddit.com/r/programming/comments/1q4s31j/rebuilding_eventdriven_read_models_in_a_safe_and/)
Easy (Horizontal Scrollbar) Fixes for Your Blog CSS
https://www.reddit.com/r/programming/comments/1q4t0gz/easy_horizontal_scrollbar_fixes_for_your_blog_css/
submitted by /u/aartaka (https://www.reddit.com/user/aartaka)
[link] (https://aartaka.me/easy-fixes.html) [comments] (https://www.reddit.com/r/programming/comments/1q4t0gz/easy_horizontal_scrollbar_fixes_for_your_blog_css/)
https://www.reddit.com/r/programming/comments/1q4t0gz/easy_horizontal_scrollbar_fixes_for_your_blog_css/
submitted by /u/aartaka (https://www.reddit.com/user/aartaka)
[link] (https://aartaka.me/easy-fixes.html) [comments] (https://www.reddit.com/r/programming/comments/1q4t0gz/easy_horizontal_scrollbar_fixes_for_your_blog_css/)
Clean Code vs. A Philosophy Of Software Design
https://www.reddit.com/r/programming/comments/1q4v7rf/clean_code_vs_a_philosophy_of_software_design/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://github.com/johnousterhout/aposd-vs-clean-code) [comments] (https://www.reddit.com/r/programming/comments/1q4v7rf/clean_code_vs_a_philosophy_of_software_design/)
https://www.reddit.com/r/programming/comments/1q4v7rf/clean_code_vs_a_philosophy_of_software_design/
submitted by /u/iamkeyur (https://www.reddit.com/user/iamkeyur)
[link] (https://github.com/johnousterhout/aposd-vs-clean-code) [comments] (https://www.reddit.com/r/programming/comments/1q4v7rf/clean_code_vs_a_philosophy_of_software_design/)
It's a horse!
https://www.reddit.com/r/programming/comments/1q4y82s/its_a_horse/
submitted by /u/justpablo (https://www.reddit.com/user/justpablo)
[link] (https://polmuz.github.io/2026/01/04/its-a-horse.html) [comments] (https://www.reddit.com/r/programming/comments/1q4y82s/its_a_horse/)
https://www.reddit.com/r/programming/comments/1q4y82s/its_a_horse/
submitted by /u/justpablo (https://www.reddit.com/user/justpablo)
[link] (https://polmuz.github.io/2026/01/04/its-a-horse.html) [comments] (https://www.reddit.com/r/programming/comments/1q4y82s/its_a_horse/)