• Artist: The Beatles
• Album: Revolver
• Song: Tomorrow Never Knows

Ah, so it does [1]. Apologies! Perhaps another older Thinkpad has a 12" screen? From what I’ve heard, and from my experience with my own T460, they’re usually pretty solid laptops, so if you could find one with the specs that you are seeking, I would say that it’s worth considering.

Older Thinkpad (eg T460)?

Dang, that’s pretty neat! Man, there’s probably going to be some funky bugs with legacy code getting included into Rust.

Make it work, then make it better.

I really like this one. It’s borderline a mantra.

I thought Rust already had several different methods for interacting with C++?

Oh? Would you mind sharing them? It would be absolutely fantastic if such a thing existed and is mature enough to be practically used.

Personally, I have little interest in learning or dealing with C++ solely for the sake of developing KDE applications. I would much rather use Rust.

Imo, restricting the languages that can be used for app development cuts out large swaths of developers who would otherwise be eager to develop software for the project. I’m sure there are some who wouldn’t mind picking up C++ for this cause, but I’d wager that they are a minority. Gnome beats out KDE in that regard, imo, as GTK has bindings and documentation for many languages.

As a counter to perfectionism:

If it’s worth doing, then it’s worth doing poorly. [source: a reddit user]

without having to reboot to run the installer?

I’m not sure that I understand what you mean. Are you saying that you want to be able to load the OS without having to reboot your computer? Or are you saying that you just don’t want to have to click the equivalent of “try the OS” when booting a live USB? If it’s the latter, you should be able to just select the flash drive as the install point (though, tbc, I have never tried this, but I don’t see why it wouldn’t work) (I think you’d need 2 USBs, though — you’d need 1 to be the installer source, and one to be the install point — I don’t think theres any installer that can run as a desktop application. Though, if it’s Arch Linux, you might actually be able to call pacstrap from the host OS — I’ve never tried this after having already installed the OS). There’s even OS’s that are specifically designed to be ephemeral on hardware in this way — eg Tails OS.

As of 2024-09-03T22:10:25.545Z, Starlink is now complying with Brazil’s X ban [1].

LibreOffice Draw?

What’s the use of storing the timezone?

Imo, mostly QoL.

I guess; otherwise the order of commits would stop making sense.

Fundamentally, Git doesn’t require commits to be dated (I’m assuming some things about the protocol here — there might be something in the source code that does a check, but my point will still stand). Version control only cares about the changes from one thing to the next. The time at which the change occurred is irrelevant for this end. Things like committer names, committer emails, commit times, commit messages, etc. are QoL additions on top of what I view as the base git protocol. I’m not sure if there is an RFC which outlines Git in more detail, though. If someone is aware of such a standard, please share it.

unless you meant to auto-convert the local time to a unix timestamp, that could work. I’m overthinking stuff.

Personally, that’s what I presumed they were referring to. Either that, or just storing a UTC time. Technically, I suppose storing UTC is effectively storing a timezone, but not in the sense of what this post is talking about.

When else would this matter?

• When a committer doesn’t want their geographic location to be known.
• When a committer doesn’t want their contribution activity to be known.

commit contains your name and email address.

That is a bit of identifying, yes, but, arguably, not as personally identifying as a timezone. Furthermore, the manual nature of entering a username and email puts the agency on the person to choose how they wish that commit to be identified, but the time is generally chosen automatically. Unless one is paying close attention to the commit log, it’s likely that many wouldn’t notice the timezone. It’s also possible, and completely forgivable, imo, for one to assume that the timezone is only shown client-side, and isn’t actually recorded; it is only when one looks at the documentation that they will see that the timezone is indeed recorded.

these metadata can be freely manipulated

This is essentially what I am advocating for if one is trying to improve the privacy of their Git contributions.

and serve purely as information for other developers

Who are you scared of seeing your time zone in a commit on a seemingly public code repository? This is such a pointless non-discovery

Be careful about forming arguments from ignorance.

leak

In case the usage of that word is core to your argument, note that I have changed it from “leaks” to “exposes”.

So a documented core aspect of the tool is a leak.

A service/tool being documented doesn’t necessitate that that service/tool is private. All large social media companies, which seem to universally be understood as the antithesis to privacy, have very detailed terms and conditions that outline exactly what those services do. Do you think those services should be regarded as private because what they do is documented…?

Impressive research

I’m not sure why the condescension is warranted.

Huh. That’s actually kind’ve a clever use case. I hadn’t considered that. I presume the main obstacle would be the token limit of whatever LLM that one is using (presuming that it was an LLM that was used). Analyzing an entire codebase, ofc, depending on the project, would likely require an enormous amount of tokens that an LLM wouldn’t be able to handle, or it would just be prohibitively expensive. To be clear, that’s not to say that I know that such an LLM doesn’t exist — one very well could — but if one doesn’t, then that would be rationale that i would currently stand behind.

I’m cringing at the date format “1-20-21”.

I’ve played it for a bit, and it’s a decently fun and well-made game! My only gripe is that it requires an email for signup; I wish it would only require a username and password. For most users, though, I’d wager that that’s a pretty minor issue.

I upgraded from 8GB to 16GB like 2 months ago.

Watch for battery life when buying older Surface devices. Replacing batteries in the older Surface Pros is notoriously difficult, because apparently the whole assembly is glued together.

Thank you very much for the heads up!

Newer versions are apparently more repairable, but you’ll have to investigate where that cut-off line of repairability is.

It looks like an attempt at heading in the direction of repairability started with the Surface Pro 9, but it’s still quite involved [1][2].