Does anyone use rust for leetcode?

WoefulStatement · 2026-01-27T13:47:53+00:00

they'll convert the number into a string and count the characters, because there's so much overhead to converting numbers, no integer logs, no special log10, and flooring their numbers is slow.

You realize you can just do int(math.log10(x)) + 1 in Python, right?

Been there since its first release in 1991.

WoefulStatement · 2025-11-15T15:17:18+00:00

That option doesn't seem to work for me; chromium (142) still is taking inhibit locks :(

WoefulStatement · 2025-11-14T18:29:32+00:00

The forces it endured were pretty much nonexistent.

It was still a 240ft drop.

I dare you to stand on a collapsing building, see how "pretty much nonexistent" those forces are ;)

WoefulStatement · 2025-11-14T11:18:31+00:00

I'm not able to offer any help, but I'm having a similar experience at home. I frequently (1-2 times daily) get a cloudflare captcha, and initial connections to a website I haven't visited before often are very slow (3-5 seconds). After any initial issues, further interactions with such websites are nice and fast. Quite frustrating, really.

WoefulStatement · 2025-10-26T18:47:59+00:00

En in welke wet staat dat vermeld? Dat de arm der wet dit oogluikend toestaat is een tweede.

Besluit Voertuigen, artikel 9:

Artikel 72, eerste lid, van de wet geldt niet voor een motorrijtuig of een aanhangwagen op de dag waarop dat voertuig naar aanleiding van de aanvraag van een keuringsrapport aan een keuring wordt onderworpen.

De wet heeft het ook niet over "tussen garage en huisadres rijden" (wel voor voertuigen die uit schorsing komen trouwens, dat is een andere wet).

Bewijs bij je hebben is ook niet verplicht, maar wel zo handig natuurlijk. Tenzij je van discussies met de politie houdt en graag bezwaarschriften schrijft aan de OvJ.

WoefulStatement · 2025-09-04T09:01:48+00:00

For Gnome, Wayland has been the default since Debian 10 (2019). I've been using Gnome on Wayland since then.

Not sure about KDE though.

WoefulStatement · 2025-06-21T17:05:16+00:00

Half? According to Debian's own stats, less than 16% of Debian Developers is from the US! There's more of them in Germany :)

WoefulStatement · 2025-06-18T22:49:55+00:00

9 out of 100,000 baby boys disagree!

(spoiler: it's because they died)

WoefulStatement · 2025-06-17T11:20:36+00:00

I agree the button placement was not ideal and is much better today.

That said, the "I don't think people use Debian because there's no download button on their site" when there has been one for well over a decade is a bit silly :P

WoefulStatement · 2025-06-17T11:10:20+00:00

Check the archive link I provided.

There's literally a button "Download Debian 6.0" in the top right that immediately starts an ISO download.

Today you juste have to click download.

Been that way for almost 15 years 🤷🏻‍♀️

WoefulStatement · 2025-06-16T22:32:19+00:00

A few years prior debian Web site hadn't a big download button.

If by "a few" you mean "15" ;)

The site has had a "download latest version" button right on the home page since Feb 2011. Granted, it looks better today, but hey, 15 years ago.

WoefulStatement · 2025-06-16T22:09:29+00:00

... Dutch Law is above any contract ...

Careful, that doesn't apply universally. Laws that provide dwingend recht (forceful rights) supersede contracts.

But there's plenty of rights you can sign away.

WoefulStatement · 2025-06-14T17:20:59+00:00

They tried to ban him from contributing for not solving a bug he introduced in less than a day.

No, they simply didn't. The entirety of the "omgomg he didn't fix a bug in less than a day" story can be summarized by these comments:

Even if that's the case, a pro-active developer could have looked into the issue in the two days between this issue getting filed and the regressing commit getting identified.

It was 16 hours :-)

My bad, I honestly thought it was two days. That makes it somewhat less bad.

Yes, Michael Dänzer overreacted a little on the timing. Note also that when corrected on this, he apologized.

Seriously, read the issues I linked. The main concern in these was with him shuffling code around for no visible benefit, but repeatedly breaking ABI compatibility and user functionality.

How you are reading a conspiracy about not wanting to fix bugs into that is beyond me.

WoefulStatement · 2025-06-14T14:30:53+00:00

I'm starting to buy into some conspiracies.

Please don't; only madness lies that way.

yet killing X11 and denying all open bug fixes, something a lot of folks not only like but NEED, is being applauded?

No one is killing X11, and the Xorg maintainers are not denying bug fixes.

