Lessons from changing tech stacks in real production apps.
https://www.reddit.com/r/programming/comments/1ldu45x/lessons_from_changing_tech_stacks_in_real/
<!-- SC_OFF -->I'm curious to hear from developers who have gone through this: What were the actual reasons that made your team switch technologies, frameworks, languages, or tools in a production app? Was it due to performance issues? Maintenance pain? Team experience? Scaling challenges? Ecosystem problems? Also, if you didn’t switch when you probably should have, what held you back? Would love to hear some war stories or insights to understand what really drives these decisions. <!-- SC_ON --> submitted by /u/Personal-Work4649 (https://www.reddit.com/user/Personal-Work4649)
[link] (https://medium.com/sharenowtech/front-end-architecture-making-rebuild-from-scratch-not-so-painful-7b2232dc1666) [comments] (https://www.reddit.com/r/programming/comments/1ldu45x/lessons_from_changing_tech_stacks_in_real/)
https://www.reddit.com/r/programming/comments/1ldu45x/lessons_from_changing_tech_stacks_in_real/
<!-- SC_OFF -->I'm curious to hear from developers who have gone through this: What were the actual reasons that made your team switch technologies, frameworks, languages, or tools in a production app? Was it due to performance issues? Maintenance pain? Team experience? Scaling challenges? Ecosystem problems? Also, if you didn’t switch when you probably should have, what held you back? Would love to hear some war stories or insights to understand what really drives these decisions. <!-- SC_ON --> submitted by /u/Personal-Work4649 (https://www.reddit.com/user/Personal-Work4649)
[link] (https://medium.com/sharenowtech/front-end-architecture-making-rebuild-from-scratch-not-so-painful-7b2232dc1666) [comments] (https://www.reddit.com/r/programming/comments/1ldu45x/lessons_from_changing_tech_stacks_in_real/)
Double-Entry Ledgers: The Missing Primitive in Modern Software
https://www.reddit.com/r/programming/comments/1lduuw1/doubleentry_ledgers_the_missing_primitive_in/
submitted by /u/pgr0ss (https://www.reddit.com/user/pgr0ss)
[link] (https://pgrs.net/2025/06/17/double-entry-ledgers-missing-primitive-in-modern-software/) [comments] (https://www.reddit.com/r/programming/comments/1lduuw1/doubleentry_ledgers_the_missing_primitive_in/)
https://www.reddit.com/r/programming/comments/1lduuw1/doubleentry_ledgers_the_missing_primitive_in/
submitted by /u/pgr0ss (https://www.reddit.com/user/pgr0ss)
[link] (https://pgrs.net/2025/06/17/double-entry-ledgers-missing-primitive-in-modern-software/) [comments] (https://www.reddit.com/r/programming/comments/1lduuw1/doubleentry_ledgers_the_missing_primitive_in/)
I wrote a compiler
https://www.reddit.com/r/programming/comments/1le4t7a/i_wrote_a_compiler/
submitted by /u/azhenley (https://www.reddit.com/user/azhenley)
[link] (https://blog.singleton.io/posts/2021-01-31-i-wrote-a-compiler/) [comments] (https://www.reddit.com/r/programming/comments/1le4t7a/i_wrote_a_compiler/)
https://www.reddit.com/r/programming/comments/1le4t7a/i_wrote_a_compiler/
submitted by /u/azhenley (https://www.reddit.com/user/azhenley)
[link] (https://blog.singleton.io/posts/2021-01-31-i-wrote-a-compiler/) [comments] (https://www.reddit.com/r/programming/comments/1le4t7a/i_wrote_a_compiler/)
"Yes, A.I. still sucks at coding in some cases — For now…"Article in AI Advances, 17-Jun-2025
https://www.reddit.com/r/programming/comments/1le980t/yes_ai_still_sucks_at_coding_in_some_cases_for/
<!-- SC_OFF -->Summary: Testing the limits of LLMs in code gerenation for Raspberry Pi Pico PIO assembly, as well as an example of how we design modern CPUs microcodes. If you work in these fields, your job is still pretty much secured against AI for many years... <!-- SC_ON --> submitted by /u/xgeorgio_gr (https://www.reddit.com/user/xgeorgio_gr)
[link] (https://ai.gopubby.com/yes-a-i-still-sucks-at-coding-in-some-cases-for-now-828a0fc17ada) [comments] (https://www.reddit.com/r/programming/comments/1le980t/yes_ai_still_sucks_at_coding_in_some_cases_for/)
https://www.reddit.com/r/programming/comments/1le980t/yes_ai_still_sucks_at_coding_in_some_cases_for/
<!-- SC_OFF -->Summary: Testing the limits of LLMs in code gerenation for Raspberry Pi Pico PIO assembly, as well as an example of how we design modern CPUs microcodes. If you work in these fields, your job is still pretty much secured against AI for many years... <!-- SC_ON --> submitted by /u/xgeorgio_gr (https://www.reddit.com/user/xgeorgio_gr)
[link] (https://ai.gopubby.com/yes-a-i-still-sucks-at-coding-in-some-cases-for-now-828a0fc17ada) [comments] (https://www.reddit.com/r/programming/comments/1le980t/yes_ai_still_sucks_at_coding_in_some_cases_for/)
Data Oriented Design, Region-Based Memory Management, and Security
https://www.reddit.com/r/programming/comments/1le9yyi/data_oriented_design_regionbased_memory/
<!-- SC_OFF -->Hello, the attached devlog covers a concept I have seen quite a bit from (game) developers enthusiastic about data-oriented design, which is region-based memory management. An example of this pattern is a program allocating a very large memory region on the heap and then placing data in the region using normal integers, effectively using them as offsets to refer to the location of data within the large region. While it certainly seems fair that such techniques have the potential to make programs more cache-efficient and space-efficient, and even reduce bugs when done right, I am curious to hear some opinions on whether this pattern could be considered a potential cybersecurity hazard. On the one hand, DOD seems to offer a lot of benefits as a programming paradigm, but I wonder whether there is merit to saying that the extremes of hand-rolled memory management could start to be problematic in the sense that you lose out on both the hardware-level and kernel-level security features that are designed for regular pointers. For applications that are more concerned with security and ease of development than aggressively minimizing instruction count (which one could argue is a sizable portion - if not a majority - of commercial software), do you think that a traditional syscall-based memory management approach, or even a garbage-collected approach, is justifiable in the sense that they better leverage hardware pointer protections and allow architectural choices that make it easier for developers to work in narrower scopes (as in not needing to understand the whole architecture to develop a component of it)? As a final point of discussion, I certainly think it's fair to say there are certain performance-critical components of applications (such as rendering) where these kinds of extreme performance measures are justifiable or necessary. So, where do you fall on the spectrum from "these kinds of patterns are never acceptable" to "there is never a good reason not to use such patterns," and how do you decide whether it is worth it to design for performance at a potential cost of security and maintainability? <!-- SC_ON --> submitted by /u/nerd8622 (https://www.reddit.com/user/nerd8622)
[link] (https://guide.handmadehero.org/code/day341/) [comments] (https://www.reddit.com/r/programming/comments/1le9yyi/data_oriented_design_regionbased_memory/)
https://www.reddit.com/r/programming/comments/1le9yyi/data_oriented_design_regionbased_memory/
<!-- SC_OFF -->Hello, the attached devlog covers a concept I have seen quite a bit from (game) developers enthusiastic about data-oriented design, which is region-based memory management. An example of this pattern is a program allocating a very large memory region on the heap and then placing data in the region using normal integers, effectively using them as offsets to refer to the location of data within the large region. While it certainly seems fair that such techniques have the potential to make programs more cache-efficient and space-efficient, and even reduce bugs when done right, I am curious to hear some opinions on whether this pattern could be considered a potential cybersecurity hazard. On the one hand, DOD seems to offer a lot of benefits as a programming paradigm, but I wonder whether there is merit to saying that the extremes of hand-rolled memory management could start to be problematic in the sense that you lose out on both the hardware-level and kernel-level security features that are designed for regular pointers. For applications that are more concerned with security and ease of development than aggressively minimizing instruction count (which one could argue is a sizable portion - if not a majority - of commercial software), do you think that a traditional syscall-based memory management approach, or even a garbage-collected approach, is justifiable in the sense that they better leverage hardware pointer protections and allow architectural choices that make it easier for developers to work in narrower scopes (as in not needing to understand the whole architecture to develop a component of it)? As a final point of discussion, I certainly think it's fair to say there are certain performance-critical components of applications (such as rendering) where these kinds of extreme performance measures are justifiable or necessary. So, where do you fall on the spectrum from "these kinds of patterns are never acceptable" to "there is never a good reason not to use such patterns," and how do you decide whether it is worth it to design for performance at a potential cost of security and maintainability? <!-- SC_ON --> submitted by /u/nerd8622 (https://www.reddit.com/user/nerd8622)
[link] (https://guide.handmadehero.org/code/day341/) [comments] (https://www.reddit.com/r/programming/comments/1le9yyi/data_oriented_design_regionbased_memory/)
Linking programming, set theory, and number theory...
https://www.reddit.com/r/programming/comments/1le9z0b/linking_programming_set_theory_and_number_theory/
<!-- SC_OFF -->This is my SoME4 submission that I think takes a novel approach towards Boolean operations, multisets, and prime factors. It turns out being good at programming can really help with this specific concept in number theory. I'd appreciate any feedback that I can use to improve in future videos. The last time I posted here, people gave lots of useful tips. <!-- SC_ON --> submitted by /u/pihedron (https://www.reddit.com/user/pihedron)
[link] (https://youtu.be/9HZDiLsJ4-Y) [comments] (https://www.reddit.com/r/programming/comments/1le9z0b/linking_programming_set_theory_and_number_theory/)
https://www.reddit.com/r/programming/comments/1le9z0b/linking_programming_set_theory_and_number_theory/
<!-- SC_OFF -->This is my SoME4 submission that I think takes a novel approach towards Boolean operations, multisets, and prime factors. It turns out being good at programming can really help with this specific concept in number theory. I'd appreciate any feedback that I can use to improve in future videos. The last time I posted here, people gave lots of useful tips. <!-- SC_ON --> submitted by /u/pihedron (https://www.reddit.com/user/pihedron)
[link] (https://youtu.be/9HZDiLsJ4-Y) [comments] (https://www.reddit.com/r/programming/comments/1le9z0b/linking_programming_set_theory_and_number_theory/)
Benchmark: snapDOM may be a serious alternative to html2canvas
https://www.reddit.com/r/programming/comments/1leaam8/benchmark_snapdom_may_be_a_serious_alternative_to/
submitted by /u/tinchox5 (https://www.reddit.com/user/tinchox5)
[link] (https://zumerlab.github.io/snapdom/#benchmark) [comments] (https://www.reddit.com/r/programming/comments/1leaam8/benchmark_snapdom_may_be_a_serious_alternative_to/)
https://www.reddit.com/r/programming/comments/1leaam8/benchmark_snapdom_may_be_a_serious_alternative_to/
submitted by /u/tinchox5 (https://www.reddit.com/user/tinchox5)
[link] (https://zumerlab.github.io/snapdom/#benchmark) [comments] (https://www.reddit.com/r/programming/comments/1leaam8/benchmark_snapdom_may_be_a_serious_alternative_to/)
Voiden: The Offline API Devtool
https://www.reddit.com/r/programming/comments/1lefans/voiden_the_offline_api_devtool/
<!-- SC_OFF -->So, somewhere along the way, API tooling has lost the plot. One tool for specs. Another for tests. A third one for docs. Then, a parade of SDKs, mocks, CI scripts, and shiny portals nobody really asked for. All served up by platforms that charge you a fortune while flying in celebrities to play "developer advocate" at their overblown conferences. And the ones who don't do all of that just end up differing from it in color palettes, and the way they paywall core features. Hence Voiden. A tool that came out of the frustration of its creators in need of something better.
Unifying the API work without heavy-handed platforms controlling our process.
With Voiden, you can define, test, and document APIs like a developer, not a SaaS user.
No accounts. No lock-in. No telemetry. Just Markdown, Git, hotkeys, and your damn specs. TL;DR
- Keep specs, tests, and docs in plain Markdown, not across half a dozen tools you must keep in sync.
- Version with Git, not proprietary clouds.
- Extend with plugins, not paywalls.
- No syncing.
- No "collaboration" tax. And yes, Voiden looks different than your ordinary API client.
That is the point. It's a unique approach to building APIs. Your workflow, your rules. Your Voiden file can be as simple as a couple of hotkeys. Or it can be as complex as you want it to be. Import (multiple) reusable block(s) from across your project and document everything you need. Oh, and your messy old Postman and OAS YAML files are all importable and generate executable, documentable files within the app. <!-- SC_ON --> submitted by /u/kiselitza (https://www.reddit.com/user/kiselitza)
[link] (https://voiden.md/) [comments] (https://www.reddit.com/r/programming/comments/1lefans/voiden_the_offline_api_devtool/)
https://www.reddit.com/r/programming/comments/1lefans/voiden_the_offline_api_devtool/
<!-- SC_OFF -->So, somewhere along the way, API tooling has lost the plot. One tool for specs. Another for tests. A third one for docs. Then, a parade of SDKs, mocks, CI scripts, and shiny portals nobody really asked for. All served up by platforms that charge you a fortune while flying in celebrities to play "developer advocate" at their overblown conferences. And the ones who don't do all of that just end up differing from it in color palettes, and the way they paywall core features. Hence Voiden. A tool that came out of the frustration of its creators in need of something better.
Unifying the API work without heavy-handed platforms controlling our process.
With Voiden, you can define, test, and document APIs like a developer, not a SaaS user.
No accounts. No lock-in. No telemetry. Just Markdown, Git, hotkeys, and your damn specs. TL;DR
- Keep specs, tests, and docs in plain Markdown, not across half a dozen tools you must keep in sync.
- Version with Git, not proprietary clouds.
- Extend with plugins, not paywalls.
- No syncing.
- No "collaboration" tax. And yes, Voiden looks different than your ordinary API client.
That is the point. It's a unique approach to building APIs. Your workflow, your rules. Your Voiden file can be as simple as a couple of hotkeys. Or it can be as complex as you want it to be. Import (multiple) reusable block(s) from across your project and document everything you need. Oh, and your messy old Postman and OAS YAML files are all importable and generate executable, documentable files within the app. <!-- SC_ON --> submitted by /u/kiselitza (https://www.reddit.com/user/kiselitza)
[link] (https://voiden.md/) [comments] (https://www.reddit.com/r/programming/comments/1lefans/voiden_the_offline_api_devtool/)
Advanced Rust Programming Techniques • Florian Gilcher
https://www.reddit.com/r/programming/comments/1lefknc/advanced_rust_programming_techniques_florian/
submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/QQzAWxYKPSE) [comments] (https://www.reddit.com/r/programming/comments/1lefknc/advanced_rust_programming_techniques_florian/)
https://www.reddit.com/r/programming/comments/1lefknc/advanced_rust_programming_techniques_florian/
submitted by /u/goto-con (https://www.reddit.com/user/goto-con)
[link] (https://youtu.be/QQzAWxYKPSE) [comments] (https://www.reddit.com/r/programming/comments/1lefknc/advanced_rust_programming_techniques_florian/)
Coding a RSS Article Aggregator; Episode 2 MVP, Article Module, Cron Jobs
https://www.reddit.com/r/programming/comments/1leglyk/coding_a_rss_article_aggregator_episode_2_mvp/
submitted by /u/ambyAgubuzo (https://www.reddit.com/user/ambyAgubuzo)
[link] (https://youtube.com/watch?v=8BLbkDYH_OU&si=sU4T4o3c08LjEJNL) [comments] (https://www.reddit.com/r/programming/comments/1leglyk/coding_a_rss_article_aggregator_episode_2_mvp/)
https://www.reddit.com/r/programming/comments/1leglyk/coding_a_rss_article_aggregator_episode_2_mvp/
submitted by /u/ambyAgubuzo (https://www.reddit.com/user/ambyAgubuzo)
[link] (https://youtube.com/watch?v=8BLbkDYH_OU&si=sU4T4o3c08LjEJNL) [comments] (https://www.reddit.com/r/programming/comments/1leglyk/coding_a_rss_article_aggregator_episode_2_mvp/)
A* Path Finding
https://www.reddit.com/r/programming/comments/1legxlh/a_path_finding/
submitted by /u/symbolicard (https://www.reddit.com/user/symbolicard)
[link] (https://www.redblobgames.com/pathfinding/a-star/introduction.html) [comments] (https://www.reddit.com/r/programming/comments/1legxlh/a_path_finding/)
https://www.reddit.com/r/programming/comments/1legxlh/a_path_finding/
submitted by /u/symbolicard (https://www.reddit.com/user/symbolicard)
[link] (https://www.redblobgames.com/pathfinding/a-star/introduction.html) [comments] (https://www.reddit.com/r/programming/comments/1legxlh/a_path_finding/)
Ace Your Next JavaScript Interview: `this`, `new`, Prototypes, Classes (Part 3) ✨
https://www.reddit.com/r/programming/comments/1leh78y/ace_your_next_javascript_interview_this_new/
submitted by /u/pepincho (https://www.reddit.com/user/pepincho)
[link] (https://thetshaped.dev/p/ace-your-next-javascript-interview-this-new-keywords-prototypes-classes) [comments] (https://www.reddit.com/r/programming/comments/1leh78y/ace_your_next_javascript_interview_this_new/)
https://www.reddit.com/r/programming/comments/1leh78y/ace_your_next_javascript_interview_this_new/
submitted by /u/pepincho (https://www.reddit.com/user/pepincho)
[link] (https://thetshaped.dev/p/ace-your-next-javascript-interview-this-new-keywords-prototypes-classes) [comments] (https://www.reddit.com/r/programming/comments/1leh78y/ace_your_next_javascript_interview_this_new/)
Exploring JavaScript (ES2025 Edition)
https://www.reddit.com/r/programming/comments/1lehwel/exploring_javascript_es2025_edition/
submitted by /u/mariuz (https://www.reddit.com/user/mariuz)
[link] (https://exploringjs.com/js/downloads/exploring-js-book-changelog.html) [comments] (https://www.reddit.com/r/programming/comments/1lehwel/exploring_javascript_es2025_edition/)
https://www.reddit.com/r/programming/comments/1lehwel/exploring_javascript_es2025_edition/
submitted by /u/mariuz (https://www.reddit.com/user/mariuz)
[link] (https://exploringjs.com/js/downloads/exploring-js-book-changelog.html) [comments] (https://www.reddit.com/r/programming/comments/1lehwel/exploring_javascript_es2025_edition/)
CRA to Next.js: Unlock 5x Performance & Perfect SE
https://www.reddit.com/r/programming/comments/1leigvo/cra_to_nextjs_unlock_5x_performance_perfect_se/
<!-- SC_OFF -->Hey everyone, With Create React App now deprecated, I know a lot of us are looking at how to migrate existing projects. I just finished moving a decent-sized app over to the Next.js App Router and wanted to share what I learned. The biggest "aha!" moments for me were: Moving all data fetching from useEffect hooks into async Server Components. This completely eliminated my client-side request waterfalls. Replacing react-router-dom with the new file-based routing and next/navigation hooks. Using middleware for auth instead of client-side logic. It's so much cleaner. I compiled all my notes, code snippets, and a pre-migration checklist into a full guide to make the process easier for others. Hope it helps you out! Link:https://beyondit.blog/blogs/CRA-to-Next-js-Unlock-5x-Performance-Perfect-SEO <!-- SC_ON --> submitted by /u/WillingnessFun7051 (https://www.reddit.com/user/WillingnessFun7051)
[link] (https://beyondit.blog/blogs/CRA-to-Next-js-Unlock-5x-Performance-Perfect-SEO) [comments] (https://www.reddit.com/r/programming/comments/1leigvo/cra_to_nextjs_unlock_5x_performance_perfect_se/)
https://www.reddit.com/r/programming/comments/1leigvo/cra_to_nextjs_unlock_5x_performance_perfect_se/
<!-- SC_OFF -->Hey everyone, With Create React App now deprecated, I know a lot of us are looking at how to migrate existing projects. I just finished moving a decent-sized app over to the Next.js App Router and wanted to share what I learned. The biggest "aha!" moments for me were: Moving all data fetching from useEffect hooks into async Server Components. This completely eliminated my client-side request waterfalls. Replacing react-router-dom with the new file-based routing and next/navigation hooks. Using middleware for auth instead of client-side logic. It's so much cleaner. I compiled all my notes, code snippets, and a pre-migration checklist into a full guide to make the process easier for others. Hope it helps you out! Link:https://beyondit.blog/blogs/CRA-to-Next-js-Unlock-5x-Performance-Perfect-SEO <!-- SC_ON --> submitted by /u/WillingnessFun7051 (https://www.reddit.com/user/WillingnessFun7051)
[link] (https://beyondit.blog/blogs/CRA-to-Next-js-Unlock-5x-Performance-Perfect-SEO) [comments] (https://www.reddit.com/r/programming/comments/1leigvo/cra_to_nextjs_unlock_5x_performance_perfect_se/)
Node.js Interview Q&A: Day 11
https://www.reddit.com/r/programming/comments/1leit9l/nodejs_interview_qa_day_11/
submitted by /u/MysteriousEye8494 (https://www.reddit.com/user/MysteriousEye8494)
[link] (https://medium.com/devinsight/node-js-interview-q-a-day-11-af1fb3153220) [comments] (https://www.reddit.com/r/programming/comments/1leit9l/nodejs_interview_qa_day_11/)
https://www.reddit.com/r/programming/comments/1leit9l/nodejs_interview_qa_day_11/
submitted by /u/MysteriousEye8494 (https://www.reddit.com/user/MysteriousEye8494)
[link] (https://medium.com/devinsight/node-js-interview-q-a-day-11-af1fb3153220) [comments] (https://www.reddit.com/r/programming/comments/1leit9l/nodejs_interview_qa_day_11/)
💥 Tech Talks Weekly #64: all new Software Engineering conference talk recordings published in the past 7 days
https://www.reddit.com/r/programming/comments/1lejunu/tech_talks_weekly_64_all_new_software_engineering/
submitted by /u/TechTalksWeekly (https://www.reddit.com/user/TechTalksWeekly)
[link] (https://www.techtalksweekly.io/p/tech-talks-weekly-64) [comments] (https://www.reddit.com/r/programming/comments/1lejunu/tech_talks_weekly_64_all_new_software_engineering/)
https://www.reddit.com/r/programming/comments/1lejunu/tech_talks_weekly_64_all_new_software_engineering/
submitted by /u/TechTalksWeekly (https://www.reddit.com/user/TechTalksWeekly)
[link] (https://www.techtalksweekly.io/p/tech-talks-weekly-64) [comments] (https://www.reddit.com/r/programming/comments/1lejunu/tech_talks_weekly_64_all_new_software_engineering/)
JSON module scripts are now Baseline Newly available
https://www.reddit.com/r/programming/comments/1lem1s3/json_module_scripts_are_now_baseline_newly/
submitted by /u/feross (https://www.reddit.com/user/feross)
[link] (https://web.dev/blog/json-imports-baseline-newly-available?hl=en) [comments] (https://www.reddit.com/r/programming/comments/1lem1s3/json_module_scripts_are_now_baseline_newly/)
https://www.reddit.com/r/programming/comments/1lem1s3/json_module_scripts_are_now_baseline_newly/
submitted by /u/feross (https://www.reddit.com/user/feross)
[link] (https://web.dev/blog/json-imports-baseline-newly-available?hl=en) [comments] (https://www.reddit.com/r/programming/comments/1lem1s3/json_module_scripts_are_now_baseline_newly/)
Building with purpose 6.2: Retrieving the user from Clerk
https://www.reddit.com/r/programming/comments/1lemkdh/building_with_purpose_62_retrieving_the_user_from/
submitted by /u/jordiolle11 (https://www.reddit.com/user/jordiolle11)
[link] (https://www.jordi-olle.com/blog/building-with-purpose-62-retrieving-the-user-from-clerk) [comments] (https://www.reddit.com/r/programming/comments/1lemkdh/building_with_purpose_62_retrieving_the_user_from/)
https://www.reddit.com/r/programming/comments/1lemkdh/building_with_purpose_62_retrieving_the_user_from/
submitted by /u/jordiolle11 (https://www.reddit.com/user/jordiolle11)
[link] (https://www.jordi-olle.com/blog/building-with-purpose-62-retrieving-the-user-from-clerk) [comments] (https://www.reddit.com/r/programming/comments/1lemkdh/building_with_purpose_62_retrieving_the_user_from/)
UI Component Testing Revisited: Modern Implementation with Visual Verification
https://www.reddit.com/r/programming/comments/1lepscg/ui_component_testing_revisited_modern/
submitted by /u/defnotthrown (https://www.reddit.com/user/defnotthrown)
[link] (https://paulhammant.com/2025/06/17/ui-component-testing-revisited/) [comments] (https://www.reddit.com/r/programming/comments/1lepscg/ui_component_testing_revisited_modern/)
https://www.reddit.com/r/programming/comments/1lepscg/ui_component_testing_revisited_modern/
submitted by /u/defnotthrown (https://www.reddit.com/user/defnotthrown)
[link] (https://paulhammant.com/2025/06/17/ui-component-testing-revisited/) [comments] (https://www.reddit.com/r/programming/comments/1lepscg/ui_component_testing_revisited_modern/)
Osprey Programming Language
https://www.reddit.com/r/programming/comments/1letj43/osprey_programming_language/
<!-- SC_OFF -->Osprey is a modern functional programming oriented language designed for elegance, safety, and performance. But, more importantly, this is the first programming language and compiler that encourages you to contribute with AI assistance. Much of the compiler code was written with help from AI. Compilers are no longer relegated to the select few who have the time and privilege to spend years studying compiler design. Check out the playground and jump on the GitHub discussion threads <!-- SC_ON --> submitted by /u/emanresu_2017 (https://www.reddit.com/user/emanresu_2017)
[link] (https://www.ospreylang.dev/) [comments] (https://www.reddit.com/r/programming/comments/1letj43/osprey_programming_language/)
https://www.reddit.com/r/programming/comments/1letj43/osprey_programming_language/
<!-- SC_OFF -->Osprey is a modern functional programming oriented language designed for elegance, safety, and performance. But, more importantly, this is the first programming language and compiler that encourages you to contribute with AI assistance. Much of the compiler code was written with help from AI. Compilers are no longer relegated to the select few who have the time and privilege to spend years studying compiler design. Check out the playground and jump on the GitHub discussion threads <!-- SC_ON --> submitted by /u/emanresu_2017 (https://www.reddit.com/user/emanresu_2017)
[link] (https://www.ospreylang.dev/) [comments] (https://www.reddit.com/r/programming/comments/1letj43/osprey_programming_language/)