935 karma · joined June 10, 2021
Looking at the examples given, perhaps it would be relatively trivial to wrap both these libraries into a single one where the library does the if statements for you.
Having said that, moving logic for id generation to the application because it's less portable otherwise is an odd reason.
If it's a company, please have the forum integrated into your software.
I seriously do not want yet another login unless there is a good reason. It's ridiculous. I have nearly 700 logins in my password manager and I'd say probably 500 of those items are websites I've registered once to ask a question (quite often questions that go unanswered). Half of these forums do not even provide the capability to removing my account without contacting the admins, which is just an unnecessary hassle.
[0] https://extensions.gnome.org/extension/1486/extensions-sync/
[0] https://github.com/uBlockOrigin/uBlock-issues/issues/1357
5% is certainly better than 20%, but when you don't have the money, even 1% deposit is too much.
Are we just gonna implement everything on top of PostreSQL?
I dislike loyalty to any company because even if you're a permanent employee, the company won't hesitate to fire you or replace you if it comes to it.
At the end of the day, time is the most valuable resource people have, and if you're okay with working for the rest of your life for someone else without enjoying your life, then fine, otherwise, you really should re-consider your position.
Also, if you're a heavy vim user, and if you use tridactyl for Firefox, for some of the easier user script (e.g. simple redirects), you can use tridactyl, which might be cleaner. It's not as clean for larger scripts but it can work too.
$ ll
drwxrwxr-x - dan 27 Oct 15:12 -I .idea
.rw-rw-r-- 15 dan 9 Sep 11:44 -N .tool-versions
drwxrwxr-x - dan 9 Sep 11:53 -I dist
drwxrwxr-x - dan 23 Sep 18:53 -- docs
.rw-rw-r-- 376 dan 29 Jun 12:26 -I some-project.iml
drwxr-xr-x - dan 10 Sep 12:28 -I node_modules
.rw-rw-r-- 301 dan 21 Oct 13:17 -N override.env
edit: if it wasn't clear, the above output is a subset of the real output.The way I handle it is essentially never setting up automatic thread locking, and then, default to closing the issue, unless I add some specific label.
This is mostly for my sanity. There's a lot of issues where you get an issue raised with "x doesn't work", with little to no information. Great, I can't do anything with that, so I push back, and often you don't hear anything back. At this point, I close it (or rather, stale bot does after inactivity). If the user then provides more information and the issue is triaged and valid, I add a label, which makes sure stale bot does not close the issue.
If an issue does get closed, I'll get a notification if someone ends up commenting, and I can take appropriate action. It also gives others the opportunity to comment if they can provide additional context.