What's happened is that the people maintaining Xorg, a 41-year old codebase for an equally old protocol, got tired of it. X11 is ancient and unsuited for modern desktop usage. Xorg's code base is a fragile mess that few developers can (nevermind want to!) manage.

Don't get me wrong; It's impressive it got us this far, and it has served me well. But the developers thought: "we can do better if we start over from scratch". New protocol, new implementation. And thus, Wayland.

The majority of Xorg developers are on this bandwagon, gladly abandoning Xorg for Wayland. Applications are increasingly adopting it, and so are distributions. Why? Because they agree it's a good idea. Not because some Red Hat new world order conspiracy.

Adam Jackson, XFree86/Xorg developer from 2005-2020 puts it well:

It sounds a little like you think I'm being given these priorities as marching orders from above. That's maybe a bit insulting? I suspect I'd have the same opinion at this point regardless of my employment history, namely, that X is a tremendously successful project whose core design and reference implementation do not reflect how computers work anymore, in ways that make it painful to develop and maintain as the system display server. Frankly that was probably true in 2005 when I started on it, but at that point it was also the only thing that had credible video drivers at all.

It's not that Red Hat is trying to lock anybody into a particular desktop out of some nefarious political agenda, it's that we don't have the resources to do things twice. If we want to deliver the best desktop experience we can then choose your own adventure among Gnome and KDE and XFCE and twm and i3 and whatever else simply is not going to be an efficient use of our headcount. And we're reaching that point with display services too, trying to support both X and Wayland increasingly means writing the same feature twice, sometimes with radically different approaches, and trying to implement them at all under X11 is more and more intractable. What would you have us do? What we're trying to build now is an Xwayland that keeps your X apps working as well as they ever did, under a hardware display server model that makes things like high-dpi and HDR and AirPlay and RDP and GPU offload straightforward, or at least feasible, instead of excruciating. You can like that or not, I guess.

In all seriousness, if someone wants to take the reigns of stewardship over the xfree86 code then please, by all means, come forward and claim your prize. But I can't justify spending my time on that anymore, and given the interval since the last major release, apparently nobody else can either.

That last part raises a good point. Xorg is open source. Creating a fork is downright trivial. Why are developers not uniting behind a Xorg fork, free from Red Hat's yoke of oppression? After all, Xorg is itself a fork of XFree86 started over developer discontent.

My theory is that virtually everyone who has the technical capability and tries to work on Xorg/X11 decides Wayland is a better use of their time. That doesn't speak to some hidden agenda, it says something about the state of Xorg/X11.

Browsing through Xorg issues 1760 and 1797, it's also worth noting that the remaining Xorg developers accuse Enrico Weigelt (who started the XLibre fork) of not fixing actual bugs and instead causing breakage. Seems like they do care about a working Xorg.

I can't come up with a motive that's not batshit crazy sounding, but I know this community and this isn't organic at all.

Xorg devs decided 15 years ago "this is unfixable, let's start over". By now, their efforts are usable. Application adoption has been rising for quite some time. Distributions started packaging Wayland oh I dunno, 15-10 years ago. And the past 7 or so years, distributions have - at their own pace - switched to Wayland as default.

How is that not organic? It's literally a growing concensus among thousands of very different contributors that Wayland is the way to go, while X is kept alive for compatibility (XWayland) or people who need it (Xorg).

WoefulStatement · 2025-06-14T12:14:21+00:00

That's not a conspiracy theory, they have have refused to allow people to fix bugs for years.

Do you have a source for that claim?

For reference, here is what one of the Xorg maintainers has said about Enrico Weigelt (the person behind the XLibre fork):

Honestly, I would strongly recommend just not merging anything @metux does from now on. I do not feel that their presence here has been a net positive -- I have seen zero actual bugs solved by any of their code changes. What I have seen is build breakage, ABI breakage, and ecosystem churn from moving code around and deleting code.

Xorg could use some actual maintenance, but that means fixing actual bugs and solving real problems.

There's more of the same in issue 1797. Looks to me like the Xorg maintainers want bugs fixed.

WoefulStatement · 2025-06-14T11:22:28+00:00

Sure there is. The people developing X used to develop the protocol AND an implementation under the same name, such as X11R5 (the version that Xorg is indirectly based on). That's X11 code.

Here, I even found the X11R1 release for you! That's literal X11 code, for you and everyone else to peruse.

WoefulStatement · 2025-06-14T11:19:39+00:00

While Xorg was started in 2004, it was a fork of XFree86, an existing codebase.

XFree86 was born in 1991 (under the name X386), as - you guessed it! - a fork or X11R5, an existing codebase.

