Pistos2

Here's something I sometimes tell people:

Contentment comes when "the way you want it" and "the way it is" overlap enough -- but sometimes in life, you can really only change one of those.

This article would have been significantly easier to comprehend if the author had given the tradeoffs names instead of constantly referring to them by "first", "second", and "third" tradeoff. (Granted, he finally does so at the end of the article.)

> If you also take a look at the tests than never fail, you will also have a sense of the bugs you should not write.

Just checking: Did you mean "the tests you should not write"?

(I'm not OP) Zulip is good in theory, but I had two problems with it:

1) they had no [simple] means to install it on an existing server (VPS, what-have-you). It assumed (required!) that Zulip would be the only thing on whatever you installed it on. That is, it seemed to assume a container environment (docker, etc.)

B) The public Zulip instance exposed everyone's email address in plain text, ready for easy harvesting.

iii) It's hard to alter the inertia of a team or organization of sufficient size that is already using Slack.

I'm hardly a Slack fan, but, in fairness, I've never considered Slack to be slow or resource intensive. Either the web UI or the (OSX) desktop app.

Or are you referring to audio calls and video calls?

> no point running STUN an TURN on the same server as Nextcloud

I just prefer to self-host as much as possible.

Yep, you're right. My mistake. But we've been touch by other means.

I'm using coturn for TURN and STUN, and they are on the same VPS that hosts the Nextcloud code, version 13. If you actually want to help me solve the problems, send me a DM on github (username Pistos), and I can give you more of the technical details.

In my experience, Nextcloud's file sharing features are great, working as expected. We use it mainly to share large files with business contacts, both directions. I haven't tried the desktop apps. We use the web interface and the mobile apps.

Anecdata point: I had a lot of trouble setting up Nextcloud Talk with my own STUN & TURN servers. Even after I'd gotten that going, NCT video calls have been extremely unreliable, with it fully working only maybe 1 in 5 times, or worse. I still don't know why. Could be dependent on the kind of Internet each side is connected to (home network behind ISP router vs. coffee shop vs. corporate network with potential firewall, etc. etc.)

I get the point of this, but me personally, I prefer to have aspects of me forgotten/gone rather than remembered, stored and searchable in the future. Yes, it's true that, about once every two months, I am looking for something that I swear I came across on the Internet at some point. However, the rest of the time, I'm able to re-find it just by doing another search, whether on search-engine-of-choice, or a search box on particular-website (e.g. socnet, stackoverflow, reddit, github, hacker news...).

I can't imagine writing a real-world Vue app without Vuex. As such, I can't help feeling like this article, despite the best of intentions, is probably misrepresenting things. The last several Vue apps I've written have not used `emit`; not one single time. (context: `emit` is shown/used in this article)