3 ms·
Sounds like the community might be a reason to use Vue over React ;) In all seriousness this is a problem I've run into before as well. I once reported a bug a
by jrs95 8y ago
Sounds like the community might be a reason to use Vue over React ;)
In all seriousness this is a problem I've run into before as well. I once reported a bug and the lead developer of the project responded saying he didn't think the bug existed. Setting the hostname in the config to the server's IP address was irreversible even if you change it later -- the site would redirect back to the raw IP and outgoing emails would have the raw IP in them. Many other users were commenting about the issue with no response from the maintainer, and I ended up finding a workaround using one of the "developer options" which was really just a one line ruby config change. Then, the author wrote like a one paragraph response saying that you should never set up the software like that and not to use that workaround because it's a "developer option". This bug went unfixed for about 2 years after that. And this is a relatively common and high profile piece of open source software. The whole thing was just bizarre, especially how positive my experiences with other open source projects (some third party Spring packages and Go Dep in particular) have been.
- mlevental 8y ago>Sounds like the community might be a reason to use Vue over React ;) I've run into these "no I'm not telling you because of best practices" people in every single "community"
- jrs95 8y agoI'm sure -- the only times I haven't are when I haven't even had the opportunity to. I was just joking around.
- specialist 8y agoGrrr. I’ve always designed away the sharp edges. Because I don’t want the 4:00a wake up call from panicky customers. Which is why all my devs also did rotations in tech supp, QA/test, build monkey, etc.