DeadBabyOrgasm
They're a super cheap way of
1. allowing feature flags
2. injecting credentials in a way the user thinks about exactly once
3. moving workstation-specific details out of your code repository
They're implemented into the core of most every language in existence (especially shell scripts) and you're probably already using them without knowing. They're (get this) _variables_ for tuning to your _environment_.
Sounds like I'm being sarcastic here (eh, maybe a bit) but it never really hit me until I really dug into the concept.
I'm willing to throw a few bucks at that. For clip art (SVG) in a blog post, I'll throw $10-$15 at that. Per post. But the art needs to speak to me or otherwise just "click" with my yet-to-be-defined vision for the content. I don't know what will click until I see it. I also don't want to waste either party's time with my hemming and hawing, trying to put a feeling into words so I can describe to the designer... how I think they should do their job. I'm not the expert. I just fail at communicating. It's much easier on everyone if I see it already done or otherwise 95% of the way there.
Sites like these help me a lot more with finding things that just "click." At least a lot more than the alternatives of finding someone on Upwork, et al.
Does Bitwarden have that autotype option? If not, I'm wondering how difficult it would be to build it myself, if only for the desktop clients.
What I've settled on is to use a python version manager (pyenv is the least intrusive balanced with most usable) and using direnv to create project-specific python environments. Adding `use python 3.7.3` to an `.envrc` in a directory will make it so cd-ing into it will create a virtualenv if it doesn't yet exist and use the pyenv-installed python at 3.7.3.
- *-mode (specific syntax highlighting, commands, etc. based on project or task)
- edit/save remote files via built-in TRAMP [0]
- built-in plugin manager (interactive, or via emacs init config)
- MELPA [1]
- Non-blocking (e.g., run tests in one buffer while editing source in another)
- client-server approach (neovim adopted this, but emacs has had far more time to work out the kinks)
The main reasons I stay with vim are:
- already committed to vi-like muscle memory (and evil-mode, while admirable, doesn't cut it)
- no translation of VimL configs and plugins to Emacs Lisp
- many plugins for languages, frameworks, etc. which I use daily are severely out of date in emacs (and I'm too lazy to maintain them myself)
[0]: http://askubuntu.com/questions/79100/how-to-open-a-remote-fi...
[1]: http://melpa.org/
I'd still use vim-wiki because it's intended to be a lightweight knowledge database similar to a mind-map, but more robust. It allows for quick, easy organization of ideas whereas vim-notes appears to be more for a formal writing process.
Masters of subtlety...
(a) Use the upload form for Launchpad.net [0]
(b) Host your own deb server [1]
Unless you use Bazaar for a VCS, the only time you login to Launchpad is to upload a new release. With Homebrew it's built into git with adding a new tag. A _LOT_ lower barrier to entry here.
[0]: https://help.launchpad.net/Projects/FileDownloads#Publishing...
[1]: https://www.unixmen.com/setup-local-apt-repository-using-ins...
Either way, I'd definitely be interested in something like homebrew for ChromeOS. Guides for cross-platform capabilities would be most welcome!
echo "127.0.0.1 github.com" | sudo tee -a /etc/hosts > /dev/null
If I understand OP's question, it seems syncing would involve more than just `git push` from the local gitlab server to remote.
That said, IANAL.
I think the distributed, federated approach such as Friendica (et al.) will be more likely to succeed than this, in large part due to data ownership concerns.
That said, variety in this space is always welcome. We, as the users, can only benefit from it.
In my experience, this is an ambitious goal. As humans, we don't like change and, as a whole, won't do it without strong reason. Opening your browser means going to the bigger sites (e.g., Facebook) because they're convenient. The convenience isn't due to only thinking Facebook when thinking of social media, it's about what features Facebook offers me as its user.
If, on the other hand, the goal is more for the audience than the small websites, and it's to expose the average viewer to more variety, why not partner with Stumbleupon, Reddit, or one of many other community link-aggregation platforms?