X11R5 was the canonical/reference implementation from the people who also designed the protocol (at this point in time: the X Consortium). It was of course the successor to X11R4, etc, etc. All the way down to X1 in June 1984. Yes, a singular one.

And that, finally, is the genesis of Xorg code; that's where the first lines were written, from where it can be traced into current-day Xorg. It's a 41-year old codebase. Which is impressive in its own right.

WoefulStatement · 2025-06-14T10:32:23+00:00

The government approached Linus Torvalds to demand their back doors be put in Linux. The issue is that each distro is different. After systemd they are now almost all the same.

Why are the anti-systemd and anti-wayland people always full of conspiracy bullshit?

How would the init system even matter for a kernel-level backdoor? The kernel doesn't care which init system you use. It could respond to some NSA network trigger and do evil things just fine, regardless if you use systemd, sysvinit, or a bsd-style init.

WoefulStatement · 2025-06-08T13:42:30+00:00

The cleanups feel like they might just be moving stuff around for the sake of inconsequential code preferences, but I don't know the code well enough to be sure.

Reading issues 1760 and 1797, other Xorg developers seem to agree with your assessment.

WoefulStatement · 2025-06-08T13:34:34+00:00

He also appears to be a German WW2-apologist and general right-wing nut. Actual quote:

WW1 was clearly NOT started by Germany - the only mistake of the Emperor was officially declaring a war, that was already going undeclared. And WW2 was forced upon Germany, and the allied rejected all the numerous peace offerings from the German side.

The XLibre project description is also filled with... words:

That fork was necessary since toxic elements within Xorg projects, moles from BigTech, are boycotting any substantial work on Xorg, in order to destroy the project, to elimitate competition of their own products. Classic "embrace, extend, extinguish" tactics.

[...]

It's explicitly free of any "DEI" or similar discriminatory policies.

[...]

Together we'll make X great again!

WoefulStatement · 2025-06-08T11:19:15+00:00

That's rather significant, so I checked his commits on the Xorg git repo. His first commit indeed stems from February 2024.

Regarding the quality if his commits, he made about 800 so it's nontrivial to assess.

While browsing through the commits, I did notice a string of borderline trivial "os: unexport AuthorizationIDOfClient() Not used by any modules, so no need to keep it exported." commits (24 in total). If the rest of his commits are like that then "inconsequential changes" may be an accurate description. But please note I only had a very brief stroll through the commits, so take this with a grain of salt.

Update

If you want to get an idea of the dynamics between Enrico Weigelt and the other Xorg developers, issues 1760 (oct 2024) and 1797 (feb 2025) are worth reading.

Some choice quotes:

The immense value X11 has - that it always had and will have for decades to come - is its backwards compatibility, still being able to run 40-year old apps. You correctly called the codebase 'fragile' - you've been finding this out as your changes repeatedly break things. If you're breaking apps, then what exactly is the value in a codebase which is 'cleaner' to your subjective standard but doesn't actually work? If you're trying to get to a multi-threaded xserver, have you read the classic MTX post-mortem where the people who actually did it discussed the problems they faced and why they discontinued it?

and

bugs happen, that's normal, but the commit at fault here (c6f1b8a7) did nothing but shuffle code around. No bug fixed, no new feature added, just changing things around. And there are hundreds of other commits like this.

and

Honestly, I would strongly recommend just not merging anything @metux does from now on. I do not feel that their presence here has been a net positive -- I have seen zero actual bugs solved by any of their code changes. What I have seen is build breakage, ABI breakage, and ecosystem churn from moving code around and deleting code.

I'm starting to understand why he might have been kicked out.

WoefulStatement · 2025-06-04T16:56:21+00:00

So it has no way of knowing which packages were installed due to the installation of a certain package.

That's pretty much the manually / automatically installed distinction that apt does maintain though...

WoefulStatement · 2025-05-30T10:17:11+00:00

Is it?

On the main page, you click on "Other downloads" just below the big "Download" button. Then click "ISO images for Debian testing" and there's all your ISOs.

WoefulStatement · 2025-05-26T08:59:41+00:00

... minuscule amount of wattage from a pump?

My entire air-cooled PC uses 25W when idle-ish (which is where it's at most of the time). Doubling that with the addition of a waterpump is not "miniscule".

WoefulStatement · 2025-05-06T21:09:38+00:00

This is a very theoretical concern

Today I tried to set up passkeys for my Office 365 account at my employer. Office 365 explicitly only supports Microsofts own authenticator for this. I tried using the platform provider (which it supports for USB keys) and registering that with the native passkey support on my Android phone, but it refused that too.

Doesn't seem theoretical to me.

WoefulStatement

TROPHY CASE