I almost expected someone to learn that just from me posting. 😅

Basically, OpenOffice used to be organized by Sun Microsystems. Then Sun got bought by Oracle back in 2010.
Oracle does not have a good reputation at all, so the OpenOffice devs from back then figured they’d need to take things into their own hands and set up The Document Foundation to organize further development. But the OpenOffice trademark was owned by Sun/Oracle, so they had to rename and get a new homepage and everything. The name they chose is LibreOffice: https://www.libreoffice.org/

After the OpenOffice project was effectively dead, Oracle handed it and its trademark over to the Apache Foundation, where it’s seeing occasional bug fixes. But to my knowledge, they don’t even have the capacity to fix all the security problems.
All the actual feature development happens over on the LibreOffice side.

So, in practice, if you want OpenOffice, what you really want is LibreOffice.

Yep. It does also optionally have graphics by the way. It just also has this accompanying text log in case you need to read up on wtf just happened.

Huh, did not know you could redirect confusion, but I guess, Ru is more than just a reflection amulet then. 🙃

Yeah, not great. You always hope that projects under a larger foundation, like GNOME, have a higher bus factor¹, but unless that foundation has dispensible income to pay someone, you’re ultimately still reliant on volunteers and not many people volunteer for maintenance.

What the foundation can do, though, which is also really important, is to hand over the keys to a new maintainer, should you disappear over night.
Like, yeah, forking is great, but some people will never learn of the fork. It happens about once a year that I find someone online who’s still using OpenOffice and that project has been practically dead since 2011.
So, I do hope we can get more open-source projects under some sort of umbrella. No idea how to actually do that, though. I also have open-source projects where I would not even know where to start to get them under some organization…

The Rust compiler is more sophisticated than most compilers, so it can be slower at the same kind of tasks. But it also just does a different task here.

One of the tradeoffs in Rust’s design is that libraries get compiled specifically for a concrete application. So, whereas in most programming languages, you just download pre-compiled libraries, in Rust, you actually download their source code and compile all of it on your machine.

This isn’t relevant, if you get a pre-built binary. And it’s not particularly relevant during development either, because you get incremental compilation. But yeah, if someone wants to compile a Rust codebase from scratch, then they have to sit through a long build.

Yeah, the good tooling also means it isn’t even terribly difficult for the dev to provide builds, but it isn’t quite as automated as publishing to crates.io, so many don’t bother with automating or manually uploading…

LibreOffice Draw works decently well for this.

Hmm, well no, but don’t you still risk being banned or at least being hidden away by the Algorithm™, if such scandalous thing as a nipple is to be seen?

I’m not sure now, if she actually said this is why she’s on PeerTube. Could also be that other social media platforms pissed her off and then she found a new home on the fediverse.

…just remembered, she recently posted a video, where she’s unboxing a Mastodon plush and figured, maybe she says something there, and yeah: Apparently, she got banned from Instagram a whole bunch of times, so now she’s self-hosting Masto and then evidentally also PeerTube.

https://peertube.doesstuff.social/w/qskCWUnsmJZLZ9ZP4KCiph

Yeah, Lety does some NSFW-adjacent videos, which YouTube is too stuck up for.

Most of the stuff posted to video.thepolarbear.co.uk is.

The guy who hosts the PeerTube instance, Hamish, is hardline anti-big-tech, I believe. Whereas Chris Were and Drew / uoou are mostly just tired of YouTube commenters. Well, and there’s some other folks, who occasionally post there, where I don’t know, whether they post to YouTube, too.

Usually, the desktop environment devs come together and standardize on something. But yeah, someone has to drive that effort. Open-source isn’t really something you plan, you just need someone to push for it.

Fuck Microsoft

For Germany, there’s also https://www.gesetze-im-internet.de/index.html which lists the laws in their current version, similar to dejure, but well, the webpage is actually hosted by our government. It’s as official as you’re gonna get on the internet.

I always just do ss -ltnp | grep <port-number>, which filters well enough for my purposes and is a bit easier to remember…

I’m on NixOS for my personal laptop, too. I just tried it and well, #!/bin/bash apparently does not work, but #!/bin/sh does.

The file /bin/sh does also exist as a symlink for me:

> ls -l /bin/sh
lrwxrwxrwx 1 root root 73 14. Dez 19:50 /bin/sh -> /nix/store/35yc81pz0q5yba14lxhn5r3jx5yg6c3l-bash-interactive-5.3p3/bin/sh*

Does that point into the bash package for you, too?

Edit: And for #!/bin/bash, the output was:

> ./test
exec: Failed to execute process './test': The file specified the interpreter '/bin/bash', which is not an executable command.

To give a quick highlight, because this case is often politicized and misrepresented:

The plaintiff, Stella Liebeck (1912–2004), a 79-year-old woman, purchased hot coffee from a McDonald’s restaurant, accidentally spilled it in her lap, and suffered third-degree burns in her pelvic region. She was hospitalized for eight days while undergoing skin grafting, followed by two years of medical treatment. […]

Liebeck’s attorneys argued that, at 180–190 °F (82–88 °C), McDonald’s coffee was defective, and more likely to cause serious injury than coffee served at any other establishment.

So, the lawsuit never demanded McDonald’s to put a warning that you’re not supposed to spill hot coffee on yourself. It argued that it’s an unnecessary safety hazard, because the coffee was served at hazardous temperatures.
No matter how many warnings you put down, it can happen that someone spills coffee on themselves and they shouldn’t need to be hospitalized from that.

Runtimes/“VMs” like the JVM also allow nice things like stack traces. I don’t know about the author but I much prefer looking at a stack trace over “segmentation fault (core dumped)”. Having a runtime opens new possibilities for concurrency and parallelism too.

Rust has stacktraces without needing a runtime. Don’t ask me what exactly is going on behind the scenes, but there is a way to request a stacktrace for a given point in the program. And unless you’re doing embedded stuff, a stacktrace is automatically generated for errors.

And as for concurrency/parallelism, it’s correct what you wrote, but I just wanted to point out that it doesn’t have to be a language runtime. Using Rust as an example again, you typically spawn the Tokio async runtime on program start, if you’re gonna do async/await stuff.

I find it annoying, because the hype means that if you’re not building a solution that involves AI in some way, you practically can’t get funding. Many vital projects are being cancelled due to a lack of funding and tons of bullshit projects get spun up, where they just slap AI onto a problem for which the current generation of AI is entirely ill-suited.

Basically, if you don’t care for building useful stuff, if you’re an opportunistic scammer, then the hype is fucking excellent. If you do care, then prepare for pain.

That is definitely not right. That sounds like you don’t have a shebang or it isn’t defined correctly. The shebang has to be the very first thing in the script, with no whitespace before it. It gets read out by the kernel, which very dumbly checks the first few bytes.

And well, such a shebang should also work for Python or the like. If you copy the first script in this link into a file script.py, then run chmod +x script.py and finally run ./script.py, does that print Hello, World! ?

I have fish set as the default command to run when my terminal emulator starts, but my system-wide default shell is bash and I always throw a #!/bin/sh or #!/bin/bash shebang at the top of my scripts either way.

With that setup, I hardly notice fish’s syntax differences. Are you using it like that, too?