rules_derive: deriving using macro_rules
https://www.reddit.com/r/programming/comments/1mcj49w/rules_derive_deriving_using_macro_rules/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://matx.com/research/rules_derive) [comments] (https://www.reddit.com/r/programming/comments/1mcj49w/rules_derive_deriving_using_macro_rules/)
https://www.reddit.com/r/programming/comments/1mcj49w/rules_derive_deriving_using_macro_rules/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://matx.com/research/rules_derive) [comments] (https://www.reddit.com/r/programming/comments/1mcj49w/rules_derive_deriving_using_macro_rules/)
The Useless useCallback
https://www.reddit.com/r/programming/comments/1mcj6fr/the_useless_usecallback/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://tkdodo.eu/blog/the-useless-use-callback) [comments] (https://www.reddit.com/r/programming/comments/1mcj6fr/the_useless_usecallback/)
https://www.reddit.com/r/programming/comments/1mcj6fr/the_useless_usecallback/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://tkdodo.eu/blog/the-useless-use-callback) [comments] (https://www.reddit.com/r/programming/comments/1mcj6fr/the_useless_usecallback/)
Debugging the Pixel 8 kernel via KGDB
https://www.reddit.com/r/programming/comments/1mcj6p0/debugging_the_pixel_8_kernel_via_kgdb/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://xairy.io/articles/pixel-kgdb) [comments] (https://www.reddit.com/r/programming/comments/1mcj6p0/debugging_the_pixel_8_kernel_via_kgdb/)
https://www.reddit.com/r/programming/comments/1mcj6p0/debugging_the_pixel_8_kernel_via_kgdb/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://xairy.io/articles/pixel-kgdb) [comments] (https://www.reddit.com/r/programming/comments/1mcj6p0/debugging_the_pixel_8_kernel_via_kgdb/)
Linux 6.16 changelog
https://www.reddit.com/r/programming/comments/1mcj6v8/linux_616_changelog/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://kernelnewbies.org/Linux_6.16) [comments] (https://www.reddit.com/r/programming/comments/1mcj6v8/linux_616_changelog/)
https://www.reddit.com/r/programming/comments/1mcj6v8/linux_616_changelog/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://kernelnewbies.org/Linux_6.16) [comments] (https://www.reddit.com/r/programming/comments/1mcj6v8/linux_616_changelog/)
From XML to JSON to CBOR
https://www.reddit.com/r/programming/comments/1mcj74c/from_xml_to_json_to_cbor/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://cborbook.com/introduction/from_xml_to_json_to_cbor.html) [comments] (https://www.reddit.com/r/programming/comments/1mcj74c/from_xml_to_json_to_cbor/)
https://www.reddit.com/r/programming/comments/1mcj74c/from_xml_to_json_to_cbor/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://cborbook.com/introduction/from_xml_to_json_to_cbor.html) [comments] (https://www.reddit.com/r/programming/comments/1mcj74c/from_xml_to_json_to_cbor/)
Advanced Rust macros with derive-deftly
https://www.reddit.com/r/programming/comments/1mcj769/advanced_rust_macros_with_derivedeftly/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://diziet.pages.torproject.net/rust-derive-deftly/latest/guide/) [comments] (https://www.reddit.com/r/programming/comments/1mcj769/advanced_rust_macros_with_derivedeftly/)
https://www.reddit.com/r/programming/comments/1mcj769/advanced_rust_macros_with_derivedeftly/
submitted by /u/ketralnis (https://www.reddit.com/user/ketralnis)
[link] (https://diziet.pages.torproject.net/rust-derive-deftly/latest/guide/) [comments] (https://www.reddit.com/r/programming/comments/1mcj769/advanced_rust_macros_with_derivedeftly/)
Deprecations and Removals - Inside Java Podcast 39
https://www.reddit.com/r/programming/comments/1mcnc6q/deprecations_and_removals_inside_java_podcast_39/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=fDcOXIk4j28) [comments] (https://www.reddit.com/r/programming/comments/1mcnc6q/deprecations_and_removals_inside_java_podcast_39/)
https://www.reddit.com/r/programming/comments/1mcnc6q/deprecations_and_removals_inside_java_podcast_39/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=fDcOXIk4j28) [comments] (https://www.reddit.com/r/programming/comments/1mcnc6q/deprecations_and_removals_inside_java_podcast_39/)
The Ultimate Git Tutorial (Git 2.50)
https://www.reddit.com/r/programming/comments/1md1a1y/the_ultimate_git_tutorial_git_250/
<!-- SC_OFF -->The ultimate Git tutorial (https://jhcarl0814.github.io/ClosedAI/git/git.html) has been updated (from Git 2.49 to Git 2.50). Previous post from Git 2.47 era introducing What & Why and Features for this tutorial. What & Why: The ultimate tutorial for beginners to thoroughly understand Git, introducing concepts/terminologies in a pedagogically sound order, illustrating command options and their combinations/interactions with examples. This way, learning Git no longer feels like a lost cause. You'll be able to spot, solve or prevent problems others can't, so you won't feel out of control whenever a problem arises. The ultimate knowledge base site for experienced users, grouping command options into intuitive categories for easy discovery. FAQ Q1: There is too much content, while I somehow expect to read only a portion when facing a lot of content, selectively. How do I use the page to learn Git?
A1: Unselectively read all the concept links and blue command links in DOM order. Blue command links introduce most commonly used Git commands and contain examples for command options. For example, click to read the definition of "object database", then "file system", and so on. Q2: This doesn't look like a tutorial, as tutorials should look easy, very very easy, want easy things you know. / Where is the tutorial? I only see many links. / I think learning to use a revision control system should only be a small part of my programming job, so it should not take tremendous amount of time. / I just want to get job done quickly and then run away, sure no one wants to figure out what is working or how it is working behind the scenes. / I think revision control systems should be easy because it's not programming proper. Look at XXX revision control system, it's easy (but apparently nobody uses it)! / Want easy things, very very easy, tremendously easy.
A2: Here you go. (https://www.reddit.com/r/git/comments/1ftj350/mastering_git_a_comprehensive_git_cheatsheet_for/) Oh wait. (https://medium.com/@amitmishraam941/mastering-git-a-comprehensive-command-cheatsheet-95ed1db88847) Q3: I used the tutorials in A2 but don't know what to do whenever I want to do something with Git. / I used the tutorials in A2 but screwed up at work so now I'm staring at the screen in a daze. / I should be able to do what I want after reading some tremendously easy tutorials, but I can't. Now I need to continue looking for easy tutorials that is easy for beginners. / How to use a revision control system if I cannot?
A3: Here are more easy tutorials. (https://www.google.com/search?q=mastering+git+a+comprehensive+git+cheatsheet+for) Q4: This tutorial is unintuitive, arcane and overwhelming.
A4: So people who can't think abstractly and deeply can be shut out. Q5: Why not just RTFM (https://git-scm.com/docs)? / Git is easy, so those who feel it difficult should not go programming. / People should be able to look for information themselves to learn programming so there is no need to make a page like this. / (And other attempts to keep knowledge scattered all around the Internet so you would spend all your life collecting it, this way you don't have time to think about things like Illu*******, so good!đ)
A5: Knowledge gathering and organization is to save people's time. If you don't take other people's time seriously, they won't take your time seriously either. Q6: http://git-scm.com/book / http://gitimmersion.com/ / I can't see the links in the side bar of r/git (https://www.reddit.com/r/git) đđđ, so can you repeat them here? / (And links to other tutorials, no idea why they don't make a standalone post.)
https://www.reddit.com/r/programming/comments/1md1a1y/the_ultimate_git_tutorial_git_250/
<!-- SC_OFF -->The ultimate Git tutorial (https://jhcarl0814.github.io/ClosedAI/git/git.html) has been updated (from Git 2.49 to Git 2.50). Previous post from Git 2.47 era introducing What & Why and Features for this tutorial. What & Why: The ultimate tutorial for beginners to thoroughly understand Git, introducing concepts/terminologies in a pedagogically sound order, illustrating command options and their combinations/interactions with examples. This way, learning Git no longer feels like a lost cause. You'll be able to spot, solve or prevent problems others can't, so you won't feel out of control whenever a problem arises. The ultimate knowledge base site for experienced users, grouping command options into intuitive categories for easy discovery. FAQ Q1: There is too much content, while I somehow expect to read only a portion when facing a lot of content, selectively. How do I use the page to learn Git?
A1: Unselectively read all the concept links and blue command links in DOM order. Blue command links introduce most commonly used Git commands and contain examples for command options. For example, click to read the definition of "object database", then "file system", and so on. Q2: This doesn't look like a tutorial, as tutorials should look easy, very very easy, want easy things you know. / Where is the tutorial? I only see many links. / I think learning to use a revision control system should only be a small part of my programming job, so it should not take tremendous amount of time. / I just want to get job done quickly and then run away, sure no one wants to figure out what is working or how it is working behind the scenes. / I think revision control systems should be easy because it's not programming proper. Look at XXX revision control system, it's easy (but apparently nobody uses it)! / Want easy things, very very easy, tremendously easy.
A2: Here you go. (https://www.reddit.com/r/git/comments/1ftj350/mastering_git_a_comprehensive_git_cheatsheet_for/) Oh wait. (https://medium.com/@amitmishraam941/mastering-git-a-comprehensive-command-cheatsheet-95ed1db88847) Q3: I used the tutorials in A2 but don't know what to do whenever I want to do something with Git. / I used the tutorials in A2 but screwed up at work so now I'm staring at the screen in a daze. / I should be able to do what I want after reading some tremendously easy tutorials, but I can't. Now I need to continue looking for easy tutorials that is easy for beginners. / How to use a revision control system if I cannot?
A3: Here are more easy tutorials. (https://www.google.com/search?q=mastering+git+a+comprehensive+git+cheatsheet+for) Q4: This tutorial is unintuitive, arcane and overwhelming.
A4: So people who can't think abstractly and deeply can be shut out. Q5: Why not just RTFM (https://git-scm.com/docs)? / Git is easy, so those who feel it difficult should not go programming. / People should be able to look for information themselves to learn programming so there is no need to make a page like this. / (And other attempts to keep knowledge scattered all around the Internet so you would spend all your life collecting it, this way you don't have time to think about things like Illu*******, so good!đ)
A5: Knowledge gathering and organization is to save people's time. If you don't take other people's time seriously, they won't take your time seriously either. Q6: http://git-scm.com/book / http://gitimmersion.com/ / I can't see the links in the side bar of r/git (https://www.reddit.com/r/git) đđđ, so can you repeat them here? / (And links to other tutorials, no idea why they don't make a standalone post.)
A6: Pro Git, Git Ready, Git Reference, Git Magic, Git for Computer Scientists, A Visual Git Reference, Git Primer, Git Immersion, Think Like a Git, Git Workflows, Git on Stack Overflow, Getting Git Right, The Git Parable. Updates: Added external links to precedence among options and environment variables and configuration variables, and security section of git upload-pack. Added concept links to tree, directory, hook, merge workflow, patch workflow, and many merge-operation-related concepts; moved and grouped all merge-operation-related concept links at one place under "Combining Diffs" section. Added internal link to examples for namespaces. Added plumbing link to git check-mailmap. Extracted common prefixes in links' text into bash brace expansion style. Simplified (e.g. removing unnecessary intermediate shell variables and scaffolding branches and tags) and/or improved (e.g. adding diff against AUTO_MERGE, adding commands to orthogonally show effects of options, adding commands to deal with post-merge-conflict situations, adding options to print more relevant paths in more predictable form, printing values of intermediate shell variables) examples: Parameters: "git config rename-section and git config remove-section", "git var", "git -C [] and git --git-dir= [] and git --work-tree= []", "git --bare [] and git --git-dir= [] and git --work-tree= []", "git --namespace= []". Managing Working Trees: "git worktree add --track/--no-track". Managing References: "git ls-remote --get-url". Repository Creation and Synchronization: "git init --separate-git-dir=", "git clone --separate-git-dir=", "git clone --config='remote.origin.fetch='", "git fetch --shallow-exclude=", "git fetch remote to fetch from", "git push [--tags]", "git push --force-with-lease --force-if-includes/--no-force-if-includes", "git push --force-with-lease=:". Diffing: "git diff --find-renames= --break-rewrites=[][/]", "git diff --find-copies= --break-rewrites=[][/]", "git diff --find-object=". Listing History: "git log --first-parent", "git log commit following and inclusion". Snapshotting: "git checkout (without ) (with âĻ)", "git checkout (with optional ) (without âĻ)", "git reset --merge". Merge Workflow: "git merge --squash and git merge (--no-squash) --no-commit". Rewriting History: "git rebase --root --onto= []", "git rebase --rebase-merges=rebase-cousins". Fixed typo or formatting in description of these examples: "git checkout (with optional ) (without âĻ)", "git reset --keep", "git diff --stat". Fixed these examples (e.g. escaping control characters) to make output conform to HTML spec (The W3C Markup Validation Service (https://validator.w3.org/)): "git config allowed characters in section name and subsection name", "git config allowed characters in value". Split "git fetch refs to fetch from remote and local refs to update" into two examples "git fetch refs to fetch from remote" and "git fetch local refs to update". <!-- SC_ON --> submitted by /u/jhcarl0814 (https://www.reddit.com/user/jhcarl0814)
[link] (https://jhcarl0814.github.io/ClosedAI/git/git.html) [comments] (https://www.reddit.com/r/programming/comments/1md1a1y/the_ultimate_git_tutorial_git_250/)
[link] (https://jhcarl0814.github.io/ClosedAI/git/git.html) [comments] (https://www.reddit.com/r/programming/comments/1md1a1y/the_ultimate_git_tutorial_git_250/)
Happy 20th birthday MDN!
https://www.reddit.com/r/programming/comments/1md1cc2/happy_20th_birthday_mdn/
submitted by /u/feross (https://www.reddit.com/user/feross)
[link] (https://web.dev/blog/mdn-birthday?hl=en) [comments] (https://www.reddit.com/r/programming/comments/1md1cc2/happy_20th_birthday_mdn/)
https://www.reddit.com/r/programming/comments/1md1cc2/happy_20th_birthday_mdn/
submitted by /u/feross (https://www.reddit.com/user/feross)
[link] (https://web.dev/blog/mdn-birthday?hl=en) [comments] (https://www.reddit.com/r/programming/comments/1md1cc2/happy_20th_birthday_mdn/)
đšī¸ Virtual Office 2D game self-hostable & open-sourced!
https://www.reddit.com/r/programming/comments/1md1fxd/virtual_office_2d_game_selfhostable_opensourced/
submitted by /u/Inevitable-Brain-629 (https://www.reddit.com/user/Inevitable-Brain-629)
[link] (https://github.com/workadventure/workadventure) [comments] (https://www.reddit.com/r/programming/comments/1md1fxd/virtual_office_2d_game_selfhostable_opensourced/)
https://www.reddit.com/r/programming/comments/1md1fxd/virtual_office_2d_game_selfhostable_opensourced/
submitted by /u/Inevitable-Brain-629 (https://www.reddit.com/user/Inevitable-Brain-629)
[link] (https://github.com/workadventure/workadventure) [comments] (https://www.reddit.com/r/programming/comments/1md1fxd/virtual_office_2d_game_selfhostable_opensourced/)
Most watched Software Engineering talks of 2025 (so far)
https://www.reddit.com/r/programming/comments/1md34bm/most_watched_software_engineering_talks_of_2025/
submitted by /u/GarethX (https://www.reddit.com/user/GarethX)
[link] (https://www.techtalksweekly.io/p/50-most-watched-software-engineering) [comments] (https://www.reddit.com/r/programming/comments/1md34bm/most_watched_software_engineering_talks_of_2025/)
https://www.reddit.com/r/programming/comments/1md34bm/most_watched_software_engineering_talks_of_2025/
submitted by /u/GarethX (https://www.reddit.com/user/GarethX)
[link] (https://www.techtalksweekly.io/p/50-most-watched-software-engineering) [comments] (https://www.reddit.com/r/programming/comments/1md34bm/most_watched_software_engineering_talks_of_2025/)
Documented my journey from monolith hell to event-driven bliss (with actual code, not just pretty diagrams)
https://www.reddit.com/r/programming/comments/1md5bjs/documented_my_journey_from_monolith_hell_to/
<!-- SC_OFF -->Alright, so I just finished what might be the most thorough procrastination project of my career - documenting how to properly break apart a monolithic application. You know those articles that show you beautiful architecture diagrams but leave out all the messy implementation details? Yeah, this is the opposite of that. Built a complete example app and walked through every painful step of the migration. The evolution: Monolith (everything's coupled, it's a mess) Modular monolith (same app, better boundaries) Actual microservices (separate deployments) Event-driven architecture (async all the things) What I actually learned: Split your databases first, even if it breaks stuff. Forces you to think about real boundaries Use tools to enforce your architecture rules (humans are terrible at following conventions) Gradual changes > big rewrites. Each step should be shippable Test coverage at the API level is way more important than unit tests for this stuff The example is a food delivery app because it has all the fun cross-service complexity - orders, payments, deliveries, status updates, etc. Best part? Each phase has working code and handles all the annoying edge cases like "what happens when you can't do joins anymore" and "how do you handle transactions across services." Full thing: https://medium.com/@ilyachase/practical-example-of-decoupling-a-monolithic-php-application-6ff82fefc80a Code: https://github.com/ilyachase/monolith-decoupling-example Anyone else been through architectural migration hell? What patterns actually worked vs what looked good on paper? <!-- SC_ON --> submitted by /u/ilyachase (https://www.reddit.com/user/ilyachase)
[link] (https://medium.com/@ilyachase/practical-example-of-decoupling-a-monolithic-php-application-6ff82fefc80a) [comments] (https://www.reddit.com/r/programming/comments/1md5bjs/documented_my_journey_from_monolith_hell_to/)
https://www.reddit.com/r/programming/comments/1md5bjs/documented_my_journey_from_monolith_hell_to/
<!-- SC_OFF -->Alright, so I just finished what might be the most thorough procrastination project of my career - documenting how to properly break apart a monolithic application. You know those articles that show you beautiful architecture diagrams but leave out all the messy implementation details? Yeah, this is the opposite of that. Built a complete example app and walked through every painful step of the migration. The evolution: Monolith (everything's coupled, it's a mess) Modular monolith (same app, better boundaries) Actual microservices (separate deployments) Event-driven architecture (async all the things) What I actually learned: Split your databases first, even if it breaks stuff. Forces you to think about real boundaries Use tools to enforce your architecture rules (humans are terrible at following conventions) Gradual changes > big rewrites. Each step should be shippable Test coverage at the API level is way more important than unit tests for this stuff The example is a food delivery app because it has all the fun cross-service complexity - orders, payments, deliveries, status updates, etc. Best part? Each phase has working code and handles all the annoying edge cases like "what happens when you can't do joins anymore" and "how do you handle transactions across services." Full thing: https://medium.com/@ilyachase/practical-example-of-decoupling-a-monolithic-php-application-6ff82fefc80a Code: https://github.com/ilyachase/monolith-decoupling-example Anyone else been through architectural migration hell? What patterns actually worked vs what looked good on paper? <!-- SC_ON --> submitted by /u/ilyachase (https://www.reddit.com/user/ilyachase)
[link] (https://medium.com/@ilyachase/practical-example-of-decoupling-a-monolithic-php-application-6ff82fefc80a) [comments] (https://www.reddit.com/r/programming/comments/1md5bjs/documented_my_journey_from_monolith_hell_to/)
Looking for Paywall Article Sharing (Pragmatic Engineer)
https://www.reddit.com/r/programming/comments/1md6nb7/looking_for_paywall_article_sharing_pragmatic/
<!-- SC_OFF -->Hello,
I came across an article that really interests me, but it's behind a subscription paywall ($15/month). That feels like a steep price for just one article, so I was wondering if anyone here is subscribed and could share it with me? Title: Building Great SDKs
Link: https://newsletter.pragmaticengineer.com/p/building-great-sdks Thanks! <!-- SC_ON --> submitted by /u/lambda-person (https://www.reddit.com/user/lambda-person)
[link] (https://newsletter.pragmaticengineer.com/p/building-great-sdks) [comments] (https://www.reddit.com/r/programming/comments/1md6nb7/looking_for_paywall_article_sharing_pragmatic/)
https://www.reddit.com/r/programming/comments/1md6nb7/looking_for_paywall_article_sharing_pragmatic/
<!-- SC_OFF -->Hello,
I came across an article that really interests me, but it's behind a subscription paywall ($15/month). That feels like a steep price for just one article, so I was wondering if anyone here is subscribed and could share it with me? Title: Building Great SDKs
Link: https://newsletter.pragmaticengineer.com/p/building-great-sdks Thanks! <!-- SC_ON --> submitted by /u/lambda-person (https://www.reddit.com/user/lambda-person)
[link] (https://newsletter.pragmaticengineer.com/p/building-great-sdks) [comments] (https://www.reddit.com/r/programming/comments/1md6nb7/looking_for_paywall_article_sharing_pragmatic/)
Desktop app distribution in 2024 - are we solving the right problems?
https://www.reddit.com/r/programming/comments/1md6xy8/desktop_app_distribution_in_2024_are_we_solving/
<!-- SC_OFF -->Mobile has App Store and Google Play. Web has npm and browser extension stores. Desktop has... what exactly? This seems particularly relevant for AI applications where desktop offers significant advantages: Direct hardware access (GPU, specialized chips) No bandwidth constraints for large models Privacy by default (data doesn't leave the machine) System-level integration capabilities Technical question: What's preventing modern desktop app distribution from being a solved problem? Challenges I've been thinking about: Cross-platform packaging and dependency management Automated updates without compromising security Discovery algorithms for desktop software Code signing across different operating systems For the community: Those building desktop applications (especially AI tools), what's your biggest distribution challenge? Are current solutions like GitHub releases, direct downloads, or OS-specific stores adequate? Related observation: Many new AI tools work better as desktop apps than web apps, but discovery remains terrible. Wondering if this represents a broader opportunity in desktop software distribution. Curious about the community's thoughts on the state of desktop app ecosystems and whether there are technical solutions we're missing. <!-- SC_ON --> submitted by /u/Real-Tip8531 (https://www.reddit.com/user/Real-Tip8531)
[link] (https://pcagents.store/) [comments] (https://www.reddit.com/r/programming/comments/1md6xy8/desktop_app_distribution_in_2024_are_we_solving/)
https://www.reddit.com/r/programming/comments/1md6xy8/desktop_app_distribution_in_2024_are_we_solving/
<!-- SC_OFF -->Mobile has App Store and Google Play. Web has npm and browser extension stores. Desktop has... what exactly? This seems particularly relevant for AI applications where desktop offers significant advantages: Direct hardware access (GPU, specialized chips) No bandwidth constraints for large models Privacy by default (data doesn't leave the machine) System-level integration capabilities Technical question: What's preventing modern desktop app distribution from being a solved problem? Challenges I've been thinking about: Cross-platform packaging and dependency management Automated updates without compromising security Discovery algorithms for desktop software Code signing across different operating systems For the community: Those building desktop applications (especially AI tools), what's your biggest distribution challenge? Are current solutions like GitHub releases, direct downloads, or OS-specific stores adequate? Related observation: Many new AI tools work better as desktop apps than web apps, but discovery remains terrible. Wondering if this represents a broader opportunity in desktop software distribution. Curious about the community's thoughts on the state of desktop app ecosystems and whether there are technical solutions we're missing. <!-- SC_ON --> submitted by /u/Real-Tip8531 (https://www.reddit.com/user/Real-Tip8531)
[link] (https://pcagents.store/) [comments] (https://www.reddit.com/r/programming/comments/1md6xy8/desktop_app_distribution_in_2024_are_we_solving/)
Zstandard Compression in Python 3.14: Why It Is a Big Deal for Developers
https://www.reddit.com/r/programming/comments/1mdajyi/zstandard_compression_in_python_314_why_it_is_a/
submitted by /u/yangzhou1993 (https://www.reddit.com/user/yangzhou1993)
[link] (https://yangzhou1993.medium.com/b161fea9ffcb?sk=cef998d87e1a0712cd0c5c0b39e74ed8) [comments] (https://www.reddit.com/r/programming/comments/1mdajyi/zstandard_compression_in_python_314_why_it_is_a/)
https://www.reddit.com/r/programming/comments/1mdajyi/zstandard_compression_in_python_314_why_it_is_a/
submitted by /u/yangzhou1993 (https://www.reddit.com/user/yangzhou1993)
[link] (https://yangzhou1993.medium.com/b161fea9ffcb?sk=cef998d87e1a0712cd0c5c0b39e74ed8) [comments] (https://www.reddit.com/r/programming/comments/1mdajyi/zstandard_compression_in_python_314_why_it_is_a/)
Yes, the majority of language migrations are driven by hype
https://www.reddit.com/r/programming/comments/1mdaocg/yes_the_majority_of_language_migrations_are/
<!-- SC_OFF -->71% of experienced software developers say their language migration decisions were influenced more by hype than by proven outcomes, and the other 29% are lying. <!-- SC_ON --> submitted by /u/scarey102 (https://www.reddit.com/user/scarey102)
[link] (https://leaddev.com/technical-direction/yes-the-majority-of-language-migrations-are-driven-by-hype) [comments] (https://www.reddit.com/r/programming/comments/1mdaocg/yes_the_majority_of_language_migrations_are/)
https://www.reddit.com/r/programming/comments/1mdaocg/yes_the_majority_of_language_migrations_are/
<!-- SC_OFF -->71% of experienced software developers say their language migration decisions were influenced more by hype than by proven outcomes, and the other 29% are lying. <!-- SC_ON --> submitted by /u/scarey102 (https://www.reddit.com/user/scarey102)
[link] (https://leaddev.com/technical-direction/yes-the-majority-of-language-migrations-are-driven-by-hype) [comments] (https://www.reddit.com/r/programming/comments/1mdaocg/yes_the_majority_of_language_migrations_are/)
Sharding Postgres at network speed
https://www.reddit.com/r/programming/comments/1mdc7w1/sharding_postgres_at_network_speed/
submitted by /u/levkk1 (https://www.reddit.com/user/levkk1)
[link] (https://pgdog.dev/blog/sharding-postgres-at-network-speed) [comments] (https://www.reddit.com/r/programming/comments/1mdc7w1/sharding_postgres_at_network_speed/)
https://www.reddit.com/r/programming/comments/1mdc7w1/sharding_postgres_at_network_speed/
submitted by /u/levkk1 (https://www.reddit.com/user/levkk1)
[link] (https://pgdog.dev/blog/sharding-postgres-at-network-speed) [comments] (https://www.reddit.com/r/programming/comments/1mdc7w1/sharding_postgres_at_network_speed/)
You're Shipping Too Slow - Improving Deployment frequency
https://www.reddit.com/r/programming/comments/1mdgs31/youre_shipping_too_slow_improving_deployment/
submitted by /u/agbell (https://www.reddit.com/user/agbell)
[link] (https://www.youtube.com/watch?v=Qfl3KUl2vT4) [comments] (https://www.reddit.com/r/programming/comments/1mdgs31/youre_shipping_too_slow_improving_deployment/)
https://www.reddit.com/r/programming/comments/1mdgs31/youre_shipping_too_slow_improving_deployment/
submitted by /u/agbell (https://www.reddit.com/user/agbell)
[link] (https://www.youtube.com/watch?v=Qfl3KUl2vT4) [comments] (https://www.reddit.com/r/programming/comments/1mdgs31/youre_shipping_too_slow_improving_deployment/)
A Jujutsu later: Exploring jj-vcs
https://www.reddit.com/r/programming/comments/1mdhy0m/a_jujutsu_later_exploring_jjvcs/
submitted by /u/Sonder-Otis (https://www.reddit.com/user/Sonder-Otis)
[link] (https://mtende.blog/a-jujutsu-later) [comments] (https://www.reddit.com/r/programming/comments/1mdhy0m/a_jujutsu_later_exploring_jjvcs/)
https://www.reddit.com/r/programming/comments/1mdhy0m/a_jujutsu_later_exploring_jjvcs/
submitted by /u/Sonder-Otis (https://www.reddit.com/user/Sonder-Otis)
[link] (https://mtende.blog/a-jujutsu-later) [comments] (https://www.reddit.com/r/programming/comments/1mdhy0m/a_jujutsu_later_exploring_jjvcs/)
GitHub - isene/xrpn: The eXtended RPN programming language
https://www.reddit.com/r/programming/comments/1mdmpo5/github_isenexrpn_the_extended_rpn_programming/
submitted by /u/isene (https://www.reddit.com/user/isene)
[link] (https://github.com/isene/xrpn) [comments] (https://www.reddit.com/r/programming/comments/1mdmpo5/github_isenexrpn_the_extended_rpn_programming/)
https://www.reddit.com/r/programming/comments/1mdmpo5/github_isenexrpn_the_extended_rpn_programming/
submitted by /u/isene (https://www.reddit.com/user/isene)
[link] (https://github.com/isene/xrpn) [comments] (https://www.reddit.com/r/programming/comments/1mdmpo5/github_isenexrpn_the_extended_rpn_programming/)