Conversation

Notices

1. Embed this notice
   nivs (nivrig@mastodon.social)'s status on Wednesday, 15-Oct-2025 02:21:32 JST nivs

   The Great Software Quality Collapse:

   https://techtrenches.substack.com/p/the-great-software-quality-collapse

   • Doughnut Lollipop 【記録係】:blobfoxgooglymlem: likes this.
   • Doughnut Lollipop 【記録係】:blobfoxgooglymlem: repeated this.
   • Embed this notice
     Wolf480pl (wolf480pl@mstdn.io)'s status on Wednesday, 15-Oct-2025 02:22:52 JST Wolf480pl

     in reply to

     @nivrig
     > The degradation isn't gradual—it's exponential.

     not quadratic or cubic but exponential? I hope the author has numbers to back this up

     > VS Code: 96GB memory leaks through SSH connections

     *clicks link*

     > not 96 GB per second, or per hour, or per connection
     > 96 GB is where the person realized and killed the thing

     ffs... this number is meaningless. It would've used all the memory if it kept running, like *most memory leaks eventually do*.

     Haelwenn /элвэн/ :triskell:, Doughnut Lollipop 【記録係】:blobfoxgooglymlem: and Johnny Peligro like this.
   • Embed this notice
     Gabriele Svelto (gabrielesvelto@mas.to)'s status on Wednesday, 15-Oct-2025 02:23:44 JST Gabriele Svelto

     in reply to

     @nivrig "AI is a force multiplier for incompetence" is the thermonuclear take we all need right now

     Doughnut Lollipop 【記録係】:blobfoxgooglymlem: likes this.
     Doughnut Lollipop 【記録係】:blobfoxgooglymlem: repeated this.
   • Embed this notice
     The Photonsphere (maridonkers@fosstodon.org)'s status on Wednesday, 15-Oct-2025 02:23:44 JST The Photonsphere

     in reply to

     • Gabriele Svelto

     @gabrielesvelto @nivrig With AI, the competent become brilliant, and the incompetent become catastrophic.

   • Embed this notice
     Wolf480pl (wolf480pl@mstdn.io)'s status on Wednesday, 15-Oct-2025 03:03:17 JST Wolf480pl

     in reply to

     @nivrig
     So the claim is that these are memory leaks that nobody bothered to fix, despite them being "large".

     But in all cases except Discord, the "large number" is how much RAM your computer has. Of course newer computers have more RAM, so a memory leak will have to leak more memory in order to run out of RAM.

     The only number that matters is Discord's 512MB/s - an outrageously fast leak, but that's only 1 datapoint

     Also, only 2/5 examples were not fixed at the time the article was pulished

   • Embed this notice
     Wolf480pl (wolf480pl@mstdn.io)'s status on Wednesday, 15-Oct-2025 03:03:17 JST Wolf480pl

     in reply to

     @nivrig
     > Android 15 launched with 75+ known critical bugs
     > linked article lists 5 bugs, none of them security vulns, no use of the word "critical"

     Sorry, I give up.

     We all know modern software is trash but to prove anything about why it's like that, or to quantify how much worse it is than it was before, the author would need at least a trace amount of intellectual rigor

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Wolf480pl (wolf480pl@mstdn.io)'s status on Wednesday, 15-Oct-2025 03:03:18 JST Wolf480pl

     in reply to

     @nivrig
     what's next

     > MS teams
     > uses all resources available due to a bug that was later fixed

     > 16GB RAM with 50 tabs now normal in Chrome
     > linked article says 2GB with 20 tabs
     > no mention of what kind of websites are loaded in those tabs

     > Discord
     > 32GB leaked in 60s =~ 512MB/s
     > no fix yet

     ok finally a number, and it is quite big

     > Spotify
     > uses all available memory, no timeframe specified
     > no fix yet

     so 1/5 examples has quantitative data

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 15-Oct-2025 03:04:58 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Wolf480pl
     @wolf480pl @nivrig Glad I went like "substack is never worth reading".