Notices by Wolf480pl (wolf480pl@mstdn.io)

I should learn perl...

@bagder
couldn't you just temporarly set the locale to POSIX, do the comparison, and then set it ba... oh, wait, threads exist and libc's locale is a global per-process state :(

@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

@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

@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

@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*.

@p imagine wearing a star wars t-shirt but you've never been to a war, let alone the stars...

@Suiseiseki
@amonakov
But HDMI 1.0 was a proprietary extension of DVI. So if DVI kept getting newer versions, HDMI would have to decide between adopting the newer DVI standards as a base for the newer versions of the HDMI protocol, or explicitly choosing to not be DVI compatible.

Since DVI development ended, HDMI got to eat the cake and keep it to - they can stay backwards-compatible with DVI while having complete control of the direction in which the protocol is developed.

oh, apparently there is
https://elixir.bootlin.com/linux/v6.17.1/source/drivers/gpu/drm/drm_connector.c#L106

would that be dual-link HDMI? That'd explain why I haven't seen it...

@amonakov it's a shame VESA with DVI-D didn't lead the development of higher bitrates :(

@Suiseiseki
@amonakov
but they allowed higher bitrates for HDMI to be completely controlled by the evil HDMI Forum :(

@sjb SPAAAACEEEE

@sjb

if HDMI-A-1 is so cool then why isn't there HDMI-B-1?

Do I know a mechanical keyboard nerd who knows all these post-Cherry switches?

I know that I like Cherry MX Blue, but it's hard to find a large keyboard with these these days.

Should I look into switches from other manufacturers?

Are there any that are designed to feel the same as MX Blue, so that I could buy a keyboard with them blind, without first trying them out?

Was there a technological progress such that the newer switches are objectively better than the original Cherry MX ?

@xero

dev: Jenkins works horribly

me: have you ever seen a Jenkins that worked well?

dev: yes, at my previous job, where it didn't do much, it only ram tests

me: so how did you deploy things?

dev: Through ansible, and you had to first ssh to a thing then to another thing and only then you could run ansible. I hated that.

dev: Being able to deploy through one click in Jenkins is great. But it would be better if I didn't have to wait for so long.'

@piggo yeah, if anything it should be a basketball court

@Suiseiseki
@quad @lanodan
oh but don't you know that working with someone who knows someone who once talked to Stallman makes you responsible for all the social missteps RMS made?

@lanodan @quad
Oh I don't mean Alpine.

I mean uutils and stuff. And not necessarily its devs, but I've seen a few people on fedi cheering for replacing GNU stuff to disassociate themselves from FSF or sth...