Traditional user-interface graphics: icons, cursors, buttons, borders, and drawing style
https://www.reddit.com/r/programming/comments/1s0ymoh/traditional_userinterface_graphics_icons_cursors/
<!-- SC_OFF -->This open-source article (https://peteroupc.github.io/classic-wallpaper/docs/uielements.html) I wrote discusses aspects of the traditional visual design (up to about the year 2003) of user-interface (UI) graphics, such as button and border styles, icons, and mouse pointers. It also seeks to characterize the drawing style of traditional UI graphics, especially from 1990 to 2003, and gives advice on developing new graphical UI systems with a high degree of flexibility. User interfaces found in video games are outside the document's scope. <!-- SC_ON --> submitted by /u/peteroupc (https://www.reddit.com/user/peteroupc)
[link] (https://peteroupc.github.io/classic-wallpaper/docs/uielements.html) [comments] (https://www.reddit.com/r/programming/comments/1s0ymoh/traditional_userinterface_graphics_icons_cursors/)
https://www.reddit.com/r/programming/comments/1s0ymoh/traditional_userinterface_graphics_icons_cursors/
<!-- SC_OFF -->This open-source article (https://peteroupc.github.io/classic-wallpaper/docs/uielements.html) I wrote discusses aspects of the traditional visual design (up to about the year 2003) of user-interface (UI) graphics, such as button and border styles, icons, and mouse pointers. It also seeks to characterize the drawing style of traditional UI graphics, especially from 1990 to 2003, and gives advice on developing new graphical UI systems with a high degree of flexibility. User interfaces found in video games are outside the document's scope. <!-- SC_ON --> submitted by /u/peteroupc (https://www.reddit.com/user/peteroupc)
[link] (https://peteroupc.github.io/classic-wallpaper/docs/uielements.html) [comments] (https://www.reddit.com/r/programming/comments/1s0ymoh/traditional_userinterface_graphics_icons_cursors/)
Node.js worker threads are problematic, but they work great for us
https://www.reddit.com/r/programming/comments/1s108v7/nodejs_worker_threads_are_problematic_but_they/
submitted by /u/aardvark_lizard (https://www.reddit.com/user/aardvark_lizard)
[link] (https://www.inngest.com/blog/node-worker-threads) [comments] (https://www.reddit.com/r/programming/comments/1s108v7/nodejs_worker_threads_are_problematic_but_they/)
https://www.reddit.com/r/programming/comments/1s108v7/nodejs_worker_threads_are_problematic_but_they/
submitted by /u/aardvark_lizard (https://www.reddit.com/user/aardvark_lizard)
[link] (https://www.inngest.com/blog/node-worker-threads) [comments] (https://www.reddit.com/r/programming/comments/1s108v7/nodejs_worker_threads_are_problematic_but_they/)
Pessimistic vs Optimistic Concurrency Control
https://www.reddit.com/r/programming/comments/1s10x8v/pessimistic_vs_optimistic_concurrency_control/
submitted by /u/Comfortable-Fan-580 (https://www.reddit.com/user/Comfortable-Fan-580)
[link] (https://pradyumnachippigiri.substack.com/p/concurrency-controls-pessimistic) [comments] (https://www.reddit.com/r/programming/comments/1s10x8v/pessimistic_vs_optimistic_concurrency_control/)
https://www.reddit.com/r/programming/comments/1s10x8v/pessimistic_vs_optimistic_concurrency_control/
submitted by /u/Comfortable-Fan-580 (https://www.reddit.com/user/Comfortable-Fan-580)
[link] (https://pradyumnachippigiri.substack.com/p/concurrency-controls-pessimistic) [comments] (https://www.reddit.com/r/programming/comments/1s10x8v/pessimistic_vs_optimistic_concurrency_control/)
TrainSec voucher
https://www.reddit.com/r/programming/comments/1s150d3/trainsec_voucher/
<!-- SC_OFF -->I have a $500 TrainSec voucher that I’m not planning to use, so I’m looking to sell it. I’m asking around $250-$300, but the price is negotiable. Let me know if you’re interested. Also, you can choose your course as per your need for $500 <!-- SC_ON --> submitted by /u/Salty-Ad9979 (https://www.reddit.com/user/Salty-Ad9979)
[link] (https://trainsec.net/) [comments] (https://www.reddit.com/r/programming/comments/1s150d3/trainsec_voucher/)
https://www.reddit.com/r/programming/comments/1s150d3/trainsec_voucher/
<!-- SC_OFF -->I have a $500 TrainSec voucher that I’m not planning to use, so I’m looking to sell it. I’m asking around $250-$300, but the price is negotiable. Let me know if you’re interested. Also, you can choose your course as per your need for $500 <!-- SC_ON --> submitted by /u/Salty-Ad9979 (https://www.reddit.com/user/Salty-Ad9979)
[link] (https://trainsec.net/) [comments] (https://www.reddit.com/r/programming/comments/1s150d3/trainsec_voucher/)
Qt 6.11 released
https://www.reddit.com/r/programming/comments/1s1dtk5/qt_611_released/
submitted by /u/jlpcsl (https://www.reddit.com/user/jlpcsl)
[link] (https://www.qt.io/blog/qt-6.11-released) [comments] (https://www.reddit.com/r/programming/comments/1s1dtk5/qt_611_released/)
https://www.reddit.com/r/programming/comments/1s1dtk5/qt_611_released/
submitted by /u/jlpcsl (https://www.reddit.com/user/jlpcsl)
[link] (https://www.qt.io/blog/qt-6.11-released) [comments] (https://www.reddit.com/r/programming/comments/1s1dtk5/qt_611_released/)
Software dev job postings are up 15% since mid 2025
https://www.reddit.com/r/programming/comments/1s1e4il/software_dev_job_postings_are_up_15_since_mid_2025/
<!-- SC_OFF -->Been watching this FRED data for a while. Software development job postings on Indeed hit a low point around May 2025, then climbed steadily for 10 months straight and are now sitting about 15% higher than that trough. The recent acceleration from January 2026 onwards is pretty sharp. This runs directly against the AI is killing developer jobs narrative that's been everywhere for the past two years. I might be wrong but i think AI might actually be creating more software demand, not less. More products get built because the cost of building dropped. Someone still has to architect the systems, build the tooling, maintain the infrastructure. that's all still dev work. Curious what people here are actually seeing. Are you busier or less busy than two years ago? And if you're hiring, is the bar different now? <!-- SC_ON --> submitted by /u/IdeasInProcess (https://www.reddit.com/user/IdeasInProcess)
[link] (https://fred.stlouisfed.org/series/IHLIDXUSTPSOFTDEVE) [comments] (https://www.reddit.com/r/programming/comments/1s1e4il/software_dev_job_postings_are_up_15_since_mid_2025/)
https://www.reddit.com/r/programming/comments/1s1e4il/software_dev_job_postings_are_up_15_since_mid_2025/
<!-- SC_OFF -->Been watching this FRED data for a while. Software development job postings on Indeed hit a low point around May 2025, then climbed steadily for 10 months straight and are now sitting about 15% higher than that trough. The recent acceleration from January 2026 onwards is pretty sharp. This runs directly against the AI is killing developer jobs narrative that's been everywhere for the past two years. I might be wrong but i think AI might actually be creating more software demand, not less. More products get built because the cost of building dropped. Someone still has to architect the systems, build the tooling, maintain the infrastructure. that's all still dev work. Curious what people here are actually seeing. Are you busier or less busy than two years ago? And if you're hiring, is the bar different now? <!-- SC_ON --> submitted by /u/IdeasInProcess (https://www.reddit.com/user/IdeasInProcess)
[link] (https://fred.stlouisfed.org/series/IHLIDXUSTPSOFTDEVE) [comments] (https://www.reddit.com/r/programming/comments/1s1e4il/software_dev_job_postings_are_up_15_since_mid_2025/)
Some practical use of formal grammars when designing a programming language in C++
https://www.reddit.com/r/programming/comments/1s1hqhe/some_practical_use_of_formal_grammars_when/
submitted by /u/Kabra___kiiiiiiiid (https://www.reddit.com/user/Kabra___kiiiiiiiid)
[link] (https://pvs-studio.com/en/webinar/25/) [comments] (https://www.reddit.com/r/programming/comments/1s1hqhe/some_practical_use_of_formal_grammars_when/)
https://www.reddit.com/r/programming/comments/1s1hqhe/some_practical_use_of_formal_grammars_when/
submitted by /u/Kabra___kiiiiiiiid (https://www.reddit.com/user/Kabra___kiiiiiiiid)
[link] (https://pvs-studio.com/en/webinar/25/) [comments] (https://www.reddit.com/r/programming/comments/1s1hqhe/some_practical_use_of_formal_grammars_when/)
ChatGPT, Claude, and Gemini Render Markdown in the Browser. I Do the Opposite
https://www.reddit.com/r/programming/comments/1s1i43t/chatgpt_claude_and_gemini_render_markdown_in_the/
submitted by /u/lorenseanstewart (https://www.reddit.com/user/lorenseanstewart)
[link] (https://www.lorenstew.art/blog/i-do-the-opposite) [comments] (https://www.reddit.com/r/programming/comments/1s1i43t/chatgpt_claude_and_gemini_render_markdown_in_the/)
https://www.reddit.com/r/programming/comments/1s1i43t/chatgpt_claude_and_gemini_render_markdown_in_the/
submitted by /u/lorenseanstewart (https://www.reddit.com/user/lorenseanstewart)
[link] (https://www.lorenstew.art/blog/i-do-the-opposite) [comments] (https://www.reddit.com/r/programming/comments/1s1i43t/chatgpt_claude_and_gemini_render_markdown_in_the/)
SEVI: Silent Data Corruption of Vector Instructions in Hyper-Scale Datacenters
https://www.reddit.com/r/programming/comments/1s1iqsf/sevi_silent_data_corruption_of_vector/
submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://dl.acm.org/doi/10.1145/3779212.3790217) [comments] (https://www.reddit.com/r/programming/comments/1s1iqsf/sevi_silent_data_corruption_of_vector/)
https://www.reddit.com/r/programming/comments/1s1iqsf/sevi_silent_data_corruption_of_vector/
submitted by /u/mttd (https://www.reddit.com/user/mttd)
[link] (https://dl.acm.org/doi/10.1145/3779212.3790217) [comments] (https://www.reddit.com/r/programming/comments/1s1iqsf/sevi_silent_data_corruption_of_vector/)
Governance: Documentation to support projects
https://www.reddit.com/r/programming/comments/1s1jeoz/governance_documentation_to_support_projects/
<!-- SC_OFF -->This is a summary of the main article, the real article goes into more details Two weeks ago I wrote an article about governance and documentation on an organisational scale. This is the follow-up post that focuses on the project scale. You could just read this post, but it’s probably better that you start with the previous one first For me, there are four main areas to support a (large) project. You require the Strategy, the foundation where you start and what the idea of the project is. The Logs, these are living documents that capture what is going on. Blueprint, these are mainly diagrams to support the project visually. And finally Program Management, where you keep everything that’s related to timing and execution. Strategy All of this starts with a Business Case. The “Why” we are doing this document. This can be high level, or very deep. You will also find a Kick-off document here. These are often PowerPoint slides that define the team, scope, way of working, and timelines. Logs I always like to have an Open Questions Log. A centralized document (everyone has access) to questions that need answers. The Decision Log is where you keep track of the closed questions. Again, very handy in an ongoing project, but extra useful once the project is over and it all becomes part of the bigger documentation. Meeting Notes are also handy to store here, probably best in a subdirectory. AI-generated documents are actually very welcome here (compared to other AI generated documentation everywhere else) Blueprints I like to keep my diagrams both in the raw format (visio, draw.io, lucid,…) and in static formats (like PNG). I always like to have diagrams that show both the Target and AS-IS states, and if it’s a big project, what the project phases look like Project related documents I always like a Gantt Chart. Make sure it’s up-to-date and accessible to everyone. Ideally you also have the Critical Path highlighted. Also, deadlines and gates should be present. Providing a central Gantt chart ensures that project management is democratised. The most important ones You pick and choose what you think is essential in the scope of the project. You can also add more later. That being said I like to always have at least the core documents. Even if it’s a project for an app that will be live for two weeks. The Business Case: If this isn’t clear, the architecture will drift. Decision & Question Logs: These are the most valuable “historical” nodes for future maintainers. TO-BE Diagram: A quick reference for everyone on what’s actually changing. Also, easy to copy and paste into presentations for higher-ups. The Gantt: That’s just basic project management and keeps everyone honest. Merging it back into the bigger documentation The diagrams can move towards the resources section with links to the applications. Going over the logs, you can remove the noise and keep the logs that are relevant to processes and applications to the logs of those processes and applications. You end up moving the rest to the archive section as a project folder. It’s very essential to not just delete here. If you have a similar project in the future, you can copy a lot of homework here. Organic documentation So these are my current views on documentation. To paraphrase this article and the previous one: Small documents that are interconnected. Accessible and owned by everyone. Organically grown and mainly written from a project perspective. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2026-03-22-governance-documentation-to-support-projects/) [comments] (https://www.reddit.com/r/programming/comments/1s1jeoz/governance_documentation_to_support_projects/)
https://www.reddit.com/r/programming/comments/1s1jeoz/governance_documentation_to_support_projects/
<!-- SC_OFF -->This is a summary of the main article, the real article goes into more details Two weeks ago I wrote an article about governance and documentation on an organisational scale. This is the follow-up post that focuses on the project scale. You could just read this post, but it’s probably better that you start with the previous one first For me, there are four main areas to support a (large) project. You require the Strategy, the foundation where you start and what the idea of the project is. The Logs, these are living documents that capture what is going on. Blueprint, these are mainly diagrams to support the project visually. And finally Program Management, where you keep everything that’s related to timing and execution. Strategy All of this starts with a Business Case. The “Why” we are doing this document. This can be high level, or very deep. You will also find a Kick-off document here. These are often PowerPoint slides that define the team, scope, way of working, and timelines. Logs I always like to have an Open Questions Log. A centralized document (everyone has access) to questions that need answers. The Decision Log is where you keep track of the closed questions. Again, very handy in an ongoing project, but extra useful once the project is over and it all becomes part of the bigger documentation. Meeting Notes are also handy to store here, probably best in a subdirectory. AI-generated documents are actually very welcome here (compared to other AI generated documentation everywhere else) Blueprints I like to keep my diagrams both in the raw format (visio, draw.io, lucid,…) and in static formats (like PNG). I always like to have diagrams that show both the Target and AS-IS states, and if it’s a big project, what the project phases look like Project related documents I always like a Gantt Chart. Make sure it’s up-to-date and accessible to everyone. Ideally you also have the Critical Path highlighted. Also, deadlines and gates should be present. Providing a central Gantt chart ensures that project management is democratised. The most important ones You pick and choose what you think is essential in the scope of the project. You can also add more later. That being said I like to always have at least the core documents. Even if it’s a project for an app that will be live for two weeks. The Business Case: If this isn’t clear, the architecture will drift. Decision & Question Logs: These are the most valuable “historical” nodes for future maintainers. TO-BE Diagram: A quick reference for everyone on what’s actually changing. Also, easy to copy and paste into presentations for higher-ups. The Gantt: That’s just basic project management and keeps everyone honest. Merging it back into the bigger documentation The diagrams can move towards the resources section with links to the applications. Going over the logs, you can remove the noise and keep the logs that are relevant to processes and applications to the logs of those processes and applications. You end up moving the rest to the archive section as a project folder. It’s very essential to not just delete here. If you have a similar project in the future, you can copy a lot of homework here. Organic documentation So these are my current views on documentation. To paraphrase this article and the previous one: Small documents that are interconnected. Accessible and owned by everyone. Organically grown and mainly written from a project perspective. <!-- SC_ON --> submitted by /u/GeneralZiltoid (https://www.reddit.com/user/GeneralZiltoid)
[link] (https://frederickvanbrabant.com/blog/2026-03-22-governance-documentation-to-support-projects/) [comments] (https://www.reddit.com/r/programming/comments/1s1jeoz/governance_documentation_to_support_projects/)
Is waterfall making a quiet comeback? (sort of)
https://www.reddit.com/r/programming/comments/1s1jkki/is_waterfall_making_a_quiet_comeback_sort_of/
submitted by /u/ludovicianul (https://www.reddit.com/user/ludovicianul)
[link] (https://blog.dochia.dev/blog/waterfall-returning/) [comments] (https://www.reddit.com/r/programming/comments/1s1jkki/is_waterfall_making_a_quiet_comeback_sort_of/)
https://www.reddit.com/r/programming/comments/1s1jkki/is_waterfall_making_a_quiet_comeback_sort_of/
submitted by /u/ludovicianul (https://www.reddit.com/user/ludovicianul)
[link] (https://blog.dochia.dev/blog/waterfall-returning/) [comments] (https://www.reddit.com/r/programming/comments/1s1jkki/is_waterfall_making_a_quiet_comeback_sort_of/)
DoG RANSAC DenGering SlitSpike algorithm for reading 9-segment Soviet Postal codes from grainy images
https://www.reddit.com/r/programming/comments/1s1kc5q/dog_ransac_dengering_slitspike_algorithm_for/
<!-- SC_OFF -->The Soviet Union introduced a special envelope for mailing letters in 1971. The envelopes contained standardized boxes at the bottom where the sended wrote out out the digits by connecting the dots. The intention of the GOST R 51506-99 standard was to make these envelopes machine readable. I have not been able to get any information about how the Soviet postal code optical character recoginition machines worked. So, I wanted to see if I could come up with a way to read the postal code from a grainy image. What started out as a simple project turned out to be a journey into finding an algorithm that could distinguish signal from the noise in wonky images, and then disambiguate between confusable pairs. This would've been much easier in the Soviet days, though. Because, in Soviet Russia, the algorithm finds you. <!-- SC_ON --> submitted by /u/reditzer (https://www.reddit.com/user/reditzer)
[link] (https://boreal.social/post/dog-ransac-dengering-slitspike-algorithm-for-reading-9) [comments] (https://www.reddit.com/r/programming/comments/1s1kc5q/dog_ransac_dengering_slitspike_algorithm_for/)
https://www.reddit.com/r/programming/comments/1s1kc5q/dog_ransac_dengering_slitspike_algorithm_for/
<!-- SC_OFF -->The Soviet Union introduced a special envelope for mailing letters in 1971. The envelopes contained standardized boxes at the bottom where the sended wrote out out the digits by connecting the dots. The intention of the GOST R 51506-99 standard was to make these envelopes machine readable. I have not been able to get any information about how the Soviet postal code optical character recoginition machines worked. So, I wanted to see if I could come up with a way to read the postal code from a grainy image. What started out as a simple project turned out to be a journey into finding an algorithm that could distinguish signal from the noise in wonky images, and then disambiguate between confusable pairs. This would've been much easier in the Soviet days, though. Because, in Soviet Russia, the algorithm finds you. <!-- SC_ON --> submitted by /u/reditzer (https://www.reddit.com/user/reditzer)
[link] (https://boreal.social/post/dog-ransac-dengering-slitspike-algorithm-for-reading-9) [comments] (https://www.reddit.com/r/programming/comments/1s1kc5q/dog_ransac_dengering_slitspike_algorithm_for/)
Announcing TypeScript 6.0
https://www.reddit.com/r/programming/comments/1s1luym/announcing_typescript_60/
submitted by /u/DanielRosenwasser (https://www.reddit.com/user/DanielRosenwasser)
[link] (https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/) [comments] (https://www.reddit.com/r/programming/comments/1s1luym/announcing_typescript_60/)
https://www.reddit.com/r/programming/comments/1s1luym/announcing_typescript_60/
submitted by /u/DanielRosenwasser (https://www.reddit.com/user/DanielRosenwasser)
[link] (https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/) [comments] (https://www.reddit.com/r/programming/comments/1s1luym/announcing_typescript_60/)
Why Over-Engineering Happens
https://www.reddit.com/r/programming/comments/1s1qq16/why_overengineering_happens/
submitted by /u/fagnerbrack (https://www.reddit.com/user/fagnerbrack)
[link] (https://yusufaytas.com/why-over-engineering-happens/) [comments] (https://www.reddit.com/r/programming/comments/1s1qq16/why_overengineering_happens/)
https://www.reddit.com/r/programming/comments/1s1qq16/why_overengineering_happens/
submitted by /u/fagnerbrack (https://www.reddit.com/user/fagnerbrack)
[link] (https://yusufaytas.com/why-over-engineering-happens/) [comments] (https://www.reddit.com/r/programming/comments/1s1qq16/why_overengineering_happens/)
Interactive Web UI: Next-Gen Frontend in 2026 | RuneHub
https://www.reddit.com/r/programming/comments/1s1ru96/interactive_web_ui_nextgen_frontend_in_2026/
submitted by /u/Low-Trust2491 (https://www.reddit.com/user/Low-Trust2491)
[link] (https://rune.codes/hub/tech-trends/the-rise-of-interactive-web-ui-why-static-pages-are-dead-in-2026) [comments] (https://www.reddit.com/r/programming/comments/1s1ru96/interactive_web_ui_nextgen_frontend_in_2026/)
https://www.reddit.com/r/programming/comments/1s1ru96/interactive_web_ui_nextgen_frontend_in_2026/
submitted by /u/Low-Trust2491 (https://www.reddit.com/user/Low-Trust2491)
[link] (https://rune.codes/hub/tech-trends/the-rise-of-interactive-web-ui-why-static-pages-are-dead-in-2026) [comments] (https://www.reddit.com/r/programming/comments/1s1ru96/interactive_web_ui_nextgen_frontend_in_2026/)
Why so many languages have allocators now
https://www.reddit.com/r/programming/comments/1s2b2wt/why_so_many_languages_have_allocators_now/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=TDCwoAuL5jc) [comments] (https://www.reddit.com/r/programming/comments/1s2b2wt/why_so_many_languages_have_allocators_now/)
https://www.reddit.com/r/programming/comments/1s2b2wt/why_so_many_languages_have_allocators_now/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=TDCwoAuL5jc) [comments] (https://www.reddit.com/r/programming/comments/1s2b2wt/why_so_many_languages_have_allocators_now/)
Handheld NES on a ESP32
https://www.reddit.com/r/programming/comments/1s2blu7/handheld_nes_on_a_esp32/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=jToSBvipl80) [comments] (https://www.reddit.com/r/programming/comments/1s2blu7/handheld_nes_on_a_esp32/)
https://www.reddit.com/r/programming/comments/1s2blu7/handheld_nes_on_a_esp32/
submitted by /u/BlueGoliath (https://www.reddit.com/user/BlueGoliath)
[link] (https://www.youtube.com/watch?v=jToSBvipl80) [comments] (https://www.reddit.com/r/programming/comments/1s2blu7/handheld_nes_on_a_esp32/)
Designing a Python Language Server: Lessons from Pyre that Shaped Pyrefly
https://www.reddit.com/r/programming/comments/1s2bw68/designing_a_python_language_server_lessons_from/
<!-- SC_OFF -->Pyrefly (https://github.com/facebook/pyrefly) is a next-generation Python type checker and language server, designed to be extremely fast and featuring advanced refactoring and type inference capabilities. Pyrefly is a spiritual successor to Pyre (https://pyre-check.org/), the previous Python type checker developed by the same team. The differences between the two type checkers go far beyond a simple rewrite from OCaml to Rust - we designed Pyrefly from the ground up, with a completely different architecture. Pyrefly’s design comes directly from our experience with Pyre. Some things worked well at scale, while others did not. After running a type checker on massive Python codebases for a long time, we got a clearer sense of which trade-offs actually mattered to users. This post is a write-up of a few lessons from Pyre that influenced how we approached Pyrefly. Link to blog: https://pyrefly.org/blog/lessons-from-pyre/ The outline of topics is provided below that way you can decide if it's worth your time to read :) - Language-server-first Architecture - OCaml vs. Rust - Irreversible AST Lowering - Soundness vs. Usability - Caching Cyclic Data Dependencies <!-- SC_ON --> submitted by /u/BeamMeUpBiscotti (https://www.reddit.com/user/BeamMeUpBiscotti)
[link] (https://pyrefly.org/blog/lessons-from-pyre/) [comments] (https://www.reddit.com/r/programming/comments/1s2bw68/designing_a_python_language_server_lessons_from/)
https://www.reddit.com/r/programming/comments/1s2bw68/designing_a_python_language_server_lessons_from/
<!-- SC_OFF -->Pyrefly (https://github.com/facebook/pyrefly) is a next-generation Python type checker and language server, designed to be extremely fast and featuring advanced refactoring and type inference capabilities. Pyrefly is a spiritual successor to Pyre (https://pyre-check.org/), the previous Python type checker developed by the same team. The differences between the two type checkers go far beyond a simple rewrite from OCaml to Rust - we designed Pyrefly from the ground up, with a completely different architecture. Pyrefly’s design comes directly from our experience with Pyre. Some things worked well at scale, while others did not. After running a type checker on massive Python codebases for a long time, we got a clearer sense of which trade-offs actually mattered to users. This post is a write-up of a few lessons from Pyre that influenced how we approached Pyrefly. Link to blog: https://pyrefly.org/blog/lessons-from-pyre/ The outline of topics is provided below that way you can decide if it's worth your time to read :) - Language-server-first Architecture - OCaml vs. Rust - Irreversible AST Lowering - Soundness vs. Usability - Caching Cyclic Data Dependencies <!-- SC_ON --> submitted by /u/BeamMeUpBiscotti (https://www.reddit.com/user/BeamMeUpBiscotti)
[link] (https://pyrefly.org/blog/lessons-from-pyre/) [comments] (https://www.reddit.com/r/programming/comments/1s2bw68/designing_a_python_language_server_lessons_from/)
Don't Count Java out Yet
https://www.reddit.com/r/programming/comments/1s2gjgv/dont_count_java_out_yet/
<!-- SC_OFF -->I remember when I first started working, I loved visiting this old mainframe building, where the "serious" software engineering work was being done. The mainframe was long-gone, but the hard-core vibe of the place still lingered. As I took any excuse to walk past a different part of the building to try and sneak a peek into whatever compute wizardry I imagined was being conjured up, one thing I always noticed was copies of InfoWorld being strewn across desks and tables (and yes, even in the bathroom - hey, I said it was hard-core ;-) ). I guess those days are mostly over now, but it's nice to see that there is still some great writing going on at InfoWorld (https://www.linkedin.com/feed/?shareActive=true&url=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2335996%2F9-reasons-java-is-still-great.html&shareUrl=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2335996%2F9-reasons-java-is-still-great.html#) by some talented and knowledgeable authors. Matt Tyson (https://www.linkedin.com/feed/?shareActive=true&url=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2335996%2F9-reasons-java-is-still-great.html&shareUrl=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2335996%2F9-reasons-java-is-still-great.html#) is definitely one of them and this is a great piece on why despite the #rust / #golang / #elixir craze, #java is still the language and framework to beat. (One of these days I'm going to finally learn #spring and re-join the java club.) <!-- SC_ON --> submitted by /u/scottedwards2000 (https://www.reddit.com/user/scottedwards2000)
[link] (https://www.infoworld.com/article/2335996/9-reasons-java-is-still-great.html) [comments] (https://www.reddit.com/r/programming/comments/1s2gjgv/dont_count_java_out_yet/)
https://www.reddit.com/r/programming/comments/1s2gjgv/dont_count_java_out_yet/
<!-- SC_OFF -->I remember when I first started working, I loved visiting this old mainframe building, where the "serious" software engineering work was being done. The mainframe was long-gone, but the hard-core vibe of the place still lingered. As I took any excuse to walk past a different part of the building to try and sneak a peek into whatever compute wizardry I imagined was being conjured up, one thing I always noticed was copies of InfoWorld being strewn across desks and tables (and yes, even in the bathroom - hey, I said it was hard-core ;-) ). I guess those days are mostly over now, but it's nice to see that there is still some great writing going on at InfoWorld (https://www.linkedin.com/feed/?shareActive=true&url=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2335996%2F9-reasons-java-is-still-great.html&shareUrl=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2335996%2F9-reasons-java-is-still-great.html#) by some talented and knowledgeable authors. Matt Tyson (https://www.linkedin.com/feed/?shareActive=true&url=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2335996%2F9-reasons-java-is-still-great.html&shareUrl=https%3A%2F%2Fwww.infoworld.com%2Farticle%2F2335996%2F9-reasons-java-is-still-great.html#) is definitely one of them and this is a great piece on why despite the #rust / #golang / #elixir craze, #java is still the language and framework to beat. (One of these days I'm going to finally learn #spring and re-join the java club.) <!-- SC_ON --> submitted by /u/scottedwards2000 (https://www.reddit.com/user/scottedwards2000)
[link] (https://www.infoworld.com/article/2335996/9-reasons-java-is-still-great.html) [comments] (https://www.reddit.com/r/programming/comments/1s2gjgv/dont_count_java_out_yet/)
Malicious litellm 1.82.8: Credential Theft and Persistent Backdoor
https://www.reddit.com/r/programming/comments/1s2h4by/malicious_litellm_1828_credential_theft_and/
<!-- SC_OFF -->litellm, a famous python package got compromised and it executes on your system without even importing it — cloud creds, SSH keys, K8s secrets, crypto wallets, env vars and what not, all exfiltrated to the attacker's server. Full technical analysis: https://safedep.io/malicious-litellm-1-82-8-analysis/ <!-- SC_ON --> submitted by /u/No_Plan_3442 (https://www.reddit.com/user/No_Plan_3442)
[link] (https://safedep.io/malicious-litellm-1-82-8-analysis/) [comments] (https://www.reddit.com/r/programming/comments/1s2h4by/malicious_litellm_1828_credential_theft_and/)
https://www.reddit.com/r/programming/comments/1s2h4by/malicious_litellm_1828_credential_theft_and/
<!-- SC_OFF -->litellm, a famous python package got compromised and it executes on your system without even importing it — cloud creds, SSH keys, K8s secrets, crypto wallets, env vars and what not, all exfiltrated to the attacker's server. Full technical analysis: https://safedep.io/malicious-litellm-1-82-8-analysis/ <!-- SC_ON --> submitted by /u/No_Plan_3442 (https://www.reddit.com/user/No_Plan_3442)
[link] (https://safedep.io/malicious-litellm-1-82-8-analysis/) [comments] (https://www.reddit.com/r/programming/comments/1s2h4by/malicious_litellm_1828_credential_theft_and/)
Litellm 1.82.7 and 1.82.8 on PyPI are compromised, do not update!
https://www.reddit.com/r/programming/comments/1s2h8lt/litellm_1827_and_1828_on_pypi_are_compromised_do/
<!-- SC_OFF -->We just have been compromised, thousands of peoples likely are as well, more details updated IRL at the link Update: Callum McMahon, who discovered this, wrote an explainer and postmortem going into greater detail: https://futuresearch.ai/blog/no-prompt-injection-required <!-- SC_ON --> submitted by /u/ddp26 (https://www.reddit.com/user/ddp26)
[link] (https://futuresearch.ai/blog/litellm-pypi-supply-chain-attack/) [comments] (https://www.reddit.com/r/programming/comments/1s2h8lt/litellm_1827_and_1828_on_pypi_are_compromised_do/)
https://www.reddit.com/r/programming/comments/1s2h8lt/litellm_1827_and_1828_on_pypi_are_compromised_do/
<!-- SC_OFF -->We just have been compromised, thousands of peoples likely are as well, more details updated IRL at the link Update: Callum McMahon, who discovered this, wrote an explainer and postmortem going into greater detail: https://futuresearch.ai/blog/no-prompt-injection-required <!-- SC_ON --> submitted by /u/ddp26 (https://www.reddit.com/user/ddp26)
[link] (https://futuresearch.ai/blog/litellm-pypi-supply-chain-attack/) [comments] (https://www.reddit.com/r/programming/comments/1s2h8lt/litellm_1827_and_1828_on_pypi_are_compromised_do/)