That would be cool, but human brains are weirdos. If you’re already copying text, you could’ve edited or annotated it, for example. For example, if it’s an opinion you don’t entirely agree with, you might feel obliged to say so, because you have the ability to do so when it’s a text post.

If you want to call that irrational, I’m not arguing against that. I’m just saying it’s the reality we live in and I’d like to have tooling to deal with that better, because I would also prefer text to not be screenshotted.

Yeah, really unfortunate that that’s not possible. Always having to take a screenshot and then type out letter by letter what’s on the screenshot, that can be quite annoying.

But even if copying text was possible, the reason people post pictures of text is to give proper attribution, but also to distance themselves from the content, so that it’s clear that they don’t necessarily hold the exact same opinion or that they might not have all the knowledge to defend the statements in the post.

Cross-posting could fill that same roll without screenshotting text.

Hmm, okay, maybe you want to report a bug for it not maintaining display settings, if you haven’t yet…

What do you mean by display outputs? Like what screens it uses? (That should be manageable with Win+P or the little monitor icon in the system tray.)

Would be cool, if we could cross-post Mastodon posts…

OCaml has a camel with two bumps. So, that’s gotta be the Perl dromedary camel…

I think, they meant the opposite. Extending your workday until 3 AM means you’ll be your least productive at that point. Whereas if you’re coding on a passion project at 3 AM (and you’re reasonably rested), then it’s often the most productive time of day, because there’s no distractions, nothing else to be doing…

The thing is, your attempts at eliminating boilerplate can be pretty bad and take pretty long before they’re worse than writing out the boilerplate in full.

Boilerplate code is by itself a problem. If it’s just scaffolding, i.e. you’re not duplicating logic, then it still makes code harder to read and annoying to maintain.

If you are duplicating logic, then it’s a maintenance nightmare. You fix a bug in one version of it, now you gotta update 14 other versions which the LLM dutifully generated with the same bug.
Or worse, it wasn’t dutiful (much like a human typically isn’t), so now you’ve got different bugs in different versions of it, as well as different fixes over time, and you quickly lose track which version is the good one.

I mean, yeah, but if Proton is doing an absolutely flawless job, then it has 0 performance penalty compared to Windows. All the actual gains still do come from Linux having less overhead. So, both are true, that Proton is killing it and that the gains come from Linux.

Well, and there’s also just lots of webpages implemented as an SPA – Single-Page Application.
Which you might be able to register in your browser as a PWA – Progressive Web App.
And which are just generally equally as interactive as an app, so good luck explaining the difference to folks who don’t care about implementation specifics…

In particular, frontend has to interact with humans, which is one hell of a messy API.

Yeah, I also thought it was a meme and used purely in derogatory form, until I learned that the term was actually coined by a co-founder of OpenAI…

But like, does that happen often for you, that you need a piece of code that’s gonna be thrown away?

I always feel like if code exists, it’s not gonna be thrown away, so it’s a good idea to make it maintainable. But I do probably have somewhat of a bias…

One thing to understand here is that it mostly depends on the “desktop environment”, which is basically the GUI of the system. (Imagine you could have the Windows XP GUI on a Windows 11 PC. Or the macOS GUI on a Windows 11 PC.)

Distros intended for desktop use will typically come with a certain desktop environment by default, so to some degree, you can talk about the distro, but yeah, there’s just gonna be a strong correlation with their default desktop environment.

To my knowledge, GNOME and (recent/Wayland versions of) KDE have good support. Most comments here imply these two desktop environments, so for example Ubuntu, Fedora and POP!_OS are typically GNOME, whereas Kubuntu and Nobara are typically KDE.

Some folks here also mention Linux Mint and LMDE working well, which use the Cinnamon desktop environment, so I guess that works well, too. Cinnamon is somewhat based on GNOME.
Well, and Elementary OS’s whole shtick is its Pantheon desktop environment, which is also based on GNOME.

So, basically, as Elementary’s Pantheon is its own thing, there’s no guarantee that it’ll work, but I would not be surprised.
As someone else already said, you can use a Linux Live USB to try it out before installing. You should be able to just follow along the installation instructions of Elementary OS and shortly before you actually install things, you should find yourself in Pantheon and can try it out.

It’s easy to set up a cache, but what’s hard is convincing your devs to use it.

Mainly because, well, it generally works without configuring the cache in your build pipeline, as you’ll almost always need some solution for accessing the internet anyways.

But there’s other reasons, too. You need authentication or a VPN for accessing a cache like that. Authentications means you have to deal with credentials, which is a pain. VPN means it’s likely slower than downloading directly from the internet, at least while you’re working from home.

Well, and it’s also just yet another moving part in your build pipeline. If that cache is ever down or broken or inaccessible from certain build infrastructure, chances are it will get removed from affected build pipelines and those devs are unlikely to come back.

Having said that, of course, GitHub is promoting caches quite heavily here. This might make it actually worth using for the individual devs.

I also remember there being a tiny shitstorm when Google started proxying package manager requests through their own servers, maybe two years ago or so. I don’t know what happened with that, though, or if it’s actually relevant here…

For Rust, as I understand, crates.io hosts a copy of the source code. It is possible to specify a Git repository directly as a dependency, but apparently, you cannot do that if you publish to crates.io.

So, it will cause pain for some devs, but the ecosystem at large shouldn’t implode.

It’s gonna be problematic in particular for organisations with larger offices. If you’ve got hundreds of devs/sysadmins under the same public IP address, those 60 requests/hour are shared between them.

Basically, I expect unauthenticated pulls to not anymore be possible at my day job, which means repos hosted on GitHub become a pain.

For that purpose, I use a language with a decent compiler, but I know not everyone is as lucky…

I think the main reason why Word is losing mindshare, is because it was designed for paper. The whole formatting system makes the assumption that there’s a fixed width and height into which your text and images fit. In reality, a phone screen is a lot narrower and a widescreen monitor a lot wider.

Markdown never made these assumptions. For the most part simply because plain text reflows to fill whatever space you give it. But there’s no way to position an image either, I imagine mostly for simplicity’s sake. It can look goofy at times, but it never looks broken.
That’s why I can write this comment on my phone and someone else can look at it on desktop and it’s perfectly readable in both scenarios.