Sadly, I have the same experience. It's one of the minus points of using Thunderbird, alongside the lack of the feature for shipping my configurations (e.g. filters) across machines.
Agree. Writing communication is essential, and might have more influence than speaking communication, in a remote working environment. The whole OSS movement has been built on this.
> Is there anybody who can share their experiences with issues and workarounds in this area?
Just use your Bash/zsh to run Bash/zsh scripts: `bash script.sh`.
> turned off by it not being POSIX-compliant.
I was like this when I first started using Fish. I spent some time to learn some different syntax to get away from the POSIX-compliance. Overall, I think the saner syntax of Fish is worth the effort. Now I use the terminal much happier.
Besides, 90% of the time I don't need to follow POSIX-compliant. Many scripts or extensions nowadays support Fish.
For enterprise use, I still stick to Bash/zsh. They're the standard.
From my experience, programming and technology communities are already really strong on Lemmy. I'm confident to say that if you care about these topics, moving from Reddit to Lemmy is a good option.
For another categories, they're still small and having struggles gaining traction to have enough users and posts to be lively. But I think it's just a matter of time if Lemmy continues polishing its features and community discoveries.
I used to love Tuta for the tempting price (1eur/month). But now due to the increasing price, poor UX, no bridge to Thunderbird, broken filter rules, I switched to another provider.
I still have an account that I have some stuff linked to, I want to close it down entirely soon, it sucks there isn't any way to export all my emails without paying though.
I think the only option to make sure it will run in the 10 years is to package the linking libraries and all the dependencies. Container (e.g. Docker) or Nix can solve this, provided that these technology still live in the next 10 years.
> The way most people talk about software engineering, you'd think they were some kind of open-source warrior building entire applications from scratch when really they're on the Cancel Prime Membership Button Obfuscation Enablement team at Amazon.
True, if one apply most of the lessons in the article (e.g. "Nobody gives a f** about your clean code") to a well-established open source project, the maintainers will grind you to death.
